-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge DOMSettableTokenList into DOMTokenList #119
Comments
If changing prototypes is an issue we could do the same thing as how |
In httparchive i only see http://www.gstatic.com/caja/5678/es53-taming-frame.opt.js?debug=1 containing "DOMSettableTokenList.prototype" but it was actually "TameDOMSettableTokenList.prototype". Looking at all instances of "DOMSettableTokenList" is just a handful of copies of http://kpn.blueconic.net/frontend/static/javascript/blueconic/blueconic.min.js which does var myGlobalVarBlacklist=["window","top","location","external","chrome", ... ,"DOMSettableTokenList" So probably we don't need to keep |
Move DOMSettableTokenList#value to DOMTokenList and remove the DOMSettableTokenList interface.
Move DOMSettableTokenList#value to DOMTokenList and remove the DOMSettableTokenList interface.
Move DOMSettableTokenList#value to DOMTokenList and remove the DOMSettableTokenList interface.
Per discussion on IRC with @domenic and @zcorpan only HTML uses these classes. It seems like we could simplify things a bit by merging them into a single class and use
[PutForward]
everywhere.The problem I could see is that libraries depend on changing the prototype of these classes in ways that are incompatible with such a simplification. What do folks think?
The text was updated successfully, but these errors were encountered: