13786 2011-08-15 14:44:28 +0000 Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter. 2011-12-07 18:26:34 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Server-Sent Events (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#text/event-stream P3 normal --- 1 contributor ian annevk ian julian.reschke mike public-webapps public-webapps-bugzilla oldest_to_newest 55088 0 contributor 2011-08-15 14:44:28 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Multipage: http://www.whatwg.org/C#text/event-stream Complete: http://www.whatwg.org/c#text/event-stream Comment: Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter. Posted from: 113.197.157.202 User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1 55094 1 annevk 2011-08-15 15:39:28 +0000 Yeah, the processing rules for unknown parameters just need to be changed. Instead of aborting the request they should simply be ignored, as is the case for unknown parameters with text/html, text/css, etc. 55636 2 ian 2011-08-23 00:05:35 +0000 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 problem is that a number of servers actually send charset="" parameters, so we have to support it. We can't ignore it because if the character encoding is set to something else then we would be corrupting the data if we interpreted it as UTF-8. (What if one day we all move on to some new encoding scheme? It's important that we be able to migrate. We can't easily do so if we are ignoring charset=""!) 55668 3 annevk 2011-08-23 08:00:55 +0000 If we are moving to a new encoding schema that would be problematic for HTML, CSS, etc. resources too. I think it would be better if it is problematic in the same way. 56262 4 ian 2011-09-04 03:30:45 +0000 How would it be problematic for HTML and CSS? They actually support charset="", so a new type wouldn't be a problem at all as far as I can tell. 56268 5 annevk 2011-09-04 07:15:23 +0000 HTML and CSS have a fallback encoding too (typically Windows-1252 or some locale-specific encoding). The resource does not become unsupported. Here the fallback would just be fixed to UTF-8. 56269 6 annevk 2011-09-04 07:16:13 +0000 And to be clear, UTF-8 would remain to be the only encoding that works until we decide otherwise. 56317 7 ian 2011-09-04 21:21:59 +0000 I don't really see why we'd actively ignore charset="" here. 56320 8 annevk 2011-09-04 21:25:52 +0000 Because for MIME types in general you always ignore unknown parameters. That is, you do not halt processing. And if charset is a recognized parameter it should not behave differently from HTML when confronted with an unknown value. 58379 9 ian 2011-10-18 20:28:48 +0000 (In reply to comment #8) > Because for MIME types in general you always ignore unknown parameters. That > is, you do not halt processing. But it isn't unknown. > And if charset is a recognized parameter it > should not behave differently from HTML when confronted with an unknown value. I don't see why. HTML does all kinds of crazy stuff we shouldn't copy. 58406 10 annevk 2011-10-19 01:28:03 +0000 It is not just text/html. Every other MIME type that takes a charset parameter behaves this way, text/css, text/javascript. 58814 11 ian 2011-10-25 00:11:21 +0000 Are you arguing those are any less crazy? :-) 59024 12 ian 2011-10-26 23:33:31 +0000 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: I see no value in silently ignoring the charset="" parameter. We don't ignore any other parameter, why ignore this one? We only support it at all because some servers insist on sending it, according to implementation feedback. 59483 13 annevk 2011-11-02 14:18:37 +0000 We should ignore the other parameters too. Name one format that is similar to text/event-stream. 59510 14 ian 2011-11-02 17:03:28 +0000 Ah, if you want to ignore all parameters that's a different matter. 61099 15 ian 2011-12-07 18:26:34 +0000 Done.