- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Apr 2021 16:35:44 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-ruby] replaced annotation containers and base containers are nonsensical`, and agreed to the following: * `RESOLVED: Undo previous resolution. Treat replaced elements with an internal ruby display value as if they were inline at used value time` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-ruby] replaced annotation containers and base containers are nonsensical<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6000<br> <dael> Rossen_: Let's timebox to 5m<br> <dael> florian: We discussed that it didn't make a whole lot of sense for replace elements to have ruby-base or ruby-text. xidorn has pushed back<br> <dael> florian: Would rather we treat as inline replaced elements. Invokes rest of box fixup. Anon parents still generated. This would be simplier and is what happens with tables already. Replaced elements in table only get to be inline and wrapped into table parts<br> <dael> florian: I think emilio also argued for that.<br> <dael> florian: Givent he pushback and we do this for tables I think this is a good idea. Saying they're treated as inlines makes sense<br> <dael> florian: If we do that I would also propose we move this into the display spec instead of being in tables and ruby. Display talks about layout internals and could say when you try and apply to replaced element it's treated as inline<br> <dael> florian: Any problems with that?<br> <dael> Rossen_: Did anyone follow it?<br> <dael> Rossen_: florian since there's no issues or comments, prop?<br> <dael> florian: Prop: Undo previous resolution. Treat replaced elements with an internal ruby display value as if they were inline<br> <dael> florian: at used value time<br> <dael> Rossen_: Would this align closer with table?<br> <dael> florian: Yes, closer with tables on Moz current impl<br> <dael> Rossen_: If I have display:table on the replaced element it becomes inline?<br> <dael> florian: display: table-row or -cell they're inline. For outermost like display:table or ruby this is handled.<br> <dael> florian: For internal you're treated as inline<br> <dael> Rossen_: Right. Awesome<br> <dael> Rossen_: Additional comments or objections?<br> <dael> RESOLVED: Undo previous resolution. Treat replaced elements with an internal ruby display value as if they were inline at used value time<br> <dael> Rossen_: Did previous one make it into spec?<br> <dael> florian: Not yet<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6000#issuecomment-828601143 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 April 2021 16:35:46 UTC