7 ms·
In this situation, grabbing a 3rd party JS regex library for a handful of kilobytes probably solves your problem, but I’m sure that crossed your mind. Is it re
by honkdaddy 4y ago
In this situation, grabbing a 3rd party JS regex library for a handful of kilobytes probably solves your problem, but I’m sure that crossed your mind.
Is it really as bad as the IE days though? I didn’t work on web back then, but these days if I run into a safari comparability issue, the workaround is usually pretty painless.
- SCLeo 4y agoI do not believe there is a 3rd party polyfill for lookbehind as it is quite tricky to implement regular expressions. If you found one, please let me know. Thanks in advance.
- ntoskrnl 4y agoThere's always this: https://xregexp.com/ https://xregexp.com/ But it's not really a polyfill, just a library.
- eyelidlessness 4y agoOn mobile and can’t tell whether xregexp still doesn’t have lookbehind, but in case it doesn’t I found this: https://github.com/beaugunderson/xregexp-lookbehind https://github.com/beaugunderson/xregexp-lookbehind
- tomgp 4y agoI did work on the web back in those days. The situation now is nothing like it was during IE's dominance in the early 2000s, to claim it is is hyperbole at best.
- RobertRoberts 4y agoYou are right, it's worse because the problem is more hidden and therefore a lot harder to solve. At least in the IE days everyone _knew_ IE was a problem, so we were looking for a solution as a community. Now? We comments that are dismissive of crap instead of inspiring towards quality.
- lern_too_spel 4y agoIn the IE days, you could tell the visitor to use Firefox. iOS does not allow such an easy fix.