Implement RegExp Unicode Property Escapes

NEW
Unassigned

Status

()

P1
normal
a year ago
a month ago

People

(Reporter: leonardo.balter, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 2 bugs, {dev-doc-needed, parity-chrome, parity-safari})

unspecified
dev-doc-needed, parity-chrome, parity-safari
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox60 wontfix, firefox61 wontfix, firefox62 fix-optional, firefox63 affected)

Details

(URL)

(Reporter)

Description

a year ago
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.
Keywords: dev-doc-needed
(Reporter)

Comment 1

a year ago
The skip list is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1362169

Updated

a year ago
Depends on: 1367105

Updated

a year ago
Duplicate of this bug: 258974

Updated

11 months ago
Depends on: 1415827
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.
Blocks: 1435795

Updated

8 months ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 1435799
Waldo, can you need-info the right person to address this issue?
status-firefox60: --- → affected
Flags: needinfo?(jwalden+bmo)
Priority: -- → P1
No longer blocks: 1435799

Comment 5

8 months ago
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).
Flags: needinfo?(andrebargull)
This was supported in Chrome 64 and now on Safari 11.1.  Maybe some "parity" tags should be added here.
Blocks: 1435799
No longer blocks: 1435795

Updated

2 months ago
Duplicate of this bug: 1476622
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.