Closed Bug 1315221 Opened 8 years ago Closed 8 years ago

Regex special-casing removed from WebIDL

Categories

(Firefox :: Untriaged, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1315135

People

(Reporter: tobie.langel, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce:

Heads-up that we've stopped special casing Regexp in the WebIDL spec as of
https://github.com/heycam/webidl/commit/bbb2bde

Here's a diff of what that looks like in the rendered HTML spec:
[diff]: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fcdn.rawgit.com%2Fheycam%2Fwebidl%2F001ba52%2Findex.html&doc2=https%3A%2F%2Fcdn.rawgit.com%2Ftobie%2Fwebidl%2F00b9786%2Findex.html

That means that the following algorithms now allow regexes in places where they previously didn't:

1. to convert an ES value to a dictionary: https://heycam.github.io/webidl/#es-dictionary
2. to convert an ES value to a sequence: https://heycam.github.io/webidl/#es-sequence
3. to convert an ES value to a union type (step 5 and 11): https://heycam.github.io/webidl/#es-union
4. the substeps of step 11 of the overload resolution algorithm: https://heycam.github.io/webidl/#es-overloads

There are also some modifications to the section on User objects implementing callback interfaces:
https://heycam.github.io/webidl/#es-user-objects

I opened an issue against web-platform-tests's testharness to account for these changes:
https://github.com/w3c/testharness.js/issues/223

Please raise any concerns by opening an issue against the spec:
https://github.com/heycam/webidl/issues/new

Thanks.
Tobie, thank you for filing this!

In the future, can you file IDL-related bugs in Core:DOM and cc me?
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
(In reply to Boris Zbarsky [:bz] (still a bit busy) from comment #1)
> Tobie, thank you for filing this!
> 
> In the future, can you file IDL-related bugs in Core:DOM and cc me?

Sure.
You need to log in before you can comment on or make changes to this bug.