Going faster than browsers in corporate environments (e.g., Firefox ESR)

[mkovatsc]

I understand that hardcore Web guys like to change specifications every day. However, it gets a bit impractical when adopting features that cannot be used in corporate environments that use modern browsers, but rely on something like the Extended Support Release branch.

Concretely, I am talking about insertAdjacentElement(), which is not supported on Firefox's ESR update channel. All current ReSpec documents are currently broken there.

I hope you understand that this is a problem for corporations, who in turn are the Members writing W3C documents in ReSpec.

Let me know if I have to open a separate issue for insertAdjacentElement() -- however, the new ESR cycle might start before that can be fixed. The issue is more fundamental...

[marcoscaceres]

Pull requests are welcomed to fix legacy browser support issues.

[mkovatsc]

Well, if Firefox ESR is legacy, I think you have to sort something out with Mozilla...
Also, I recommend not to merge some if-then-else soup for "legacy browser support issues".
My point is to adopt new features once they are stable in the products of the WHATWG club.

It might also help not to break all W3C specifications instantly, but have some kind of release management for ReSpec. If ReSpec is not for W3C documents, we need to look for a new tool.

[marcoscaceres]

I'm planning on adding polyfills via Babel preset env (last 2 browser version soon). That's probably the best I can do tho.

[marcoscaceres]

I think there is a new ESR for firefox - all new features should work. https://www.mozilla.org/en-US/firefox/52.0esr/releasenotes/

Also checked, insertAdjacentElement() is supported in all browsers, including ESR 52.

[mkovatsc]

Okay, thank you. I hope you understand where this is coming from. I appreciate it very much to have a tool like this!

[halindrome]

FWIW Matthias everyone is committed to having the toolchain work in as broad a set of environments as practical.

…

On Wed, Mar 15, 2017 at 11:39 AM, Matthias Kovatsch < ***@***.***> wrote: Okay, thank you. I hope you understand where this is coming from. I appreciate it very much to have a tool like this! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1159 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAfx8EKTr3LMJR5ha6kLCpXJU-ZUBDA7ks5rmBRRgaJpZM4MeHAg> .

-- Shane McCarron halindrome@gmail.com

[mkovatsc]

Yes, but there was a gap. I just wanted to make you aware of this issue.

[marcoscaceres]

I'll see if I can get Travis to run tests against ESR.

[marcoscaceres]

Trivial to do: https://docs.travis-ci.com/user/firefox/

[marcoscaceres]

I'll get this set up tomorrow - but wont run against 45. It will be against 52 for the next year.

[mkovatsc]

Thanks a lot!

[marcoscaceres]

So ESR is a bit of a s***show. The wrong version was being served by Mozilla (had that fixed) ... and what is in 52 ESR doesn't seem to match 52 stable. Totally weird. Will investigate a bit, but it seems Mozilla is not really taking ESR very seriously.

[marcoscaceres]

Trying this one last time: #1253

[marcoscaceres]

Seems ESR is still a pile of garbage - it doesn't behave the same as 52. Sorry, won't be able to support it because I won't be able to test on it. Will try again in a year or so.