-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dom: set composed flag when constructing ClipboardEvent
#35146
Conversation
Clipboardevent
ClipboardEvent
Why were the clipboard api test expectations not required before? |
Signed-off-by: Gae24 <[email protected]>
7167a72
to
c01c543
Compare
Forgot to add them in #33576. I'm not sure if test were actually run, |
Adding the clipboard api tests to |
Signed-off-by: Gae24 <[email protected]>
c01c543
to
049d813
Compare
🔨 Triggering try run (#12932344194) for Linux (WPT) |
Test results for linux-wpt-layout-2020 from try job (#12932344194): Flaky unexpected result (16)
Stable unexpected results that are known to be intermittent (16)
|
✨ Try run (#12932344194) succeeded. |
* clipboardevent: set composed flag Signed-off-by: Gae24 <[email protected]> * add clipboardevent test expectations Signed-off-by: Gae24 <[email protected]> --------- Signed-off-by: Gae24 <[email protected]> Signed-off-by: L Ashwin B <[email protected]>
Accessing composed flag is enough for clipboardevent interface, and documentation does not mention the steps outlined in #35124.
Added clipboard api test expectations
./mach build -d
does not report any errors./mach test-tidy
does not report any errors