-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neat URL - Testing for 4.0.0 #94
Comments
Wildcards doesn't work anymore. If you add also |
gets rewritten to: But it should stayed intact (no changes should be made) |
Re-initialise listener seems to work OK. |
Is this a regression since 4.0.0 or is it the case for the current Neat URL version on addons.mozilla.org as well? |
Task list for Smile4ever
|
I can't see changes in the browser console. |
Looks fixed now. |
Click on Neat URL icon on toolbar does not switch between disabled and enabled. |
|
@Smile4ever thank you for your work. Cheers |
Thanks
Sometimes the badge text interferes with the enable/disable functionality, I'm afraid this is a bug in Firefox and not something Neat URL can change.
How did you test this? I used https://vivaldi.com/blog/teamblog/vivaldi-1-13-adds-window-panel/#pk_campaign=newsletter&pk_kwd=community |
Regarding the logging: [Neat URL]: (type main_frame): 'http://www.omgubuntu.co.uk/2017/05/ubuntu-desktop-gnome-extensions-survey-1710?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+d0od+(OMG!+Ubuntu!)' has been changed to 'http://www.omgubuntu.co.uk/2017/05/ubuntu-desktop-gnome-extensions-survey-1710' background.js:462:3 It seems to work okay and as expected. |
Can you retest using the changes in git? (not the ZIP version, that one wasn't updated yet)
Can you retest using the changes in git? (not the ZIP version, that one wasn't updated yet) |
That is strange... I retested all again and still the same. and with https://github.com/Smile4ever/firefoxaddons/archive/master.zip Can you point me to the git directly?... maybe I am taking the wrong source. Cheers |
In case you don't manage to do the steps above: I also updated the ZIP version which can be found here: |
OK... I will take the ZIP. It seems easier. :) |
Its different output between 3.2.0 and 4.0.0... Original: 3.2.0: 4.0.0: |
Took the latest ZIP, but still the same, at least the your vivaldi test URL, but wildcards are now OK (the Cheers |
Thank you. Are you sure you added "#?pk_campaign" (with the question mark) and not "#pk_campaign"? |
^^That was it. "Vivaldi" is OK now. |
Logging also OK. |
Now I have lost myself what I have tried and what not. :) Cheers and thank you |
OK... second round, now with more clear brain :): #73... the URL is still not left intact, but now does not cause breakage #75... didn't test this one #93... OK now #91... OK now and count number is correct #76... didn't test this one #83... Works but not with wildcard and I am puzzled why the question mark is needed Thank you |
#73: If it does not cause breakage, I'm happy enough.
Exact hash parameters need to use #, for example #bio Garbage like #?utm_source=hi&utm_campaign=github needs to use #? This is because those hash parameters behave like search parameters, but from a technical standpoint they are not. I could support #& as well, but I think it's better to only have one variation so users don't get confused more: #? So to answer your question: when garbage (and most of the time, but optionally &) comes after #, and you want to delete that parameter, use #? Edit: To be clear: the ZIP file has been updated again so if you want to test #83 again you will be able to in an easy way. Thanks for your help so far! |
#83 works now also with wildcards. Thank you :) Just one more thing: Otherwise perfect job. Thank you @Smile4ever. :) |
Do you have any ETA for publishing it to AMO? |
Tomorrow evening probably. |
@crssi
The code is in git, plus there is also a compiled version in ZIP format (but I think it's easier to use about:debugging)
Things you can test:
And any breakages you notice. Please use this issue for any problems you find that are unrelated to existing issues (otherwise, use the relevant issue to comment on).
The text was updated successfully, but these errors were encountered: