FF - Classic Theme Restorer may be dead by the end of 2017  


  1. Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #1

    FF - Classic Theme Restorer may be dead by the end of 2017


    It looks like Mozilla have resumed their quest to make Firefox totally irrelevant.
    Mozilla announced a couple of days ago that it plans to make Firefox support only WebExtensions add-ons by the end of 2017.

    While that seems far far away right now, it is almost certain that things won't be ready by then. What I mean by that is that WebExtensions capabilities won't match those of Firefox's current system.

    While popular add-ons like NoScript will likely be ported over thanks to Mozilla working with developers actively on implementing missing API features, the same cannot be said for other add-ons.

    Soon there won't be even a single usable browser left.
    The latest Pale Moon (27) is horrible on my PC (takes at least 10 seconds to load).
    God only know how long it would take if you tried to run it from a HDD.

    Seems like Google has "won the Internet" and everyone will be forced to use the abomination that is Chrome.
      My Computer


  2. Posts : 287
    win 10 home
       #2

    It took no more than 2 seconds (HDD) for Pale Moon (27) to start. It is still a work in progress, limping along because of the lack of prioritized support from the addon community. Mozilla and Firefox with the larger user base get first dibs.

    We'll just have to move the goalposts on Google's inevitable browser conquest.
      My Computer


  3. Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
    Thread Starter
       #3

    Add-on Issues


    pyramid10 said:
    It took no more than 2 seconds (HDD) for Pale Moon (27) to start.
    It turns out that add-on compatibility issues caused the long start up time.

    My PM now starts in ~2 seconds. :)
      My Computer


  4. Posts : 2,341
    Win 11 x 64 Home on PC and Win 10 Pro x 64 on Surface 5.
       #4

    As far as I am concerned FF can die right now. The browser refused to close, open in background. I had to sign out and back in again to open it.
      My Computer


  5. Posts : 824
    Win10/64 Pro 1511 (and 2 Win 7/64 Ult & Pro systems)
       #5

    Hi:

    elbmek said:
    As far as I am concerned FF can die right now. The browser refused to close, open in background. I had to sign out and back in again to open it.
    This thread pertains to CTR, a particular Fx extension, and changes coming to Fx programming (rather than to trouble-shooting).

    Having said that, most Fx performance problems originate in the user's profile, not in the program itself.
    There are myriad reasons for this (e.g. extensions -- old, conflicting, broken; settings/configuration/preferences; hardware/networking problems; global plug-ins; accumulated temp files; security software conflicts; even malware; etc.).

    There are several well-written, well-organized tutorials that detail diagnostics and troubleshooting steps.
    They range from purely "debugging" (such as Mozilla Safe Mode), to creating a new profile, to wiping out everything and starting from scratch (rarely necessary).

    I suggest starting here:

    Troubleshoot and diagnose Firefox problems



    HTH

    MM
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:55.
Find Us




Windows 10 Forums