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] Make null entries be ignored instead of causing errors #21050

Closed
wants to merge 1 commit into from

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jan 6, 2020

This CL makes null entries, i.e. mappings to null, [], invalid URLs,
etc., be ignored, while previously they caused an error.

Built-in-modules-enabled cases:

The tests for built-in-modules-enabled cases are based on an old version
of the spec where null entries should cause errors.
This CL changes the tests so that null entries are ignored.

Associated spec updates for this change is not needed for now,
because the built-in modules support is tentatively dropped from the spec.

Built-in-modules-disabled cases:

The new behavior is already conformant with the current spec and WPT tests.

Bug: 990561, WICG/import-maps#184
Change-Id: I3ce416adc9b9145b7fae8d9a22973698bd632f7e

Reviewed-on: https://chromium-review.googlesource.com/1986653
WPT-Export-Revision: 16d4743f1a586050f5f2828672412b1dc1577d63

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.

This CL makes `null` entries, i.e. mappings to `null`, `[]`, invalid URLs,
etc., be ignored, while previously they caused an error.

Built-in-modules-enabled cases:

The tests for built-in-modules-enabled cases are based on an old version
of the spec where `null` entries should cause errors.
This CL changes the tests so that `null` entries are ignored.

Associated spec updates for this change is not needed for now,
because the built-in modules support is tentatively dropped from the spec.

Built-in-modules-disabled cases:

The new behavior is already conformant with the current spec and WPT tests.

Bug: 990561, WICG/import-maps#184
Change-Id: I3ce416adc9b9145b7fae8d9a22973698bd632f7e
@gsnedders gsnedders closed this Jan 24, 2020
@gsnedders gsnedders deleted the chromium-export-cl-1986653 branch January 24, 2020 18:05
@gsnedders gsnedders restored the chromium-export-cl-1986653 branch January 24, 2020 18:46
@Hexcles Hexcles reopened this Jan 24, 2020
@KyleJu
Copy link
Contributor

KyleJu commented Apr 10, 2024

Close this PR because the Chromium CL cannot be found.

@KyleJu KyleJu closed this Apr 10, 2024
@KyleJu KyleJu deleted the chromium-export-cl-1986653 branch April 10, 2024 00:41
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.

6 participants