update-browser bug or Firefox ESR bug?
Posted: 23 Sep 2021, 14:44
I just used update-browser -d -f and choose creating the ESR version.
In the setup I gave update-browser this default homepage URL:
since that this lets the browser to instruct forum.porteus.org to first open the login screen, and after that it shows me the most recent changed posts in all the threads I posted so far, aka "Quick Links ▷ Your posts", aka my "subscribed" threads as some forums call such.
But this is what either Firefox or ncmprhnsbl script turned it into:
That URL by itself is useless. It only does a useless search and so strains the forum.porteus server needlessly, and results in 0 matches.
In FFx settings FFx indeed shows that this is the URL
it is set up to be the homepage - which is a utterly senseless URL.
I have no clue how that could have happened.
I also created the most recent PM version using the same URL as homepage and this is what PM tells me its homepage is:
Here once again a single misplaced character changes a good URL into a senseless one.
Is the change due to a bug in the live version of update-firefox-live or is it a bug in FFx itself?
A homepage can be anything a user so desires, and wanting to log in into the best Linux forum there is and then having told the forum to show you the wanted threads is a very valid homepage for all and any browsers..
Why mess it up by adding a unnecessary / at the end? A given homepage needs to always be treated literally, not knowing if adding a simple / at the end when there was none originally can be harmless (like with changing http://ard.de into http://ard.de/ )
"Simple" URLs like these do not create a difference between the version with the / and without the / at the end.
But complex URLs like the "let me log into http://forum.porteus.org and then show me the most recent of my "subscribed" threads" can be messed up by a seemingly innocent / at the end.
Of course the user can simply edit the homepage URL in settings and remove the / at the end.
But a user usually wants his/her modules to work as intended from the stand and not having every time when used in a fresh environment to be fixed. Again. And again.
So please, if the added "/" is indeed a bug in update-firefox-live please fix that bug.
In the setup I gave update-browser this default homepage URL:
Code: Select all
https://forum.porteus.org/search.php?search_id=egosearch
But this is what either Firefox or ncmprhnsbl script turned it into:
Code: Select all
https://forum.porteus.org/search.php?search_id=egosearch/
In FFx settings FFx indeed shows that this is the URL
Code: Select all
https://forum.porteus.org/search.php?search_id=egosearch/
I have no clue how that could have happened.
I also created the most recent PM version using the same URL as homepage and this is what PM tells me its homepage is:
Code: Select all
http://forum.porteus.org/search.php?search_id=egosearch
Is the change due to a bug in the live version of update-firefox-live or is it a bug in FFx itself?
A homepage can be anything a user so desires, and wanting to log in into the best Linux forum there is and then having told the forum to show you the wanted threads is a very valid homepage for all and any browsers..
Why mess it up by adding a unnecessary / at the end? A given homepage needs to always be treated literally, not knowing if adding a simple / at the end when there was none originally can be harmless (like with changing http://ard.de into http://ard.de/ )
"Simple" URLs like these do not create a difference between the version with the / and without the / at the end.
But complex URLs like the "let me log into http://forum.porteus.org and then show me the most recent of my "subscribed" threads" can be messed up by a seemingly innocent / at the end.
Of course the user can simply edit the homepage URL in settings and remove the / at the end.
But a user usually wants his/her modules to work as intended from the stand and not having every time when used in a fresh environment to be fixed. Again. And again.
So please, if the added "/" is indeed a bug in update-firefox-live please fix that bug.