it looks like devs started to use it in the wild without fallback :(
steamcommunity.com - Page doesn't load after signing into Steam account · Issue #51385 · webcompat/web-bugs
ES2018 regex has landed in the beta channel of FF (https://bugzilla.mozilla.org/show_bug.cgi?id=1225665) due out end of June 2020. That'll mean Chrome, Edge, and FF support it but Safari still does not.
I actually used it for a neo.mjs viewmodel regex and just got a heads up that dist/prod builds no longer work in safari due to this =/
Well, at first I got a report "breaks on mobile" => did not get a JS error inside my remote debugging tools, but luckily it is reproducable on desktop.
Adding this feature would be highly appreciated!
As somebody who uses lookbehind in regex for a lot of my code, I would like to show my strong support for the resolution of this issue. Considering that all modern browsers -- save for Safari/WebKit -- support regex lookbehind, as a web developer, I find it frustrating that WebKit is the only modern browser engine which does not support this.
Which, at the moment, means that I unfortunately must resort to excluding those who use Safari/WebKit browsers from accessing some of my projects, and by extension, those who use iOS/iPadOS devices too (since the use of WebKit in any web browser is unfortunately mandatory).
From the report date, this issue has been around since 2017, so it is coming up to the 4-year anniversary of this issue existing, as of the time of writing. I hope that by giving my remarks on this issue, the WebKit developers take notice and implement this feature which really should have been added in some time ago.
According to earlier comments, it seems that many major platforms have used regex lookbehind, which completely renders sites unusable for iOS users. Though I am not an iOS, iPadOS or macOS user myself (in part because of my views on Apple's App Store browser engine policy), I would like to see this change so that iOS/iPadOS users in particular can enjoy not just my services, but others' services too.
If this issue is being worked on as we speak, I would like to therefore thank the WebKit developers in doing so.
*** Bug 226465 has been marked as a duplicate of this bug. ***