| 10:34 | <Ms2ger> | var a = document.createElement("a"); |
| 10:34 | <Ms2ger> | a.setAttribute("href", "//[:\uD83C]"); |
| 10:34 | <Ms2ger> | w(a.href) |
| 10:34 | <Ms2ger> | Does this log a string containing an unpaired surrogate? |
| 10:34 | <Ms2ger> | Bonus points for a spec pointer to back you up |
| 10:57 | <annevk> | Ms2ger: how about a bug? https://www.w3.org/Bugs/Public/show_bug.cgi?id=26967 |
| 10:58 | <Ms2ger> | That works |
| 11:00 | <annevk> | Ms2ger: the logged string should not have surrogate, though |
| 11:00 | <annevk> | Ms2ger: oh wait, that fails to parse, so maybe it should, hmm |
| 11:02 | <Ms2ger> | Yeah, the case where parsing succeeds is fine |
| 12:03 | <annevk> | I forgot who asked me when I would write a blog post again, but I published something |
| 12:10 | <rits> | annevk: i have updated the commit list https://github.com/whatwg/html/pull/484 |
| 12:11 | <rits> | annevk: i have yesterday's question still for this issue https://github.com/whatwg/html/issues/156 |
| 12:46 | <annevk> | rits: for the second one, whereever HTML now uses 0xNN notation for bytes we could maybe move to using `c` instead |
| 12:47 | <annevk> | rits: if NN <= 7F |
| 12:47 | <rits> | annevk: okay you have implemented it for headers |
| 12:48 | <annevk> | rits: yeah, it could maybe be done for "prescan a byte stream to determine its encoding" too, but I'm not sure if it would make that more readable |
| 12:48 | <annevk> | rits: I'm also not sure if I did it for all headers and their values, I somewhat doubt it |
| 12:49 | <rits> | annevk: okay, so if i will give it a check for headers first |
| 13:32 | <smaug____> | how does one turn on some experimental flags in Chrome? |
| 13:34 | <smaug____> | ah, about:flags |
| 13:46 | <JakeA> | Domenic: Am I missing something, or is https://github.com/domenic/streams-demo not boundry-safe? |
| 13:46 | <JakeA> | As in, if the search value is present, but broken across multiple chunks |
| 15:41 | <JakeA> | Domenic: stream.cancel(reason) - I'm guessing reason should be an Error since it's also used in rejections? |
| 15:42 | <JakeA> | Or is it the other way around? "reason" will be an error if it's the result of a promise rejection? |
| 16:00 | <Domenic> | JakeA: yes it is not boundary safe, i was lazy. reason can be anything; it is only used by the underlying source, which in Chrome I don't think does anything with it (although maybe it should log it to the console or something...) |
| 16:01 | <JakeA> | Domenic: here's a boundary-safe (I think) demo that searches the html spec https://jsbin.com/tepohi/edit?js,console |
| 16:03 | <Domenic> | JakeA: ah awesome |
| 16:04 | <JakeA> | Streams are awesome btw, loads of fun |
| 16:04 | <Domenic> | :D |
| 19:13 | <Manishearth> | annevk: around? |
| 19:17 | <Manishearth> | annevk: Fetch doesn't really explain how to handle HTTP 204 |
| 19:17 | <Manishearth> | (the correct way to handle it seems to be to not navigate at all) |
| 19:50 | <annevk> | Manishearth: HTML should cover that, no? |
| 19:50 | <Manishearth> | annevk: does it? |
| 19:51 | <annevk> | Dunno, but that would be the place |
| 19:51 | <annevk> | Feel free to file an issue of course |
| 20:03 | <Manishearth> | annevk: https://html.spec.whatwg.org/#navigating-across-documents step 20, but it could be more specific I think? |
| 20:04 | <annevk> | Sure |
| 20:04 | <annevk> | Navigate needs a ton of refactoring anyway |
| 20:29 | <Manishearth> | Hixie: step 21 here mentions things which require processing not affecting the browsing context |
| 20:29 | <Manishearth> | https://html.spec.whatwg.org/multipage/browsers.html#navigating-across-documents |
| 20:29 | <Manishearth> | is there an exhaustive answer for this? |
| 20:30 | <Manishearth> | i.e. does that note contain everything that's needed on the spec-side to be processed this way? |
| 20:30 | <Manishearth> | IMO 204 and 205 should at least be listed as musts there. Things like javascript:void(0) (used by basically everyone) break otherwise. |
| 20:31 | <Manishearth> | Though I'm not sure why incorrect TLS cert is there -- AIUI that should navigate to an error page? |
| 20:31 | <Manishearth> | Basically there are certain responses (204, 205) which should not navigate at all, not even to an erro rpage |
| 20:32 | <Manishearth> | and certain responses which *may* not navigate |
| 20:47 | <annevk> | Manishearth: file issues or write PRs, best way to make progress here |
| 20:48 | <Manishearth> | annevk: cool |
| 20:50 | <annevk> | Manishearth: thank you! |
| 21:02 | <Manishearth> | annevk: https://github.com/whatwg/html/issues/511 |
| 22:54 | <smaug____> | can wpt tests test form submission? |
| 22:54 | <smaug____> | like what kind of data is sent to the server side |
| 23:41 | <one77> | hi |
| 23:41 | <botie> | hi, one77 |
| 23:41 | <one77> | im new here |
| 23:41 | <one77> | i was searching for a chatroom where i can find people like webdevelopment like i do |