WHATWG
2022-09-23
plaintext logs
prev next
source on github
05:04
<sideshowbarker>
Looking at https://github.com/mdn/content/pull/21001
05:05
<sideshowbarker>
As far as I understand, an error event isn’t cancelable unless it’s initialized/fired with its cancelable attribute explicitly set to true.
05:10
<hacknorris>
annevk: hacknorris is asking for help with illegal activity; go ahead and ban them (I've reported their account)
And just because of an asshole with 6 hour network delay i need to leave programming forever...
05:26
<sideshowbarker>

About the error event, see the change in that PR, in particular this part:
https://pr21001.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/Window/error_event#usage_notes

Unlike other events, the error event is canceled by returning true from the handler instead of returning false. When canceled, the error won't appear in the console, but the current script will still stop executing.

Is that behavior defined in the spec somewhere? And is that different from the event being “cancelable”?

05:28
<sideshowbarker>
ah, in https://html.spec.whatwg.org/multipage/webappapis.html#runtime-script-errors I guess
07:42
<Yoav Weiss>
hsivonen: just saw your question from Tuesday.. :/ mfreed would likely know
07:47
<hsivonen>
hsivonen: just saw your question from Tuesday.. :/ mfreed would likely know
I'm assuming that non-initial about:blank being interoperably unlike http URLs in its DOM construction means that it's too risky to make it behave like http URLs in relation to the event loop.
07:48
<hacknorris>
Btw. Today already someone knows answer to this my yesterday question about css?
08:09
<freddy>
hacknorris: I believe you are in the wrong room.
08:11
<hacknorris>
Means?
08:15
<hacknorris>
annevk: clearly said i can ask about css...
08:20
<annevk>
I had overlooked that earlier message... Thanks for calling it out TabAtkins
09:06
<annevk>
For the first time in five years or so the SG repository has no outstanding PRs! (Not a challenge.)
14:57
<Sgeo>
What is the purpose of the x-user-defined encoding? I'm curious if it's in the spec only because it used to be used as a way to download binary files ( https://stackoverflow.com/questions/6986789/why-are-some-bytes-prefixed-with-0xf7-when-using-charset-x-user-defined-with-xm ) ( https://web.archive.org/web/20070612091315/http://mgran.blogspot.com/ ).
14:59
<Ms2ger 💉💉>
hysterical raisins
15:04
<Sgeo>
"Return a code point whose value is 0xF780 + byte − 0x80.".... is there a reason it doesn't just say 0xF700 + byte?
15:24
<annevk>
Sgeo: the idea is to make it clear the code point will start at 0xF780 as byte will be at least 0x80
15:26
<annevk>
evilpie: FYI, it seems you did make a push on August 8 for https://github.com/whatwg/fetch/pull/1463 but it did not include the fix for using the wrong field on request