[opensuse-factory] firefox-esr repo location;; reduced FF feature set
Why is it in experimental instead of main (as is for 12.3), or legacy? 12.3 has current 17.0.8 available, while "experimental" only has very much older 17.0.4. Recent FF versions keep losing features. "Always show the tab bar" has been purged in furtherance of dumbing Firefox down to Chrome/IE level. Disabling of JS has been obscured into devel tools somewhere. Proper calculation of DPI on http://fm.no-ip.com/Auth/dpi-screen-window.html has been broken at least partly at least since v21. Such things still work in esr. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 9 Sep 2013 00:58, Felix Miata
Why is it in experimental instead of main (as is for 12.3), or legacy?
12.3 has current 17.0.8 available, while "experimental" only has very much older 17.0.4.
Recent FF versions keep losing features. "Always show the tab bar" has been purged in furtherance of dumbing Firefox down to Chrome/IE level. Disabling of JS has been obscured into devel tools somewhere. Proper calculation of DPI on http://fm.no-ip.com/Auth/dpi-screen-window.html has been broken at least partly at least since v21. Such things still work in esr.
About dpi calculation: The property "layout.css.dpi" has gotten a "new" default of -1 (minus one) instead of the "old" default which was either 1 (one) or 0 (zero). Have a look at the property on about:config (search for dpi) in esr, take that value and set it manually in new fx. Then it works as before. About "Disable JS" The obscured "Disable JS" has some more background on why in bugzilla.mozilla.org, and was a long and hard debabate. End of the song: To many stupids disable JS and cry loud and long that "The internet does not work with Firefox", as we (mozilla) can't fix stupid, we have to take away the easy way to disable JS in Firefox. Either use and addon (e.g. Noscript, Yesscript, QuickJS, JS Switch, JSOff,...) or the internal devel-tools. Hope this give a little info about the why and how inside Firefox. On the versions in the repo, that can answer the maitainer much better than I ever could, thus I keep my gob shut about it. - Yamaban -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-09-09 08:07 (GMT+0200) Yamaban composed:
Felix Miata wrote:
Why is it in experimental instead of main (as is for 12.3), or legacy?
12.3 has current 17.0.8 available, while "experimental" only has very much older 17.0.4.
Recent FF versions keep losing features. "Always show the tab bar" has been purged in furtherance of dumbing Firefox down to Chrome/IE level. Disabling of JS has been obscured into devel tools somewhere. Proper calculation of DPI on http://fm.no-ip.com/Auth/dpi-screen-window.html has been broken at least partly at least since v21. Such things still work in esr.
About dpi calculation: The property "layout.css.dpi" has gotten a "new" default of -1 (minus one) instead of the "old" default which was either 1 (one) or 0 (zero).
Excerpts from my user.js: user_pref("layout.css.dpi", 0); // max(96dpi, System setting) user_pref("layout.css.devPixelsPerPx", 1.0); // valid increments .1 Any time I create a new profile these get applied in short order. I can't say how long I've had the latter in it, but feel safe in saying for more than a year. In a world in which a Linux distribution that takes 8 months to build expires well under two years afterward, this change is nearly ancient. Actually, upstream at least, layout.css.dpi has defaulted to -1 since it was born to replace browser.display.screen_resolution, which via https://bug233082.bugzilla.mozilla.org/attachment.cgi?id=208927 changed browser.display.screen_resolution from 0 to -1, which layout.css.dpi inherited just over 7.5 years ago on 2006-02-28: https://bugzilla.mozilla.org/show_bug.cgi?id=327406
Have a look at the property on about:config (search for dpi) in esr, take that value and set it manually in new fx. Then it works as before.
I noticed less than 48 hours ago that sometime after rv20, dpi 0 and/or devPixelsPerPx 1.0 stopped working right, and haven't yet had time to pin down when or investigate why: http://fm.no-ip.com/SS/Moz/ff23badder.png
About "Disable JS" The obscured "Disable JS" has some more background on why in bugzilla.mozilla.org, and was a long and hard debabate. End of the song: To many stupids disable JS and cry loud and long that "The internet does not work with Firefox", as we (mozilla) can't fix stupid, we have to take away the easy way to disable JS in Firefox. Either use and addon (e.g. Noscript, Yesscript, QuickJS, JS Switch, JSOff,...) or the internal devel-tools.
I knew this months ago. Stupids, the same group that was responsible for causing pixels to equate to points, effectively eliminating absolute units except for limited cases handled via the Mozilla proprietary mozmm unit, or for those using old browser versions, or those using Konq configured to use KHTML instead of WebKit.
Hope this give a little info about the why and how inside Firefox.
And some reasons to prefer Konq or SeaMonkey to Chrome or Firefox. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Felix Miata
-
Yamaban