This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I think the name of this algorithm is very confusing. Please either pick another name, or clarify that it's not supposed to mutate the resource it's directed at.
Which algorithm? The one at: http://www.whatwg.org/specs/web-apps/current-work/complete.html#submit-mutate-action ...named "mutate action"? If so, how is it confusing? It seems like a very apt name to me. Why would you think it would mutate a resource? "Action" is a URL.
(In reply to comment #1) > Which algorithm? The one at: > > > http://www.whatwg.org/specs/web-apps/current-work/complete.html#submit-mutate-action Yes, that one. See URL in the bug report metadata. > ...named "mutate action"? If so, how is it confusing? It seems like a very apt > name to me. Why would you think it would mutate a resource? "Action" is a URL. What is being mutated?
The "action" URL.
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: Seems clear to me.
Ian, "seems clear to me" isn't helpful. Could you explain what's being mutated? Re-opening, instead of raising in Tracker, as this seems to be editorial and it should be possible to resolve with low overhead.
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: Seriously, how is this not clear. The algorithm is named "Mutate Action". It mutates the action URL. What is the problem here? What would you want it to be called instead?
"Mutating a URL" sounds like "navigation" to me. A more minimal change would be to say "URL Mutate action".
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: Well it _is_ a navigation, eventually. You mutate the URL then GET it. So what's the problem? "URL Mutate action" isn't even grammatically correct as far as I can tell. Did you mean "Mutate action URL"?
Please stop marking issues as resolved when they are not. WRT question: note of these are "grammatically correct", as they are just sentence fragments. That being said, I'm ok with your proposal.
My only proposal is to not change this. 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: The reporter has said that he is confused by this but every time he tries to describe how he is confused, it turns out his interpretation is in fact correct. So the spec seems fine.
Raised as <http://www.w3.org/html/wg/tracker/issues/138>.
I like how you propose something in your issue CP which you never suggested in the bug.
Unless I'm missing something, the CP exactly says what I said in comment #9, and you rejected in #10.
I had assumed that when you said "your proposal" you meant my proposal, which was to change nothing. Please be more explicit in the future.