| 09:25 | <smaug____> | clearly microtasks are too hard to understand :/ |
| 12:34 | <Domenic> | This feels like an appropriate time for 👏 |
| 12:34 | <Domenic> | WHENEVER 👏 THE 👏 STACK 👏 IS 👏 EMPTY |
| 12:36 | <nox> | Domenic: Could be worse, at least they aren't defined in an RFC! |
| 12:36 | <Domenic> | ^_^ |
| 12:36 | <nox> | GPHemsley: I don't even need to go check which issue it is to know what you mean. |
| 13:05 | GPHemsley | sighs |
| 13:10 | <GPHemsley> | in sort-of-related news, I got schooled on the WHATWG a few weeks ago: https://en.wikipedia.org/wiki/Template_talk:Glossary_link_internal#Reverted_recent_major_changes |
| 13:10 | <GPHemsley> | (look for "Long digression on why else to not take WHATWG seriously") |
| 13:47 | <annevk> | GPHemsley: o_O |
| 13:47 | <annevk> | GPHemsley: this person should meet up with the Google-conspiracists |
| 13:47 | <nox> | "and is notably missing Microsoft and Google" |
| 13:47 | <nox> | wat |
| 13:48 | <nox> | annevk: Wouldn't they annihilate each other, like matter and anti-matter? |
| 13:53 | <annevk> | nox: https://www.youtube.com/watch?v=zGxwbhkDjZM |
| 13:54 | <nox> | Hah. |
| 14:11 | <GPHemsley> | yeah, I just threw my hands up at that point |
| 14:50 | <freesamael> | annevk: Domenic: I wrote a document about Firefox's session history implementation with a few examples, and some questions that I'm willing to find out from other browsers. Does it look enough to initiate a discussion? |
| 14:50 | <freesamael> | https://docs.google.com/document/d/1PDMf2NEaxf94ap26SREcM3DaZjk6dvq0jfsg983SPx0/edit?usp=sharing |
| 16:00 | <nox> | freesamael: ajeffrey_ did session history stuff and such comparisons too IIRC, when cleaning that stuff in Servo. |
| 16:03 | <ajeffrey_> | nox freesamael: indeed I did, cbrewster and I wrote https://arxiv.org/abs/1608.05444 largely to keep our head straight while trying to implement session history. |
| 16:09 | <freesamael> | nox: ajeffrey_: Yes I'm aware of that :) What I'm trying to find out is what to do with history of nested browsing contexts when the top-level browsing context has navigated away to a different document and the browser doesn't want to keep non-active documents (and child browsing contexts of that) in memory. I'm trying to push |
| 16:09 | <freesamael> | https://github.com/whatwg/html/issues/1454 |
| 16:12 | <nox> | Inb4 a second paper gets written. |
| 16:20 | <ajeffrey_> | freesamael: adding comments to the google doc, mostly about how Servo does things since that |
| 16:20 | <ajeffrey_> | 's what I know :) |
| 16:21 | <ajeffrey_> | freesamael: it looks like our pretty pictures were helpful btw, I like yours! |
| 16:22 | <freesamael> | ajeffrey_: Thx for the comments! Yes I stole the representation from your paper :P |
| 16:23 | <annevk> | nox: ajeffrey_: freesamael, smaug____, and I had a discussion here earlier and we reached a tentative conclusion that the spec and Servo might be too far from contemporary implementations to align with 😟 |
| 16:23 | <annevk> | I see now that's ambiguous; read that as "nox, ajeffrey_" |
| 16:24 | <ajeffrey_> | annevk: Servo is essentially the current spec :) |
| 16:24 | <annevk> | freesamael: please ping me again if I haven't gotten to it by Wednesday or so |
| 16:24 | <ajeffrey_> | freesamael: imitation === flattery :) |
| 16:25 | <freesamael> | annevk: Take your time. I may post it on the github issue later |
| 16:37 | <annevk> | littledan: is there a plan for <script type=wasm> still? Some issue I can track? |
| 16:59 | <littledan> | annevk: I think it's a little far out, but I guess this is the bug: https://github.com/WebAssembly/design/issues/1087 |
| 16:59 | <annevk> | littledan: ta, subscribed |
| 17:31 | <Domenic> | It's on my plate |
| 17:31 | <Domenic> | It'll be <script type=module> probably with MIME type distinguishing |
| 17:32 | <Domenic> | https://docs.google.com/presentation/d/11tHsNh2U9oEJD4lvV7XX2M22JnyeyyCHj1ncmspXjBU/edit?usp=sharing |
| 17:32 | <smaug____> | ajeffrey_: the current spec isn't the web |
| 17:32 | <smaug____> | and the spec doesn't deal with difficult cases |
| 17:33 | <smaug____> | FWIW, looks like chromium is fixing their issues, and sounds like they will behave even closer to gecko and edge |
| 17:46 | <ajeffrey_> | smaug____: indeed, there is a discrepancy between the spec and implementations. |
| 17:47 | <smaug____> | and session history happens to be probably the most regression prone code we have, at least in Gecko |
| 17:47 | <smaug____> | basically any change to any behavior will cause some regression bug(s) |
| 17:47 | <smaug____> | of course on of the reasons for that is that there is no spec to follow |
| 17:47 | <smaug____> | s/on/one/ |