[RegExp] Incomplete sticky flag support implementation / core-js@3.6+ breaks xregexp@4.3- patterns on IE11

[psmyrdek]

Related to: angular/angular-cli#17375

There are two issues with XRegExp and core-js I noticed recently:

1) On core-js@3.6.4 this script causes endless loop:

import 'core-js/features/regexp';
import XRegExp from 'xregexp';
window['XRegExp'] = XRegExp; // only to test some patterns in dev tools console

When using core-js@3.5.0 everything works fine.

2) Pattern that is working fine in core-js@3.5.0 now breaks (the \s, whitechar range, is gone)

I'm trying to test the following code:

import XRegExp from 'xregexp';
window['XRegExp'] = XRegExp;

console.log(XRegExp('(^((?=[uuuuuuuuu\\sxxxxxxxxx\\p{L}\\p{N}\\p{P}\\p{S}\\p{M}/])[^;\\\\<>{}])*$)|(^$)'))
console.log(XRegExp('(^((?=[uuuuuuuuu\\sxxxxxxxxx\\p{L}\\p{N}\\p{P}\\p{S}\\p{M}/])[^;\\\\<>{}])*$)|(^$)').test('test me'));

Both uuu... and xxx... added only to see effects in the browser)

And I see two different regexp patterns that got built by xregexp:

core-js@3.5.0 - spaces work fine

core-js@3.6.4 - spaces break the pattern (notice lack of x chars and \s at the beginning)

[kassenov]

We experienced the described issue on IE11 with version 3.6, when reverted to 3.5.0 it works.

[psmyrdek]

One solution may be to use https://www.npmjs.com/package/babel-plugin-transform-xregexp and build patterns in build time. Haven't tested it properly yet - feedback welcomed.

[walkerdb]

Seeing the same issue as well

[steveworkman]

Looks like a duplicate of #751

[kabbany]

Still having the same issues. Any updates regarding the issue ?

[zloirock]

Seems on xregexp side added a workaround, but it should be fixed on core-js side.

[zloirock]

#754 related

[gtranter]

I'm facing the same issue as part of Stencil JS development which currently includes core-js@3.6.5. When will this bug be fixed?

[zloirock]

@gtranter when someone will fix it. Working on it is not in my plans.

[Yevgeniy-C]

Update:
The retired, out-of-support Internet Explorer 11 desktop application has been permanently disabled through a Microsoft Edge update on certain versions of Windows 10.

IE11 visual references, such as the IE11 icons on the Start Menu and taskbar,
will be removed by the June 2023 Windows security update (“B” release) scheduled for June 13, 2023.

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/internet-explorer-11-desktop-app-retirement-faq/ba-p/2366549

Probably time to close this issue since they killed IE11 this month with new update.

[zloirock]

@Yevgeniy-C here this approach does not work - a couple of times a month someone writes me even about IE6 support. In core-js@4 will be removed IE8- support - but most likely IE9-11 still will be supported. Also, it's related to other old engines.

[Yevgeniy-C]

I thought that Microsoft forced users to delete IE and switch to edge with new update this month. Not just stopped supporting but actually deleted IE on users computers.

…

On Sun, Feb 26, 2023, 9:57 AM Denis Pushkarev ***@***.***> wrote: @Yevgeniy-C <https://github.com/Yevgeniy-C> here this approach does not work - a couple of times a month someone writes me even about IE6 support. In ***@***.*** will be removed IE8- support - but most likely IE9-11 still will be supported. Also, it's related to other old engines. — Reply to this email directly, view it on GitHub <#810 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPRQ5FNHHFH7SDISLGWVETWZN4PZANCNFSM4MG4B6XA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zloirock]

@Yevgeniy-C it's problematic to delete it from PCs that do not receive actual updates - I'm pretty sure that it's most IE users. 0.7% according to current data is a fairly large share of users. A share of other ancient engines (iOS, Android, etc) without the support of this feature is comparable. CanIUse shows that it's about 4.17% at all.