Re: [whatwg/dom] Non-builtin custom elements which don't have definition yet, may get non-null is-value (#659)

Hmm. This isn't horrible: basically, if we don't have a definition, we want to preserve the `is`, so that later if we get upgraded, it's still there. Whereas if we have a definition, we know this is useless, so we throw it away...

I can see how it's a bit weird though. What would your preferred solution be?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/659#issuecomment-400490163