00:41:43 <tomman> https://lapcatsoftware.com/articles/chrome-cookie.html GOOOOOOOOOGLEEEEE!!!!
00:42:08 <tomman> to be fair, Mozilla was first on pulling this garbage, because they consider that their users are severely handicapped
00:42:22 <tomman> now Chrome is late to the party, I guess
00:43:22 <tomman> "butbutbut you can use the dev tools"
00:43:39 <tomman> cool, now try to delete a cookie WITHOUT visiting the affected site first
00:49:48 <tomman> https://news.ycombinator.com/item?id=28407656 Hackernews reactions are depressing, as usual
15:16:53 <frg_Away> https://www.quirksmode.org/blog/archives/2021/08/breaking_the_we.html
17:39:31 <tomman> How long is the default timeout (if any) for closing active connections when you close a tab while downloading its contents?
17:39:42 <tomman> Say, I've opened right now a tab for a 50MB JPG imge
17:40:06 <tomman> decided that I'm not waiting for the image to download on my slowass DSL, so closed the tab
17:40:21 <tomman> yet SeaMonkey continues happily downloading the 50MB JPG in the background for a while
17:40:37 <tomman> This could be a problem on metered connections
17:43:17 <tomman> > A blog storm broke out over the decision to remove alert(), confirm() and prompt(), first only the cross-origin variants, but eventually all of them. Jeremy and Chris Coyier already summarised the situation, while Rich Harris discusses the uses of the three ancient modals, especially when it comes to learning JavaScript.
17:43:20 <tomman> wait, WHAT?!?!?!?
17:44:06 <tomman> let me guess: the suggested replacement is yet another megabyte-long Node.js framework library with a heavily convoluted API that will require the latest Chromeisms™
17:50:00 <frg_Away> tomman beats me deep in network and probably an async fetch. At least 30 seconds I suspect. Might even try to complete the current image download.
19:32:45 <tomman> https://twitter.com/estark37/status/1422694856544059396 this is particularly horrible
19:32:49 <tomman> "Breaking changes happen often on the web, and as a developer it’s good practice to test against early release channels of major browsers to learn about any compatibility issues upfront."
19:33:36 <tomman> so basically webdevs should get used to test their sites on broken pre-beta browser versions that won't ship for months in advance, because BREAKING IS GOOD!
19:33:57 <tomman> I can't believe the day I would hate computers would ever come, but... here we are :/
19:49:33 <njsg> "test against early release[s] [...] to learn about any compatibility issues"?
19:49:56 <njsg> but... isn't that... wouldn't it possibly be... testing against what introduces compatibility issues?
19:52:04 <njsg> such testing does have value, perhaps more to find out about stuff to correct in the browsers, but it really should be noted that the main test is with stable versions
22:04:57 <frg_Away> tomman I don't hate computers. Just big corporate monopolyies. But without users agreeing to everything they do and still using them nothing which can be done.