Daniel’s blog

—a Mac perspective on the Web seen through the Opera desktop browser

No longer showing XML parsing errors

Wednesday, September 28, 2011 12:11:00 PM

Following up to my article explaining the occasional ‘XML parsing failed’ error messages. Starting with today’s Opera Next release the error will be handled silently by reparsing the document as HTML. The user will no longer be shown an error and prompted to reparse as HTML. The error message will be printed to the error console instead.

This is a move from developer centric do-what-the-spec-says to what other browsers are doing by applying magic that fixes the problem for the end user. To be, this error seems like just one of those things that should be on by default in a separate Developer/Debug Mode in the browser.

As we no longer show the error, it also means that Opera will no longer be a fully valid XML parser.

Update: the ODIN blog has more information about this change.

Better than average network performance with HTML5 YouTubeBacking up Opera user data (11.50 and newer)

Comments

bachokocho Wednesday, September 28, 2011 12:36:14 PM

shame on mainsteam rip

ПавелGemorroj Wednesday, September 28, 2011 12:54:33 PM

+1

Michael A. Puls IIburnout426 Wednesday, September 28, 2011 3:25:40 PM

I checked to see if this messed with responseXML.document.documentElement with xhr while trying to load a broken xml file and thankfully it doesn't and it still returns null.

Would still be cool to have an opera:config option to turn it off though when needed. Looked but didn't see one. This would be especially cool for override_downloaded.ini and acid3.acidtests.org. Something like UserPrefs|XMLReparseAsHTMLOnError=0.

Swapnil RustagiSwapnil99pro Wednesday, September 28, 2011 4:00:46 PM

Hello, Daniel,

DSK-312074 (Bypass XML parsing failed message by automatically reparsing as HTML) needs to be re-done. This change has broken something. Now Acid3 only displays 99/100 score on a fresh install with this build 1076.

This is what fails in Opera 12.00 build 1076-

Test 80 failed: XML well-formedness error didn't stop script from executing.

Charles SchlossChas4 Wednesday, September 28, 2011 4:08:29 PM

http://support.apple.com/downloads/ Is a page that gives the error every time, Did it most of the time to me unless they fixed it

It used to do it to me every time not sure why no it did not today

Swapnil RustagiSwapnil99pro Wednesday, September 28, 2011 4:12:44 PM

Originally posted by Chas4:

http://support.apple.com/downloads/ Is a page that gives the error every time


Working fine here with a clean-install.

Anonymous Thursday, September 29, 2011 12:48:18 PM

匿名者 writes: in this build, i can't use java JBOSS applicaiton server version 7.0's administrator console. follow error throw by opera 12 Inline script compilation Int(b.substr(0,e-0), Syntax error at line 2683 while loading: expected expression, got

Charles SchlossChas4 Friday, September 30, 2011 3:33:34 AM

Originally posted by Swapnil99pro:

Working fine here with a clean-install


I used to get it all the time a few days ago on there

Charles SchlossChas4 Sunday, October 2, 2011 8:30:40 PM

I do get it on http://support.apple.com/downloads/

XML parsing failed: syntax error (Line: 43, Character: 0)

Swapnil RustagiSwapnil99pro Monday, October 3, 2011 3:37:27 AM

Originally posted by Chas4:

I do get it on http://support.apple.com/downloads/


Probably something wrong in your configuration. The site works perfect and I even started a download successfully.

Clean-install of Opera Next 12.00 build 1076
Windows 7 SP1 x86

Charles SchlossChas4 Monday, October 3, 2011 12:48:11 PM

Originally posted by Swapnil99pro:

Probably something wrong in your configuration. The site works perfect and I even started a download successfully.

Clean-install of Opera Next 12.00 build 1076
Windows 7 SP1 x86


Nope using the stable 11.51 as my main, I know it has changed in 12

Charles SchlossChas4 Friday, October 14, 2011 3:16:45 AM

Got it again and copied the error into the Safari report a page to apple on the damaged page

strange that it not always shown as error some times it goes straight to the page