- From: Jukka K. Korpela <jkorpela@cs.tut.fi>
- Date: Sat, 30 Nov 2013 15:40:39 +0200
- To: www-validator@w3.org
2013-11-30 14:45, Michael[tm] Smith wrote: >> Maybe I missed something; where does "URL Living Standard" say something >> about stripping line breaks? > > The parts of the algorithms where U+000A and U+000D are handled It says in different contexts that U+000A and U+000D cause “parse error”. In normal spec parlance, that would mean that the input does not constitute a URL; here it is pseudo-defined by saying this: “A parse error indicates a non-fatal mismatch between input and requirements. User agents are encouraged to expose parse errors somehow.” If the intent is that the offending character is just ignored, then this should be said. I think the normal interpretation is that “parse error” terminates parsing, or at least means that parsing cannot return a valid item. Yucca
Received on Saturday, 30 November 2013 13:41:13 UTC