8967 2010-02-13 12:21:37 +0000 Why is the optional argument in the middle? Isn't it more convenient when copy/pasting code to make optional modifications at either end without having to precisely place the cursor somewhere in the middle? Particularly for piecing together arguments, too 2010-10-04 13:59:47 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#posting-messages P3 normal LC 1 contributor ian ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31909 0 contributor 2010-02-13 12:21:37 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#posting-messages Comment: Why is the optional argument in the middle? Isn't it more convenient when copy/pasting code to make optional modifications at either end without having to precisely place the cursor somewhere in the middle? Particularly for piecing together arguments, too, since one could append the mandatory arguments first, and then if somewhere else some ports are required simple + them to the string. Admittedly, this would be crafting a string which then would have to be executed. And what about having an array of arguments? The second item is sometimes one argument, and sometimes another. So an array of arrays couldn't handled simply (e.g. sometime [1], other times [2]) when processing posts to multiple different domains and potential ports. Admittedly that be a rather informative filling multiple forms from multiple domains, but isn't that potentially desirable? Posted from: 72.253.36.224 32317 1 ian 2010-02-17 23:54:30 +0000 I don't understand what the text starting with "And what about having an array of arguments?" to the end is referring to. 32568 2 ian 2010-02-23 11:33:46 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It's in the middle because I was trying to keep targetOrigin at the end, since it looks weird to have targetOrigin in the middle, between the message being sent and the ports being sent. (This is starting to get implemented. If you would really like this changed, it would be helpful if you could contact implementors who have this implemented, and ask them if they'd be willing to change it. In particular, I think WebKit has an implementation of this. Not sure if the others do yet.) 32581 3 zcorpan 2010-02-23 12:42:16 +0000 Opera has implemented this, but we'd be happy to change so that the optional argument is at the end. http://lists.w3.org/Archives/Public/public-html/2010Jan/0578.html 33961 4 Ms2ger 2010-03-27 09:23:05 +0000 http://html5.org/tools/web-apps-tracker?from=4869&to=4870