And extremely instructive for all the not advanced people.
Originally posted by Robert90:
When XML parsing fails for an application/xhtml+xml content type, why don't you sent a HEAD request with a Firefox or IE user agent string? When that one returns a content type of text/html you can be damn sure it's an HTML file and a server configuration fault.
Agree. Ciao, Igor
Henri SivonenThursday, October 6, 2011 10:57:34 AM
Seems like an XSS risk to reparse (as opposed to implementing XML5 and having well-defined rules that don't backtrack) for the same reason why we went through the trouble of not making the HTML5 parsing algorithm reparse if the end of file is seen inside a comment or a script.
Cutting SpoonFriday, October 7, 2011 11:12:47 PM
Incidentally, I think they just landed Ragnarok into Next.
ChrisMonday, October 10, 2011 9:50:32 AM
Originally posted by hellspork:
Maybe pop a bar that says "This page was repaired. If it still looks wrong, click [here] to let us know.
I don't understand why you think this is a good idea. Most people are not going to know what this means, and they are not going to care. They don't want to know about problems the browser encounters. They just want to browse the web.
Why interrupt and bother people with information they are never going to understand and care about in the first place?
Cutting SpoonMonday, October 10, 2011 10:00:08 AM
It's no different from the "Compatibility View" notification, more graceful than error page and less confusing if the render blows up due to actual parse failure. Most people won't notice - at all - unless the page is broken. Plenty don't even notice the password save dialog when it pops.
ChrisMonday, October 10, 2011 1:23:29 PM
Compatibility view notification?
FransMonday, October 10, 2011 3:48:15 PM
Originally posted by Chris:
Compatibility view notification?
Presumably a reference to IE.
TonyStarkAKAIronManSunday, November 20, 2011 11:00:01 AM
Since I don't know where to report such errors, here it is: http://www.catfootwear.com/FR/fr still has the same exact "XML parsing failed" error.
may be he set:
opera:config#UserPrefs|AutomaticallyreparseXHTMLwithparsingerrorsasHTML to off like I did? Then it throws the error with http://www.catfootwear.com/FR/fr here in 11.60 too.
... and I really want to thank the person who is responsible for adding that option to opera:config
FransTuesday, November 22, 2011 8:18:56 PM
Originally posted by QuHno:
may be he set:
opera:config#UserPrefs|AutomaticallyreparseXHTMLwithparsingerrorsasHTML to off like I did? Then it throws the error with http://www.catfootwear.com/FR/fr here in 11.60 too.
... and I really want to thank the person who is responsible for adding that option to opera:config
Sure, I can confirm that—and I prefer it—but that's a feature, not an error.
IgorWednesday, October 5, 2011 11:33:42 AM
Originally posted by SteveKong:
And extremely instructive for all the not advanced people.Originally posted by Robert90:
Agree.Ciao, Igor
Henri SivonenThursday, October 6, 2011 10:57:34 AM
Cutting SpoonFriday, October 7, 2011 11:12:47 PM
ChrisMonday, October 10, 2011 9:50:32 AM
Originally posted by hellspork:
I don't understand why you think this is a good idea. Most people are not going to know what this means, and they are not going to care. They don't want to know about problems the browser encounters. They just want to browse the web.Why interrupt and bother people with information they are never going to understand and care about in the first place?
Cutting SpoonMonday, October 10, 2011 10:00:08 AM
ChrisMonday, October 10, 2011 1:23:29 PM
FransMonday, October 10, 2011 3:48:15 PM
Originally posted by Chris:
Presumably a reference to IE.
TonyStarkAKAIronManSunday, November 20, 2011 11:00:01 AM
http://www.catfootwear.com/FR/fr still has the same exact "XML parsing failed" error.
FransSunday, November 20, 2011 11:16:25 AM
Originally posted by TonyStarkAKAIronMan:
Can't confirm on 11.60.
QuHnoTuesday, November 22, 2011 2:01:59 PM
Originally posted by Frenzie:
may be he set:
opera:config#UserPrefs|AutomaticallyreparseXHTMLwithparsingerrorsasHTML
to off like I did?
Then it throws the error with http://www.catfootwear.com/FR/fr here in 11.60 too.
... and I really want to thank the person who is responsible for adding that option to opera:config
FransTuesday, November 22, 2011 8:18:56 PM
Originally posted by QuHno:
Sure, I can confirm that—and I prefer it—but that's a feature, not an error.