Skip to content
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

Update the staticrange IDL file #11816

Conversation

lukebjerring
Copy link
Contributor

Hello reviewer(s),

This PR is intended to consolidate the spec’s IDL definition with the WPT test suite’s copy, and any idlharness tests.

The up-to-date copy of the IDL file was automatically extracted from the reffy-reports repo (https://github.com/tidoust/reffy-reports/tree/master/whatwg/idl) which scrapes known specs automatically + regulary.

This PR is part of a migration project which will eventually be automatically updating and creating PRs for changes in spec IDL.

Please check that:
The spec (and its source) is correct and up-to-date
All tests which cover the IDL in the spec have been migrated to fetch + use the idl in the interfaces/ directory (instead of inline copies in the test files).

@lukebjerring
Copy link
Contributor Author

lukebjerring commented Aug 2, 2018

(Hearsay:) Sounds like this has been merged into DOM.

w3c/staticrange#16

foolip added a commit to foolip/reffy that referenced this pull request Aug 2, 2018
This is to avoid it propagating to idlharness.js tests in wpt:
web-platform-tests/wpt#11816

(The dom.idl in wpt is from https://dom.spec.whatwg.org/, which defines
StaticRange slightly differently, so it would be impossible to pass
tests for both.)
tidoust pushed a commit to w3c/reffy that referenced this pull request Aug 5, 2018
This is to avoid it propagating to idlharness.js tests in wpt:
web-platform-tests/wpt#11816

(The dom.idl in wpt is from https://dom.spec.whatwg.org/, which defines
StaticRange slightly differently, so it would be impossible to pass
tests for both.)
@lukebjerring lukebjerring deleted the idl-file-updates-staticrange branch October 5, 2018 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants