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 19982 - Give pointer or specifics for HTML forms encoding special handling
Summary: Give pointer or specifics for HTML forms encoding special handling
Status: RESOLVED DUPLICATE of bug 23103
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: All Windows 3.1
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-16 09:51 UTC by Martin Dürst
Modified: 2013-09-04 13:09 UTC (History)
2 users (show)

See Also:

Attachments

Description Martin Dürst 2012-11-16 09:51:28 UTC 
The spec says:

"Note: HTML forms and URLs require non-terminating encoders and have therefore special handling ..."

but it isn't specific enough to know what should be done. Either be more specific, or provide a pointer to where that's specified (or say it's not yet specified currently).
Comment 1 Anne 2012-11-16 12:37:23 UTC 
So for HTML it is specified, but not in terms of the Encoding Standard. For URLs it is specified in terms of the Encoding Standard, but we may want to change the exact handling for URLs. (Currently you get "?" in URLs whereas some browsers give you "&#{decimal code point};" instead like you get for HTML forms (in all browsers).)

I have been thinking about getting everyone to unify the two behaviors so an encoder error would always emit "&#{decimal code point};" unless you terminate on an encoder error.
Comment 2 Anne 2012-11-16 12:51:49 UTC 
*** Bug 19940 has been marked as a duplicate of this bug. ***
Comment 3 Anne 2013-09-04 13:09:03 UTC 
I forgot about this bug and fixed it elsewhere.

*** This bug has been marked as a duplicate of bug 23103 ***