- From: <bugzilla@jessica.w3.org>
- Date: Fri, 09 Mar 2012 17:41:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16103 --- Comment #8 from Odin Hørthe Omdal <odinho@opera.com> 2012-03-09 17:41:40 UTC --- It's not possible to /remove/ stuff like this, no, but it's possible to have incompatibilities (or extend). With incompatibilities, those who use some special feature from either DOMStringList or DOMString[] would have to work around those incompatibilities, and thus they'll write code that is futureproof when everyone converges on just using DOMString[]. Not getting this in feels a bit like an artificial hindering. And having two possible ways in the spec will make it a bit more vague. However, if it's really really impossible, I'd like to ask around and see if we could go down the incompat road in order to be able to actually converge on this later. By the way, the email from Sicking said "possibly", and there's an unaswered reply to it: http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0908.html -- Getting .contains() in ES arrays would maybe fix it though. Except for the name, but I haven't seen much code that isn't tests, that is relying on that. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 9 March 2012 17:41:46 UTC