User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce: Currently featured at TC39 as a Stage 3 proposal. https://github.com/tc39/proposal-regexp-unicode-property-escapes Test262 holds the tests with the `regexp-unicode-property-escapes` flag and in the `built-ins/RegExp/property-escapes/` folder. I'm updating the jstests.list to reflect all the matching test files.
The skip list is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1362169
This proposal was approved by TC39 and is now part of the ES2018 standard. It is already supported by current Chrome and by Safari TP.
Waldo, can you need-info the right person to address this issue?
status-firefox60: --- → affected
Priority: -- → P1
If Chrome and Safari already implement this, it's probable updating our irregexp import (which is being worked on now, in bug 1367105) will mean that (without too much hookup work) we'll just Get This Sort Of For Free. (There of course may be complexities involved in matching up their implementation approaches with the data we have available, for example if they implement this feature with a hard dependency on ICU -- a dependency we don't have when --without-intl-api.) Poking anba at this, although I'm not sure what exactly a needinfo here is going to do other than be mostly noise.
Flags: needinfo?(jwalden+bmo) → needinfo?(andrebargull)
(In reply to Jeff Walden [:Waldo] from comment #5) > (There of course may be complexities involved in matching up their > implementation approaches with the data we have available, for example if > they implement this feature with a hard dependency on ICU -- a dependency we > don't have when --without-intl-api.) Yes, it's going to be a hard dependency on ICU, so --without-intl-api won't get Unicode property escapes. Clearing NI because comment #5 exactly describes the current situation (requires irregexp update and then we get it basically for free).
7 months ago
This was supported in Chrome 64 and now on Safari 11.1. Maybe some "parity" tags should be added here.
This bug seems to be blocked on Bug 1367105.
status-firefox60: affected → wontfix
status-firefox61: --- → wontfix
status-firefox62: --- → fix-optional
status-firefox63: --- → affected
Keywords: parity-chrome, parity-safari
You need to log in before you can comment on or make changes to this bug.