Re: [heycam/webidl] Is internal method setup in object creation correct? (#657)

This matters in practice for exotic objects with unforgeable properties, right?  Step 12 (handling globals) is not a problem because globals never need to have special internal methods.  Though step 13 probably needs to explicitly exclude globals, actually.

In any case, exotic objects with unforgeable properties basically means Location and Document.  

In Gecko, there are much bigger problems with mismatches than just the one you point out.  For example, in Gecko you often _can't_ apply the ordinary-object internal methods to exotic objects at all.  And you can't just add properties to exotic objects.  The way we handle this in practice is that legacy platform objects have an ordinary object hanging off them in an internal slot where all the "ordinary properties" bits live.  The unforgeables just get defined directly on there during object creation, so there is no problem with the special internal methods, because they never get called.  The observable effect should be the same as in the spec, though...

-- 
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/657#issuecomment-467102356