-
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
Request upload: test synchronous feature detect #36048
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code itself looks good to me, but I am not sure if this will actually have the intended outcome, as the implementer may just see this as "just another test failure for an unimplemented feature".
I can't think of anything better, and it definitely does not do any harm, so let's just land it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me modulo nit.
assert_true(duplexAccessed, `duplex dictionary property should be accessed`); | ||
}, "Synchronous feature detect"); | ||
|
||
// The asserts the synchronousFeatureDetect isn't broken by a partial implementation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// The asserts the synchronousFeatureDetect isn't broken by a partial implementation. | |
// This asserts the synchronousFeatureDetect isn't broken by a partial implementation. |
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot about this nit... Maybe fix in a follow-up?
FWIW, I suspect as part of implementing Fetch features WebKit would sync |
Oversight of #1457. Tests: web-platform-tests/wpt#36051 & web-platform-tests/wpt#36048. Closes #1486.
Discussion: WebKit/standards-positions#24 (comment)