| 11:47 | <Andreu Botella> | I've found a case where <wbr> renders differently in different browsers, and once again I'm wondering why the rendering of <br> and <wbr> is still specified in terms of display-outside, which is not part of CSS currently, and which I doubt was ever in a published CSS standard |
| 12:06 | <akaster> | I've found a case where |
| 12:09 | <Andreu Botella> | Surely we can do better than using non-existent CSS property |
| 12:09 | <akaster> | Oh I guess @domenicdenicola:matrix.org: has this old PR that specifies them as "UA magic 🪄" https://github.com/whatwg/html/pull/2298 |
| 12:10 | <Domenic> | It might be good if someone resurrects that to just add a bunch of XXX boxes, instead of using CSS. |
| 12:10 | <Domenic> | I guess the main open question is what CSS properties apply to those elements |
| 12:12 | <Domenic> | Hmm I feel like that PR is somewhat mergeable as-is, reviewing its contents. Maybe just change one <p> to <p class="XXX">. I think I just wasn't confident enough in my new editorship in 2017 to feel comfortable merging it. |
| 12:12 | <Domenic> | If someone resurrects it I can review and merge. |
| 12:14 | <nicolo-ribaudo> | Lol, Element is not escaping the br in that link preview title |
| 12:25 | <Andreu Botella> | The rendering difference I found is that, with inherited white-space: nowrap, <wbr> in Chromium allows line breaking, but it doesn't in Firefox or Webkit |
| 12:25 | <Andreu Botella> | there's a parallel to nobr wbr { white-space: normal } |
| 12:26 | <Andreu Botella> | but we can figure this out after the magic PR is merged |
| 13:51 | <Domenic> | That may be https://github.com/whatwg/html/issues/6227 |