On Fri, Oct 20, 2023 at 11:39 AM TAMURA, Kent <tk...@chromium.org> wrote:
> > > On Fri, Oct 20, 2023 at 4:42 AM fantasai <fantasai.li...@inkedblade.net> > wrote: > >> On 10/19/23 03:41, TAMURA, Kent wrote: >> > >> > Specification >> > >> > https://drafts.csswg.org/css-ruby-1/#ruby-display >> > >> > Summary >> > >> > New CSS displayproperty values, "ruby", "ruby-base", and "ruby-text", >> are >> > added. The default display values of <ruby>, <rb> and <rt> are changed >> to >> > them, and ruby layout respects these display values. Web authors can >> use any >> > elements such as <div> to render ruby by setting the new display values. >> >> It seems you're listing a subset of values, which makes me wonder what >> differences you would be introducing between Blink's behavior and the >> behavior >> described in the specs (if any)? >> > > I think the new behavior will be a subset of CSS ruby. Blink will be > compatible with CSS ruby box generation, but web authors won't have a way > to specify ruby-base-container and ruby-text-container to elements. > > > >> >> > TAG review >> > >> > None; Firefox already shipped this. >> >> Firefox shipped a complete implementation of the ruby box model, so it's >> a bit >> different from what you're proposing. >> > /Gecko/: Shipped/Shipping >> > >> > /WebKit/: Positive ( >> https://github.com/WebKit/standards-positions/issues/232) >> >> WebKit's position is also against the whole spec... >> > > I don't think WebKit is against the specification though their ruby > development is not active. > I found that WebKit started to implement CSS Ruby last month. https://commits.webkit.org/267937@main WebKit has 'display: ruby' and 'display: ruby-text' though they're not enabled yet. > > > >> >> I think it would be important to understand how Blink's proposed >> implementation might differ from the spec and from Firefox's >> implementation, >> particularly in terms of the box model and layout structures it generates >> for >> various ruby markup patterns. >> >> Also, CSS Ruby Layout is quite complicated, do you have a prototype >> already? I >> didn't see an Intent to Prototype come through earlier. I think it would >> be a >> good idea to evaluate the quality of the implementation and any >> differences >> with Firefox before approving an intent to ship. At least, if I were in >> charge, I would want to... >> > > We don't have an implementation of this change yet. > > >> >> ~fantasai >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9d2c0ed1-478f-4f30-976a-eaff5d2c3ea6%40inkedblade.net >> . >> > > > -- > TAMURA Kent > Software Engineer, Google > > > -- TAMURA Kent Software Engineer, Google -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqGC%3DMLdNMizD3Wa%2BMPg21ihFcP89%2BYB7%3DYiPxPBpD4mjg%40mail.gmail.com.
