Skip to content

Allow overlapping BCD keys without creating ambiguity #1173

@foolip

Description

@foolip

#1164 was caused by javascript.statements.import being part of both CSS modules and JS modules. In this situation, looking up a feature by BCD key finds two features, so consumers need something more to determine the status of javascript.statements.import.

The <source> element is a good illustration of the problem. The <audio> and <video> elements aren't yet in web-features, but if we add them, it would make sense for the <source> element (and HTMLMediaElement interface) to be part of both features, which shipped at the same time. But the <source> element is also a part of the <picture> element which shipped much later. Rather than picking a feature which gets to claim each BCD key, it would be good if overlap was handled gracefully.

This also has implications for #979.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions