| 11:09 | <freddy> | The <xmp highlight="json"> looks really fugly in https://w3c.github.io/webappsec-subresource-integrity/#example-2319c0a9 (Source at https://github.com/w3c/webappsec-subresource-integrity/blob/2089aeb95782970d35f96283d1f3da89beaa8802/index.bs#L721). Looking at the bikeshed docs for <xmp> didn't really help me, anyone got a better idea? |
| 13:15 | <Ms2ger (🇪🇸)> | That highlighting sure didn't work for json |
| 13:42 | <Noam Rosenthal> | Anyone from Gecko/WebKit cares to respond to a standard position on navigation API precommit handlers? The spec PR is pretty much ready (https://github.com/whatwg/html/pull/10919) and the standard position requests are pending.. It's a minor/medium sized addition to the navigation API that was requested by multiple early adopters and frameworks. /cc zcorpan annevk |
| 21:51 | <TabAtkins> | Lol woah, what the fuck happened with that highlighting. |
| 21:56 | <TabAtkins> | Ah, that's not actually valid JSON (JSON uses double quotes), so it's making the lexer just do some nonsense behavior. |
| 21:57 | <TabAtkins> | (Aside from webidl, highlighting is done by Pygments, btw) |
| 22:17 | <TabAtkins> | https://github.com/w3c/webappsec-subresource-integrity/pull/139 |