Update to WHATWG DOM Living Standard for Events #284
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(just trying to help triage stuff to help @mhegazy, but it is just my opinion) All of these changes were added ShadowDOM APIs and the changes reflect the current ShadowDOM standards, so I think 👍 |
|
Is there a reason this isn't being accepted? |
|
The input file format has changed since this PR was opened. please refresh the PR and reopen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Referencing this issue - microsoft/TypeScript#17974
WHATWG DOM Living Standard includes composed and composedPath properties instead of scoped and deepPath. This will allow proper syntax for a case like the following: