| 00:12 | <Domenic> | I thought unloading cancels all network requests? |
| 00:13 | <Domenic> | Like I don't think initial about:blank is special here |
| 00:14 | <Domenic> | https://html.spec.whatwg.org/#abort-a-document step 2 |
| 01:40 | <sideshowbarker> | I’m still optimistic. Especially if I’m willing to do all the setup work for it myself, with the understanding that we can just test out the results first, and turn it off later if there are objections for some reason. And hopefully we can take advantage of face-to-face time at TPAC next week to have a friendly discussion about it there. |
| 01:43 | <sideshowbarker> | annevk: if you have time to look at https://github.com/mdn/content/issues/20441 that’d be much appreciated. (Or anybody else who wants to take time to look into it.) The behavior described in that issue description doesn’t seem to conform to the spec but I’ve not tried reproducing it. The OP has a repro case set up at https://github.com/AtofStryker/understanding-cookie-behavior |
| 01:49 | <sideshowbarker> | hmm wait actually I see the issue is just about the statement “Setting withCredentials has no effect on same-site requests” in MDN at https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/withCredentials. …which is just wrong in the case where a same-site request is cross-origin |
| 02:03 | <sideshowbarker> | commented at https://github.com/mdn/content/issues/20441#issuecomment-1241414596 |
| 08:31 | <smaug> | zcorpan: is plaintext-only some ancient feature? |
| 08:31 | <zcorpan> | smaug: yes |
| 08:32 | <smaug> | zcorpan: does anyone have usage data of it? |
| 08:33 | <zcorpan> | smaug: https://chromestatus.com/metrics/feature/timeline/popularity/1132 |
| 08:34 | <Ms2ger 💉💉> | Oh, I thought you meant <plaintext> |
| 08:34 | <zcorpan> | smaug: there's also https://chromestatus.com/metrics/feature/timeline/popularity/1800 which ... has higher usage :/ I was hoping browsers could remove -webkit-user-modify |
| 08:35 | <smaug> | plaintext-only is going down nicely. If chromium just pushed a tiny bit, we might be able to get rid of it |
| 08:39 | <zcorpan> | maybe, but 0.2% was enough to need to add <image> parsing back in 2006 |
| 08:40 | <zcorpan> | meanwhile the web editing folks propose a more verbose way to do the same thing (with more control, but still) https://w3c.github.io/editing/docs/contentEditableDisabled/ |
| 08:42 | <zcorpan> | also -webkit-user-modify: read-write-plaintext-only is at 2%, so if that is not also removed there's no win with removing contenteditable=plaintext-only (which maps to the css property in webkit/chromium) |
| 08:55 | <Jake Archibald> | plaintext-only is actually pretty nice for creating a text field which grows to fit its contents |
| 08:55 | <Jake Archibald> | Which I recall being pretty hard with <textarea> |
| 13:38 | <Jake Archibald> | annevk smaug: We're going to have a breakout on the history spec changes if you're interested https://www.w3.org/events/meetings/118f6c22-1545-4c3b-9581-260621fec362 |
| 13:38 | <smaug> | Jake Archibald: yeah, I'll try to be there |
| 14:51 | <hsivonen> | https://html.spec.whatwg.org/#abort-a-document step 2 |
| 19:52 | <annevk> | Jake Archibald: if there's no overlap will definitely be there. Multi-year rewrites of never properly specified features FTW. |
| 19:53 | <annevk> | zcorpan: I've been thinking a bit about your comment about image loading, the microtask it queues, and <picture>. I was wondering how that works when <picture> is being parsed. Wouldn't you have to wait for </picture> essentially? (Which is not something the parser exposes as you probably know all too well.) |
| 22:37 | <sideshowbarker> | TabAtkins: beautiful — thanks tons |
| 22:38 | <TabAtkins> | np, it was indeed extremely easy since Andreu did all the work already |
| 22:38 | <TabAtkins> | (https://w3c.github.io/csswg-drafts/ now exists, fyi to the rest of the channel) |
| 22:46 | <Domenic> | OMG! |
| 22:46 | <Domenic> | Can we switch Bikeshed to use these as the new URLs? |
| 22:52 | <TabAtkins> | Not willing to do that quite yet (it would involve either manually changing every entry in the current database by hand, via a CRUD interface, or bypassing with a hacky search-and-replace like I do to generate the mirror). We are paying plinss now to get things fixed properly, so we can reevaluate at the end of the contract. ^_^ |
| 23:18 | <Domenic> | A hacky search-and-replace seems quite worthwhile... maybe I can just do that in the global whatwg build script |