- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 20 Jan 2010 12:35:25 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/contacts In directory hutz:/tmp/cvs-serv28711 Modified Files: Overview.html Log Message: more useful title for ref regarding order of looping in JavaScript Index: Overview.html =================================================================== RCS file: /sources/public/2009/dap/contacts/Overview.html,v retrieving revision 1.31 retrieving revision 1.32 diff -u -d -r1.31 -r1.32 --- Overview.html 20 Jan 2010 12:27:16 -0000 1.31 +++ Overview.html 20 Jan 2010 12:35:23 -0000 1.32 @@ -702,7 +702,7 @@ properties [...] is not specified." <br /><br /> However, all major browsers loop over the properties of an object in the order in which they were defined (ref: - <a href="http://stackoverflow.com/questions/648139/is-the-order-of-fields-in-a-javascript-object-predicatble-when-looping-through-th/648163#648163">[1]</a> + <a href="http://ejohn.org/blog/javascript-in-chrome/"><cite>JavaScript in Chrome</cite> blog post</a> but independently verified). Chrome has some minor issues, but due to the overwhelming implementation of this behaviour in all other major browsers, the Chrome development team have marked this as a bug and it is due for fix in an upcoming release <a href="http://code.google.com/p/chromium/issues/detail?id=20144">[2]</a>.
Received on Wednesday, 20 January 2010 12:35:27 UTC