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

[Import Maps] Remove Blink internals dependency from WPT/import-maps/common #20601

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

Quick draft.

Note:

https://web-platform-tests.org/writing-tests/testdriver-extension-tutorial.html
provides two methods, testdriver-vendor.js and testdriver-extra.js.
I'm not sure which method to use, but in this CL
I used testdriver-vendor.js method, because

  • It was easier to implement.
  • So far the API is expected only for testing and not needed to be
    exposed for automation.

This CL contradicts with:
https://web-platform-tests.org/writing-tests/testdriver.html

NB: presently, testdriver.js only works in the top-level
test browsing context (and not therefore in any frame or
window opened from it).
because test_driver is accessed from inside \<iframe>s
in this CL.
Perhaps this is OK in this case, as the resolve_module_specifier
implementation works inside <iframe>s, while other test_driver
method might stop working there.

Bug: 1026809, WICG/import-maps#170
Change-Id: I8684ec544382e3036b9885e09f0c3a4d97208da5

Reviewed-on: https://chromium-review.googlesource.com/1949446
WPT-Export-Revision: 5a6d0d7336883a8295304a7fee02dce100647078

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

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

The review process for this patch is being conducted in the Chromium project.

…common

Quick draft.

Note:

https://web-platform-tests.org/writing-tests/testdriver-extension-tutorial.html
provides two methods, `testdriver-vendor.js` and `testdriver-extra.js`.
I'm not sure which method to use, but in this CL
I used `testdriver-vendor.js` method, because

- It was easier to implement.
- So far the API is expected only for testing and not needed to be
  exposed for automation.

This CL contradicts with:
https://web-platform-tests.org/writing-tests/testdriver.html
> NB: presently, testdriver.js only works in the top-level
> test browsing context (and not therefore in any frame or
> window opened from it).
because `test_driver` is accessed from inside `<iframe>`s
in this CL.
Perhaps this is OK in this case, as the `resolve_module_specifier`
implementation works inside <iframe>s, while other `test_driver`
method might stop working there.

Bug: 1026809, WICG/import-maps#170
Change-Id: I8684ec544382e3036b9885e09f0c3a4d97208da5
@gsnedders gsnedders closed this Jan 24, 2020
@gsnedders gsnedders deleted the chromium-export-cl-1949446 branch January 24, 2020 18:04
@gsnedders gsnedders restored the chromium-export-cl-1949446 branch January 24, 2020 18:40
@Hexcles Hexcles reopened this Jan 24, 2020
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.

None yet

5 participants