| 05:54 | <annevk> | https://twitter.com/arturotena/status/645708214458159104 heh |
| 05:55 | <annevk> | jamesr: well, it's specified that the browser renders between tasks and not during them (as Opera used to do and would trip folks up) |
| 08:35 | <Huvet> | Hi! I have some horrible HTML generated by Outlook that I want to parse with html5lib... it seems it's filled with <u/> tags all over. But since html5lib parses that as a regular <u> the whole document gets underlined. Is there a way in html5lib to allow more tags to be "self-closing"? |
| 08:36 | <annevk> | Huvet: you'd have to modify html5lib |
| 08:36 | <annevk> | Huvet: might be easier to search and replace <u/> with <u></u> first |
| 08:36 | <annevk> | Huvet: or remove <u/> before parsing or u elements after parsing |
| 08:38 | <Huvet> | damnit, wish there was a way to "expand" them beforehand... but doing that with a regex or string replace leads to insanity, or so I've read on Stackoverflow |
| 08:39 | <Huvet> | thanks! |
| 08:40 | <annevk> | Huvet: yeah, that's probably not a good idea unless the input is highly predictable |
| 08:40 | <annevk> | Huvet: just iterating through the tree afterwards is likely saner |
| 08:41 | <Huvet> | but afterwards means it's already too late... there can be correct <u> tags in there too, so I don't want to replace all of them |
| 08:41 | <Huvet> | so since html5lib borks them I need to do it before everything else |
| 08:42 | <Huvet> | what if I monkeypatch html5lib.constants.voidElements? |
| 08:45 | <Ms2ger> | Voids your warranty :) |
| 08:48 | <Huvet> | Yeah, I'll just parse HTML with a regex beforehand instead :) |
| 08:49 | <jgraham> | I hate to be the one asking stupid questions, but I assume it doesn't parse with an XML parser? |
| 08:52 | <Huvet> | It's random HTML from the internet, so I don't trust a xml parsers to touch it at all |
| 08:52 | <annevk> | Huvet: if you change voidElements you'll mess up the correct <u> elements too |
| 08:54 | <Huvet> | yeah, I'll keep my warranty and do it with regexps |
| 08:55 | <annevk> | Hah, not sure if I have this pile of regexps applied and then run the HTML parser and it doesn't really work will get you much help :-P |
| 09:01 | <Huvet> | "they told me to parse with regexp in #whatwg" <- great T-shirt print |
| 09:15 | <zcorpan> | modifying the html parser isn't gonna make you saner than running a regex :-) |
| 09:58 | <MikeSmith> | > "they told me to parse with regexp in #whatwg" đ đ |
| 12:58 | <MikeSmith> | nginx finally has some real competition in terms for performance https://h2o.examp1e.net/ https://github.com/h2o/h2o |
| 12:59 | <MikeSmith> | actually it doesn't seem like much of competition ăźh2o is just way faster |
| 13:00 | <MikeSmith> | also there's nghttp2 https://github.com/tatsuhiro-t/nghttp2 which is an HTTP/2 library that curl now uses |
| 13:05 | <jgraham> | If only it was rust ;) |
| 13:15 | <zcorpan> | ok i'm now having trouble installing this perl XML::parser thing |
| 13:15 | <nox> | Just use MARPA. |
| 13:15 | <zcorpan> | "Warning: Cannot install XML::parser, don't know what it is." |
| 13:15 | nox | runs away. |
| 13:15 | <MikeSmith> | jgraham: yeah |
| 13:15 | <jgraham> | zcorpan: Dare I ask why? |
| 13:15 | <zcorpan> | jgraham: https://github.com/whatwg/html-build |
| 13:16 | <nox> | jgraham: Talking about Rust, |
| 13:16 | <jgraham> | zcorpan: Ugh |
| 13:16 | <nox> | jgraham: it's been twice that html5lib-tests got new tests, |
| 13:16 | <nox> | jgraham: and both times, the differences between the tests and h5e were coming from errors in the former. :) |
| 13:17 | <MikeSmith> | jgraham: there's a perl script used in the HTML spec build that parses a Unicode-related XML file that is a dependency for the cooked spec |
| 13:17 | <jgraham> | nox: Are you volunteering to be a test reviewer? |
| 13:17 | <jgraham> | :) |
| 13:17 | <MikeSmith> | sounds like nox is |
| 13:17 | <nox> | jgraham: I kinda am, but some slipped through. |
| 13:18 | <MikeSmith> | in the case of the ruby tests that might have been at least partially my fault |
| 13:18 | <nox> | jgraham: There were some weird tests with the latest Blink bump. You merged one of the fixes, and I made a PR for the other one, feel free to review it BTW. :D |
| 13:19 | <jgraham> | nox: I think the problem with tests from Blink is that those tests are often wrong |
| 13:19 | <nox> | jgraham: Yes⌠|
| 13:19 | <jgraham> | Because they write tests according to what they would like the spec to be rather than what it actually is, or something |
| 13:19 | <nox> | jgraham: Should run h5e against them before merges. =) |
| 13:21 | <zcorpan> | ah now it seems it's working. should be XML::Parser, not XML::parser |
| 14:02 | <MikeSmith> | jgraham: https://github.com/tatsuhiro-t/nghttp2 has Python bindings btw |
| 14:02 | <MikeSmith> | sadly no Pascal bindings yet for us Pascal fans, but we can hope |
| 14:02 | <zcorpan> | MikeSmith: html-build says "Local wattsi is not present; trying the build server..." although i have (tried to) build wattsi |
| 14:03 | <MikeSmith> | zcorpan: you need to put wattsi in your PATH |
| 14:04 | <MikeSmith> | I have the build script just doing a simple "hash wattsi" check for it |
| 14:04 | <zcorpan> | MikeSmith: ok, bin/wattsi in the wattsi clone? |
| 14:04 | <MikeSmith> | yeah, if that's where you have it |
| 14:04 | <MikeSmith> | then that ./bin dir needs to be in your path |
| 14:05 | <MikeSmith> | the build script doesn't do any magic checking for it elsewhere |
| 14:07 | <MikeSmith> | @tatsuhiro_t, the developer of nghttp2, also has the coolest avatar imaginable https://github.com/tatsuhiro-t |
| 14:08 | <zcorpan> | MikeSmith: works now, thx |
| 14:08 | <MikeSmith> | super |
| 14:09 | <MikeSmith> | you will be able to build fast now |
| 14:09 | <MikeSmith> | ./build.sh --no-update should complete in 15 seconds or less |
| 14:10 | <MikeSmith> | which is pretty impressive given the size of the HTML document it's processing and everything it's doing |
| 14:13 | <MikeSmith> | https://nghttp2.org/httpbin is fun (nghttp2 testing page) |
| 14:23 | <zcorpan> | woot, managed to take the right steps to merge my PR |
| 14:23 | <MikeSmith> | nice |
| 14:24 | MikeSmith | looketh upon it with admiration |
| 14:25 | <MikeSmith> | zcorpan: please always go back to the PR and delete the review branch |
| 14:25 | <MikeSmith> | otherwise the branch bear will bite you |
| 14:26 | <zcorpan> | k |
| 15:04 | <zcorpan> | philipj: MikeSmith: re https://github.com/whatwg/html/commit/0a5aea3590336e260ffd8d35de84425360095520 maybe we should make everything give both explicitly, i suppose that makes the spec easier to understand? |
| 15:05 | <philipj> | zcorpan: doing that would indeed lead to less confusion of the sort that led to this change and revert |
| 15:07 | <zcorpan> | filed an issue |
| 17:04 | <annevk_> | So am I just getting a cached version or is something up with building the specification again? |
| 17:04 | <annevk> | Still shows September 17 here |
| 17:04 | <annevk> | Domenic? |
| 17:04 | <botie> | Domenic is, like, awake |
| 17:04 | <annevk> | Excellent |
| 17:05 | <Domenic> | Sounds like a potential build issue, will investigate |
| 17:08 | <Domenic> | problem identified... should be fixed, will make GitHub re-ping the server to test |
| 17:11 | <annevk> | Domenic: what's the email address of the new person editing ECMAScript? |
| 17:12 | <Domenic> | annevk: that's bterlson, brian.terlsonâgc |
| 17:12 | <Ms2ger> | A new person editing ECMAScript? |
| 17:13 | <annevk> | Domenic: ta |
| 17:13 | <Ms2ger> | Do they know HTML? |
| 17:13 | <bterlson> | hello |
| 17:13 | <bterlson> | what is HTML? |
| 17:13 | <bterlson> | XHTML ftw |
| 17:13 | <annevk> | bterlson: does your @microsoft.com account still work? |
| 17:13 | <bterlson> | I know the doctype by heart |
| 17:13 | <bterlson> | I sure hope so! |
| 17:13 | <annevk> | That's the one autocomplete gave me |
| 17:14 | <bterlson> | should work |
| 17:14 | <bterlson> | brian.terlsonâmc is probably better for all ecmascript-related things |
| 17:15 | <annevk> | ta |
| 17:17 | <Domenic> | annevk: spec fixed, shows 21 September now |
| 17:38 | <annevk> | \o/ |
| 17:45 | <annevk> | I guess I should do some studying tomorrow: https://twitter.com/BrendanEich/status/646013302548525056 |
| 17:53 | <annevk> | Woohoo, 6/11 worker things fixed |
| 17:55 | <Domenic> | annevk: bterlson and I are having a cancelable promises summit today |
| 17:56 | <bterlson> | Domenic: You going to Tilde? |
| 18:04 | <annevk> | No tweet for my workers commit... |
| 18:04 | <annevk> | But the hook says all is dandy |
| 18:04 | <annevk> | Oh well, good enough for today |
| 19:34 | <nox> | annevk: Some studying? |
| 19:39 | <MikeSmith> | zcorpan: yeah, removing a level of indirection that implementors reading the spec need to deal with there would be a plus |
| 19:43 | <TabAtkins> | JonathanNeal: Re top/etc - those properties specify offsets from the containing block. |
| 19:43 | <TabAtkins> | From the relevant containing block edge, that is. |
| 19:46 | <JonathanNeal> | Thanks TabAtkins ! |
| 21:10 | <slightlyoff> | zomg, how did the Storage API fuck up provisional grants? |
| 21:11 | <slightlyoff> | and "estimate" vs. "persistantEstimate"...WTF? |
| 21:11 | <slightlyoff> | nothing about this make sense |
| 21:12 | <slightlyoff> | annevk: we need an API that lets us know if durable storage WOULD be granted if it was requested, without needing to run the prompt |
| 21:28 | <slightlyoff> | I guess we can extend the Permissions API to handle this case |
| 21:28 | <slightlyoff> | will talk to Mounir |
| 21:29 | <slightlyoff> | actually, PersistentStoragePermission needs to be extended |
| 23:02 | <slightlyoff> | the specific case here is that we might want to auto-grant this and developers need to know if something *would* be granted if they asked |
| 23:02 | <slightlyoff> | I'll file a bug |