This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18674 - Regarding "3. If the result of executing the script is void (there is no return value), then the URL must be treated in a manner equivalent to an HTTP resource with an HTTP 204 No Content response." - nowhere is specified what exactly should be done in ca
Summary: Regarding "3. If the result of executing the script is void (there is no retu...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-24 05:58 UTC by contributor
Modified: 2012-10-29 23:52 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2012-08-24 05:58:01 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#javascript-protocol
Complete: http://www.whatwg.org/c#javascript-protocol

Comment:
Regarding "3. If the result of executing the script is void (there is no
return value), then the URL must be treated in a manner equivalent to an HTTP
resource with an HTTP 204 No Content response." - nowhere is specified what
exactly should be done in case of HTTP 204 response during navigation. Should
we abort navigation attempt and stay with the active document? Should we
revert to about:blank? Throw exception? 

Posted from: 95.211.27.23
User agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0) Gecko/20100101 Firefox/10.0
Comment 1 Ian 'Hixie' Hickson 2012-10-29 23:52:31 UTC 
The "Resource handling" step of the Navigation algorithm, plus the HTTP spec, seem to define 204 completely. What more should it say?