BrowserStack recommends switching to Chrome … So they’ve given up on porting their old Firefox add-on to the new WebExtensions API? @browserstack Could you update the message with more accurate information?
2
6
sounds pretty lame :/ why not update extension?
1
I’m sure they’ll do it eventually. This is probably a matter of priorities, and their message is just bad wording.
1
In their defense, if you break stuff with no transition period it's a valid statement. It would be like us removing ActiveX with no IE11 in box. So technically what they're saying is true.
3
Also, the add-on issue is one of the most common negative statements I'm seeing from customers regarding 57. A transition period probably would have been good.
1
Addons knew this was coming for more than a year. Previous releases also supported the new API. There was a long transition period already.
3
1
blog.mozilla.org/addons/2015… was nearly 27 months ago, though didn't yet have an exact timeline.
1
2
It's not about length of time, it's how much effort goes into building a bridge and helping people cross it.
2
1
1
Replying to @wycats @ManishEarth @gregwhitworth @simevidas @seesee @browserstack
I think @deadsquid and team have some a lot of good work on that.

Nov 21, 2017 · 3:30 AM UTC

1
1
Replying to @davidbaron @ManishEarth @gregwhitworth @simevidas @seesee @browserstack
I don't mean to impugn anyone's work. I just don't think avoiding this negativity was a priority. So here it is.
1