Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 10 submissions in the queue.
posted by chromas on Wednesday August 22 2018, @01:28AM   Printer-friendly
from the burn-the-bridges dept.

Mozilla plans to remove all legacy add-ons from their portal.

Support for Firefox ESR 52 will end on September 5, in two weeks, meaning there won't be any official Firefox version that supports legacy add-ons anymore.

Mozilla said today that following this date, it plans to start the process of disabling legacy add-on versions on its add-ons portal located at addons.mozilla.org (also known as the AMO).

"On September 6, 2018, submissions for new legacy add-on versions will be disabled," said Caitlin Neiman, Add-ons Community Manager at Mozilla.

"All legacy add-on versions will be disabled in early October, 2018. Once this happens, users will no longer be able to find [extensions] on AMO," she added.

Isn't modern FOSS great?/s

I can run old Blender if I need. Or go over all the archived .deb from past Debian releases. But Mozilla seems to be special. Time to call the Archive Team or the Wayback Machine.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Insightful) by ShadowSystems on Wednesday August 22 2018, @04:59AM (7 children)

    by ShadowSystems (6185) <reversethis-{moc ... {smetsySwodahS}> on Wednesday August 22 2018, @04:59AM (#724558)

    I agreed with you right up until you suggested PaleMoon.
    The PaleMoon team *intentionally removed the Accessibility subsystem* & has no intention of ever putting it back.
    I asked them why & was told it made the code cleaner, leaner, & more secure.
    I let them know that by doing so they were shooting themselves in the foot.
    They. Didn't. Care.
    So PaleMoon is a non-starter, non-option, non-functional pile of festering, rancid, Satan's scrotum scrapings.

    FF ESR 52 is what I'm using as it's the only version of FF that is compatible with my screen reader.
    Any newer version of FF ESR screams about my screen reader being incompatible (& FF ESR 52+ is the *only* program to ever claim that) & thus refuses to run worth a damn.
    If I want to use my screen reader (and I can not use a computer without one) then my choices are Internet Explorer 11 or FF ESR 52.
    I don't know what Mozilla thinks they're doing, but unless/until they release an ESR that *does* work with a screen reader, I'll be stuck on this old & no longer secure version.

    Starting Score:    1  point
    Moderation   +2  
       Insightful=1, Interesting=1, Total=2
    Extra 'Insightful' Modifier   0  

    Total Score:   3  
  • (Score: 2) by maxwell demon on Wednesday August 22 2018, @05:37AM (1 child)

    by maxwell demon (1608) on Wednesday August 22 2018, @05:37AM (#724563) Journal

    Did you try Waterfox? (Honest question; I don't have any idea about if it would work.)

    --
    The Tao of math: The numbers you can count are not the real numbers.
  • (Score: 2) by FatPhil on Thursday August 23 2018, @12:13AM (4 children)

    by FatPhil (863) <pc-soylentNO@SPAMasdf.fi> on Thursday August 23 2018, @12:13AM (#724950) Homepage
    Can we talk accessibility issues, please? I'm trying to create a clone of a website that I've used for a decade but which has turned to shit (fuck betas, one might say), and I want accessibility to be one of the features I don't compromise. If you join the soylent IRC server, I normally have this nick (when the nickserv hasn't stripped it from me, the bastard).
    --
    Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
    • (Score: 1) by ShadowSystems on Thursday August 23 2018, @12:37AM (3 children)

      by ShadowSystems (6185) <reversethis-{moc ... {smetsySwodahS}> on Thursday August 23 2018, @12:37AM (#724966)

      I'd love to join folks on IRC, but there's a problem with that.
      My screen reader doesn't play well with anything that updates in real time - every refresh of the screen (every time someone posts a message) causes my 'reader to reread the. entire. screen.
      There's never any way to jump to the last post I was in the middle of hearing about when the screen refreshed, I can't just Control+End to the end of the page & cursor up to find that message because there may be HUNDREDS of new messages in the time it takes me to do it, & the only way I have to keep track is to listen to the log files after the fact.
      It's like trying to enjoy a tennis game running at 120KHz when your brain is only doing 30FPS.
      By the time you've seen something & can react to it, the situation is so old as to make your input irrelevant.
      *Comical pout & sigh*

      The easiest way is either a forum like this one or via email.
      I can actually keep up & my 'reader doesn't go haywire with all the refreshing.
      =-J

      • (Score: 0) by Anonymous Coward on Thursday August 23 2018, @04:17AM (2 children)

        by Anonymous Coward on Thursday August 23 2018, @04:17AM (#725065)

        Out of curiosity, what screen reader do you use? I know plenty of people that use IRC clients with screen readers. If I remember, I'll ask them what they use for both the reader and IRC client.

        • (Score: 1) by ShadowSystems on Thursday August 23 2018, @06:10PM (1 child)

          by ShadowSystems (6185) <reversethis-{moc ... {smetsySwodahS}> on Thursday August 23 2018, @06:10PM (#725317)

          Win7Pro64 & Jaws 16 from Freedom Scientific.
          Thank you! =-)

          • (Score: 0) by Anonymous Coward on Friday August 24 2018, @03:21AM

            by Anonymous Coward on Friday August 24 2018, @03:21AM (#725581)

            Ok, I asked a buddy of mine and he said that there are two main paths people take when on Windows. Now this is coming off my memory from talking to him, so it may not be completely accurate in paraphrase. The first is ChatZilla, an extension for Firefox. It plays nicer with JAWS and most other screen readers than most clients you will use. The problem is that some users are getting nervous because of the EOL of Firefox ESR 52, which not only kills ChatZilla but Quantum doesn't play as nicely with screen readers in some aspects. Another browser based one he did say that qWebIRC (and another one whose name he couldn't remember) can play nicely with JAWS, if the web interface uses that and the IRC admins properly set it up. However, that is not true of every web based one.

            Instead, he recommends the second option. He says you should try mIRC and one of the sub-options. First is that mIRC plays pretty nicely with JAWS out of the box. Second and the one he uses because he can see basic shapes, set JAWS to ignore mIRC completely and use its built-in reader, which allows him to still interact with mIRC and have it in the background reading things off while doing other things that don't require the screen reader and voice commands. Third, is to use JAWS as your registered speech component, to better integrate them. Fourth, is that there are plenty of FLOSS mIRC plugins (scripts?, addons? I'm not sure the lexicon) that allow it to play nicer with JAWS.

            Another suggestion he made was using IRSSI. Apparently the TUI plays nice with JAWS. The final note he gave was that it has been a few years since he searched and got his setup, so everything I told you could be wrong or out of date. There is probably some accessibility group somewhere with suggestions that he missed.