Skip to content
This repository was archived by the owner on Feb 16, 2024. It is now read-only.

Conversation

@mathiasbynens
Copy link
Member

This would be useful to reference in integration PRs like whatwg/html#7908.

@ljharb
Copy link
Member

ljharb commented May 12, 2022

A prose summary of this would be awesome to include non-normatively in the actual spec as well, kind of like Annex E (but obv nonbreaking).

Co-authored-by: Markus Scherer <[email protected]>
@mathiasbynens mathiasbynens requested a review from markusicu May 18, 2022 15:29
Copy link
Collaborator

@markusicu markusicu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm tnx!

@mathiasbynens mathiasbynens merged commit 3121c45 into main May 18, 2022
@mathiasbynens mathiasbynens deleted the faq-v-vs-u branch May 18, 2022 16:32
[>>]
[??]
[@@]
[^^]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gibson042 @markusicu @macchiati @pthier Is /[^^]/v actually an error? I noticed the current V8 implementation allows it.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO it isn't, as the first ^ is consumed by the production CharacterClass :: [ ^ ClassContents ], so the remaining ^ is not a reserved double punctuator. [^^^] is an error in V8.
Note that also []] is not a breaking change, as this is an error also with /u.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess [_^^] or, indeed, [^^^] is a better example. I’ll change this. Thanks!

[]] is currently not listed as a breaking change, so I think there’s no action to be taken for that one. Let me know if I misunderstood.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR: #74

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants