Re: [heycam/webidl] Dictionary mixins (#195)

@dcrousso the property [[Get]] order, as bzbarsky mentioned, does expose the inheritance chain to ES code. Within a single "tier", keys are sorted lexically, but the access order is one-tier-at-a-time. If they were always be sorted across the chain, the exposure would go away, but that likely isn't web compatible (and might lead to problems for implementers).

One ordering solution for mixins would be to handle them like partials: "these keys belong to the includes-target, so its members get sorted lexically among the others". I'm pretty sure that would keep the access order well-defined without borking anything that already exists?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/195#issuecomment-810558704