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 13895 - To clarify -- on getting, does the setter preprocessor still need to be run? I.e. if the input is "http://example.org:99999", should port be 0, 65535, or 99999?
Summary: To clarify -- on getting, does the setter preprocessor still need to be run? ...
Status: CLOSED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-24 23:28 UTC by contributor
Modified: 2011-12-29 21:12 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-08-24 23:28:02 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#url-decomposition-idl-attributes
Complete: http://www.whatwg.org/c#url-decomposition-idl-attributes

Comment:
To clarify -- on getting, does the setter preprocessor still need to be run?
I.e. if the input is "http://example.org:99999", should port be 0, 65535, or
99999?

Posted from: 2620:0:1001:1001:72cd:60ff:fea8:58be
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Comment 1 Ian 'Hixie' Hickson 2011-10-15 19:30:26 UTC 
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: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Could you elaborate? What would suggest that the setter preprocessor would run?
Comment 2 Rachel Blum 2011-12-29 21:12:26 UTC 
The question was, ultimately, does the standard say anything about IDL behavior on getting values when the underlying object is invalid/malformed. 

I believe misread the spec to assume that was even possible. I.e. I missed that an authority-based URL must have been parsed and hence cannot be malformed. (http://example.org:99999 obviously is malformed)


Hope that clarifies it.  Closing, unless you feel an urgent need to elaborate more :)