Hayato Ito

icon indicating a website link http://hayatoito.github.io/ icon indicating an email [email protected]

icon company Google icon location Tokyo icon location @google @whatwg @w3c Google Chrome / Blink. DOM / Shadow DOM. Web Bundles.

Results 12 comments of Hayato Ito

Web component semantics

@alice Thank you for filing an issue. I prefer `ElementSemantics` here.

feat: add subresource-bundling

#6047 seems a bit ambiguous. That doesn't mention any particular feature. It's just about Web Bundle format itself? This PR is about "Subresource Loading with Web Bundles", which is the...

It is unclear how directionality should be inherited into Shadow DOM

We should upstream the section 6 in Shadow DOM spec to HTML Standard. https://w3c.github.io/webcomponents/spec/shadow/#attributes

It is unclear how directionality should be inherited into Shadow DOM

The definition of flat tree is here: https://drafts.csswg.org/css-scoping/#flattening

Allow protocol setter to switch between special and non-special schemes

I received a question on https://bugs.chromium.org/p/chromium/issues/detail?id=1416018 and posted a reply on https://bugs.chromium.org/p/chromium/issues/detail?id=1416018#c11. I just assumed that the standard intentionally included this limitation.

Allow protocol setter to switch between special and non-special schemes

Thanks. I currently don't intend to undo the Chrome fix, at least for now. The fix will be part of the M118 release to make Chrome align with the current...

URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true

I haven't had time to understand the issue yet. Can't we consider that encoding a trailing space is a user's responsibility, instead of URL Standard's responsibility? For example, the following...

URL serialiser does not produce idempotent strings if an opaque path has a trailing space and "exclude fragment" is true

Thanks! I didn't notice that idempotence is clearly stated as a goal in the URL Standard. I understand now. > 1. Always replace a trailing space in an opaque path...

How should Element Timing interact with Shadow DOM?

@npm1 Thank you for filing an issue! @annevk @rniwa, could you help @npm1? We'd appreciate your thoughts to move Element Timing API forward. cc: @chrishtr just in case.

How should Element Timing interact with Shadow DOM?

@npm1 > Ok, I think this is fine as long as the performance of slots can be monitored in practice. I am afraid that that's not what we want here,...