| 04:02 | <superkuh> | So now that we're saved from strict xhtml and single errors making everything not display can we disband whatwg now? Because now whatwg is worse than the cure pushing dom that's so integrated with JS that a single JS error makes all page contents not display. |
| 04:03 | <superkuh> | You've become the thing you were created to stop. |
| 04:03 | <superkuh> | And worse, it's all co-opted by mega-corps. At least the w3c never had that happen fully. |
| 10:33 | <PiersW> | That's certainly one point of view... But I don't quite understand how a single JS error makes all the page not display, unless JS is dynamically creating the page. Which isn't all that common really, and has been possible for way longer than whatwg has existed. |
| 12:31 | <lilltiger> | superkuh: It's in the topic. |
| 12:31 | <lilltiger> | "Please leave your sense of logic at the door, thanks!" |
| 12:31 | <lilltiger> | =D |
| 17:05 | <annevk> | So I ran into two separate cases today where people confused user agent and agent. Should probably link user agent more now that have it defined... |
| 17:05 | <annevk> | we have* |
| 19:08 | <Domenic> | It seems like if you do iframe.src = iframe.src + "#foo" in browsers this does not cause a second navigation. But I can't find where the spec would bail out early... |
| 19:18 | <jgraham> | Domenic: https://html.spec.whatwg.org/#navigating-across-documents:scroll-to-fragid |
| 19:20 | <Domenic> | Dangit, it was right there. Thank you jgraham |