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

[cssom][css-conditional][css-images] Switch CSS to use IDL namespace #437

Closed
wants to merge 1 commit into from

Conversation

zcorpan
Copy link
Member

@zcorpan zcorpan commented Sep 2, 2016

Web IDL added support for namespaces in
whatwg/webidl#121

elementSources in css-images-4 is commented out for now because
IDL namespaces don't support attributes yet, see #428.

Fixes part of https://www.w3.org/Bugs/Public/show_bug.cgi?id=29623


cc @bzbarsky @domenic @tabatkins @dbaron

Web IDL added support for namespaces in
whatwg/webidl#121

elementSources in css-images-4 is commented out for now because
IDL namespaces don't support attributes yet, see w3c#428.

Fixes part of https://www.w3.org/Bugs/Public/show_bug.cgi?id=29623
@bzbarsky
Copy link

bzbarsky commented Sep 2, 2016

The change seems fine. The question is which browsers are willing to try it to see whether it's web-compatible and whether we actually want to change the spec before such trials happen.....

@fantasai
Copy link
Collaborator

fantasai commented Sep 2, 2016

If Web-compat seems likely, then we should change the spec, and put a note that it may be reverted if Web-compat problems are found. If Web-compat seems unlikely, then maybe just put a note that we're in the process of trying this out and the spec may be updated if it ends up working.

@zcorpan
Copy link
Member Author

zcorpan commented Sep 3, 2016

Or maybe we can just wait with merging this until someone has tried to ship.

@fantasai
Copy link
Collaborator

Seems like an obscure approach, is the problem. This way it's documented where the feature itself is documented.

@tabatkins
Copy link
Member

I'm happy to merge this now with a note in CSSOM next to the definition that it's contingent on web-compat. Do you want me to just add that in and merge it, @zcorpan?

@zcorpan
Copy link
Member Author

zcorpan commented Nov 22, 2016

SGTM

@zcorpan
Copy link
Member Author

zcorpan commented May 30, 2017

Should add support for namespaces in web-platform-tests's idlharness.js and add an interfaces.html test for cssom (and cssom-view).

@bzbarsky
Copy link

That ended up with the wrong pull request number in the commit message... ah, well.

@bzbarsky
Copy link

@tabatkins Are there existing bugs reported against browsers for this?

@tabatkins
Copy link
Member

Looks like Chrome has one, at least https://bugs.chromium.org/p/chromium/issues/detail?id=727971

@bzbarsky
Copy link

That looks like the bug on supporting namespace at all, not for "CSS should be a namespace".

I guess the question is who is responsible for making sure that UAs actually investigate whether this is shippable.

@tabatkins
Copy link
Member

The second comment on that bug is about the CSS namespace specifically.

@bzbarsky
Copy link

Yes, it's about the fact that the functionality is needed for that. I'll be pretty surprised if this change gets made in that bug.

Anyway, I landed this in Gecko in https://bugzilla.mozilla.org/show_bug.cgi?id=1455805 but in general the CSSWG really should start filing bugs when spec changes happen....

@zcorpan zcorpan deleted the css-idl-namespace branch April 24, 2018 13:25
fergald pushed a commit to fergald/csswg-drafts that referenced this pull request May 7, 2018
foolip added a commit to foolip/css-houdini-drafts that referenced this pull request Jul 21, 2018
tabatkins pushed a commit to w3c/css-houdini-drafts that referenced this pull request Jul 23, 2018
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.

4 participants