View Single Post
Old 11-04-2017, 11:42 AM   #31199
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by Katsunami View Post
Bah. Since the last update Firefox is behaving poorly. When starting or opening a tab, the mouse freezes until Firefox/tab has loaded. Then it freezes for a fraction of a second while the page loads. On my systems it only takes a second or so, but it's annoying.

<...>
Which version are you currently running, and under what OS?

I don't see that here. My desktop is a quad-core Intel based system at 3.1ghz, with 8GB RAM, under Win10 Pro. One bit that helps speed is that Firefox, and its profile, are on the SSD that is my boot drive.

Quote:
The only conclusion I can draw is that 'something' has changed in Mozilla's XUL framework.
XUL is deprecated and going away. Mozilla has been developing a new rendering engine they call Quantum, which they claim is up to twice as fast as Gecko.

This bites in various ways. One is extensions. Going forward, extensions must use the Web Extensions API, and be pure JavaScript. Extensions will be limited to what can be done using Web Extensions. The good part is that such extensions can be largely cross-browser, and installed in Chrome or MS Edge as well as FF with minor code changes. The bad part is that most existing extensions will be broken.

I have about 40 extensions installed in Firefox, and all will stop working in FF 57. Some of my standard kit is implemented in XUL and JavaScript, and I've already gotten notices from developers saying "Sorry, but development is ended. What my extensions do can't be done in just JavaScript using the WebEx API."

I backed off to a Firefox ESR release (which is currently based on v52.4) for production use. I have a test profile I use with Firefox Developer Edition that uses only FF 57 compatible extensions to track progress in replacements for my current kit. See http://arewewebextensionsyet.com/#addons for a current progress list. Most of what has been converted is stuff I never used in the first place. See https://addons.mozilla.org/en-US/fir...?tag=firefox57 for extensions that are FF 57 compatible.)

I have current versions of other things like Chrome and Edge installed to track browser development, but I'm in a position where Firefox increasingly looks and acts just like Chrome, leading to the question "Why continue to use Firefox? Bite the bullet and just run Chrome." (Edge is actually usable, but I spend time in Linux, too, and need a browser that runs in both environments.)
______
Dennis
DMcCunney is offline   Reply With Quote