12287 2011-03-11 01:53:04 +0000 Restrict sequence<T> to operation argument types and return types 2011-05-23 21:41:30 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED FIXED P2 normal --- 1 cam cam bugs ian mike public-script-coord public-webapps-bugzilla oldest_to_newest 46625 0 cam 2011-03-11 01:53:04 +0000 sequence<T> has undesirable behaviour in JS when used as an attribute value, so we should consider preventing its use there. 46638 1 ian 2011-03-11 20:31:48 +0000 Would be good to have a recommended alternative to (e.g. a note saying to have a method return that type instead). 48684 2 cam 2011-05-23 01:23:02 +0000 Done: http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.270;r2=1.271;f=h 48690 3 bugs 2011-05-23 09:32:08 +0000 (In reply to comment #0) > sequence<T> has undesirable behaviour in JS when used as an attribute value, so > we should consider preventing its use there. Just curious, what that undesirable behavior is? Is it that JS can modify the array while native code is using it? 48717 4 cam 2011-05-23 21:41:30 +0000 The undesirable behaviour is that a new Array object would be created every time you access the property. Simple looping over a sequence attribute, like interface Blah { readonly attribute sequence<long> numbers; }; for (var i = 0; i < myBlah.numbers.length; i++) { doSomethingWith(myBlah.numbers[i]); } would end up doing a lot of wasted work.