19982 2012-11-16 09:51:28 +0000 Give pointer or specifics for HTML forms encoding special handling 2013-09-04 13:09:03 +0000 1 1 1 Unclassified WHATWG Encoding unspecified All Windows 3.1 RESOLVED DUPLICATE 23103 P2 normal Unsorted 1 duerst annevk mike pub-w3 sideshowbarker+encodingspec oldest_to_newest 78385 0 duerst 2012-11-16 09:51:28 +0000 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). 78404 1 annevk 2012-11-16 12:37:23 +0000 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. 78407 2 annevk 2012-11-16 12:51:49 +0000 *** Bug 19940 has been marked as a duplicate of this bug. *** 92968 3 annevk 2013-09-04 13:09:03 +0000 I forgot about this bug and fixed it elsewhere. *** This bug has been marked as a duplicate of bug 23103 ***