Re: [heycam/webidl] Consider flipping the [Unscopable] design (#361)

So fundamentally, we want unscopability for new members on Document, Node, Element, HTMLElement and their mixins.  We do _not_ want this for existing scopable members, nor for any members on any other interfaces.

I suppose we could try to write a web platform test that asserts things about the scopable set of names on an HTML element instance and effectively hardcodes today's list...  This would at least fail if people add a new scopable thing and then we can have a discussion about whether the new thing should be scopable or not.

-- 
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/361#issuecomment-301103409