| 07:24 | <mathiasbynens> | <script>document.write('\uD83D');</script><script>document.write('\uDE02');</script> |
| 07:24 | <mathiasbynens> | how does it render? Chrome: �� / Firefox: 😂 / Safari: (nothing) |
| 07:34 | <annevk> | mathiasbynens: oh, that's interesting |
| 07:34 | <annevk> | hsivonen: ^^ |
| 07:35 | <mathiasbynens> | (<script>document.write('\uD83D'); document.write('\uDE02');</script> works as spec’d everywhere) |
| 07:36 | <hsivonen> | Interesting. |
| 07:37 | <hsivonen> | nox: ^ |
| 07:38 | <hsivonen> | what happens to unpaired surrogates in the middle of document.write in Chrome? How far are we from changing the document.write argument to USVString? |
| 07:41 | <hsivonen> | looks like unpaired surrogates in the middle are preserved by Chrome and not turned into U+FFFD: https://software.hixie.ch/utilities/js/live-dom-viewer/saved/7044 |
| 07:43 | <hsivonen> | mathiasbynens: it appears that the issue is that Chrome doesn't do coalesced text layout when text is split across two text nodes and there's an invisible element node in the middle |
| 07:51 | <annevk> | Hmm yeah, which is really a bug they should fix as it would affect a lot of languages |
| 12:37 | <Ms2ger> | annevk, ping https://github.com/whatwg/html/pull/4733 |
| 12:40 | <annevk> | Ms2ger: I think Domenic should review that; I thing I wonder about is whether we should preserve the existing ID |
| 12:40 | <annevk> | a thing I* |
| 13:03 | <Domenic> | Ms2ger: will try to do today. It looks very comprehensive but since it's more than just a couple places I wanted to actually do my own double-check. |
| 13:03 | <Ms2ger> | Domenic, okay, sounds good |