06:32
<annevk>
It's not useful to know that it can only throw due to OOM? Is there anything else?
15:46
<Domenic>
Stack overflow IIRC was a big thing for our implementation
16:55
<mgaudet>
annevk: I'm not sure. Certainly for reading the specification, and trying to hold it together as a concept I think it's helpful. As an implementer, I'm less sure of the value (could be wrong, would welcome other opinion).
16:55
<mgaudet>
I know I definitely came into some of this with an incorrect assumption that OOM handling was something done on the web in complicated code bases-- that seems to not actually be the case though?
16:56
<mgaudet>
(The concern I had/have is broken streams that originate from states 'impossible' in the specification, generated by things like OOM, or stack overflow)
20:21
<Jesper van den Ende>
Hey, I noticed setting Node.parentElement works in all browsers. But the spec says it is readonly, doesn't that mean setting it should throw. Or am I missing something?
20:24
<evilpie>
How could I get someone else interested in https://github.com/whatwg/html/issues/3255 ?
20:31
<Jesper van den Ende>
Hey, I noticed setting Node.parentElement works in all browsers. But the spec says it is readonly, doesn't that mean setting it should throw. Or am I missing something?
ah never mind, I was trying this in the inspector console, which doesn't use "use strict" I guess