13:04
<caitp>
I'm looking at WebIDL and DOM looking for an explanation about the difference between Chrome and FF when it comes to enumerable-ness of indexed properties (particularly in NodeList.childNodes), to justify either behaviour, but I'm having trouble finding support for either behaviour
13:37
<annevk>
caitp: NodeList.prototype.childNodes is not a thing, afaik
13:37
<caitp>
right, you know what I mean
13:37
<caitp>
the NodeList returned by thing.childNodes
13:44
<annevk>
oh
13:46
<annevk>
caitp: can't really find anything quickly other than https://heycam.github.io/webidl/#legacy-platform-object-property-enumeration which doesn't really address the question
13:50
<caitp>
I'm not sure which one is correct, if any
13:50
<caitp>
related to https://twitter.com/ziyunfei/status/863347908929769472
13:51
<caitp>
anyways, will look at that on monday I guess
13:54
<annevk>
caitp: is this about the iterable<> declaration or about enumerable properties?
13:55
<annevk>
I guess I don't really know what Object.values does
14:03
<caitp>
its like Object.keys, returns values of all own enumerable properties
14:03
<caitp>
non-Symbol-keyed properties*
14:04
<caitp>
ff reports the indexed properties as enumerable, chrome doesnt
14:05
<annevk>
caitp: pretty sure Firefox is correct since bz did most of that stuff
14:05
<annevk>
caitp: and platform objects always tend to have everything enumerable, afaik
14:05
<caitp>
maybe he can explain the choice
14:07
<annevk>
caitp: https://heycam.github.io/webidl/#LegacyPlatformObjectGetOwnProperty defines it
14:08
<caitp>
yes, but that attribute doesnt apply to NodeList afaict
14:08
<annevk>
caitp: why not?
14:08
<annevk>
caitp: nodelist has a getter and is therefore a legacy platform object
14:09
<caitp>
hmm, alright
14:09
<caitp>
so, blink bindings bug, mystery solved. thanks for taking the time
21:43
<zewt>
hooray turning https off on a site because browsers are stupid and refuse to load mixed-content iframes
21:44
<zewt>
forcing people to not use https sure is a great security feature