06:24
<Kaiido>
This stackoverflow question made me look into how localStorage is defined and there is a point that seems weird. As I read it, each Document has its local storage holder set only when the localStorage getter is called, and the broadcast operation fires event only on globals that have a matching Storage holder. So if a Document does set a storage event listener without calling that getter it wouldn't receive events? All browsers seem to fire it anyway https://jsfiddle.net/yspr304z/ So why define it only in the getter? Did I miss something or should I open an issue?
07:33
<Domenic>
This stackoverflow question made me look into how localStorage is defined and there is a point that seems weird. As I read it, each Document has its local storage holder set only when the localStorage getter is called, and the broadcast operation fires event only on globals that have a matching Storage holder. So if a Document does set a storage event listener without calling that getter it wouldn't receive events? All browsers seem to fire it anyway https://jsfiddle.net/yspr304z/ So why define it only in the getter? Did I miss something or should I open an issue?
Looks like a bug introduced with the storage bottles work, indeed. A bug would be helpful.
14:01
<Dominic Farolino>
Can we treat "not present undefined" differently than "present but explicitly undefined", for members of a Web IDL dictionary? I think we can because in the former, the member would simply not [=map/exist=], while the latter would explicitly trigger Web IDL conversion steps from undefined -> the specified type. Is that right?
14:22
<Ms2ger>
No, explicit undefined isn't converted; see 4.1.3 https://webidl.spec.whatwg.org/#js-dictionary