Mason Freed comments

Results 546 comments of


                                            Mason Freed

Should adopting from a Document into its associated inert template document (and vice versa) clear the adoptedStyleSheets?

This sounds like a reasonable proposal to me! It will definitely fix the potential footgun of moving nodes to a template and back. Does the solution here avoid the multi-document...

Should we graduate this?

We're very supportive of moving this to CSSWG, but candidly I'm really hoping @emilio is up for doing the work?

Should we graduate this?

https://github.com/w3c/csswg-drafts/issues/3433#issuecomment-837398993

Should we graduate this?

https://github.com/w3c/csswg-drafts/pull/6304

Add a note about the reasoning to forbid `insertRule(@import)`, or remove the condition?

> > * RESOLVED: @import doesn't parse in constructable stylesheets and as a result throw syntax errors > > This resolution text is confusing. What we actually resolved is to...

Content attribute to import/export IDs across shadow boundaries

> I recall at some point we talked about having a mechanism to pass in a shadow root to some kind of accessor method, but I've forgotten the context. You...

Content attribute to import/export IDs across shadow boundaries

> This is a bit tangential but that API can't possibly just take closed shadow roots. It needs to take both modes of shadow roots since it would violate the...

Specification text for replace() does not match Chromium implementation

We’re not deprecating replace() entirely, just the case where the replacement sheet contains an @import rule. Calls to replace() without @import will continue working as is.

Specification text for replace() does not match Chromium implementation

I just wanted to add support to this issue. It would seem to be most-useful to ignore `@import` rules (with a warning) but keep parsing the remaining rules. This is...

Specification text for replace() does not match Chromium implementation

> If I wrote a PR to update this spec to match the current Chromium implementation, would it be accepted? Or was the plan to wait until CSS modules had...