My OperaThe My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Opera 11.60 History pushState baseURI question
Opera 11.60 broke navigation on my website. It does not longer because I added a workaround.It's all related to setting the baseURI (wrongly) after ajax loading and history.pushState
To see the problem:
Open this page in Opera 11.60:
1 http://www.webonomic.nl
2 Click internet
3 Inspect any element and readout the baseURI property, it's set to
http://www.webonomic.nl/webdesign/internet
While Opera 11.52, Firefox and Chromium set it to
http://www.webonomic.nl/
according to the base href element of original the document.
I looked up the specs:
http://www.w3.org/TR/html5/webappapis.html#script-s-base-url
A base URL
A URL, set when the script is created, used to resolve relative URLs. If the base URL is set from another source, e.g. a document base URL, then the script's base URL must follow the source, so that if the source's changes, so does the script's.
I'm not sure if a pushState is changing the source, I can imagine it does, so Opera's 11.6 behaviour does make sense somewhere. On the other hand it doesn't change the source of the script?
A couple of questions raise:
1 Is Opera's 11.60/12.00 new behaviour a bug?
2 How do we set the base url of a json document?
3 How do I set the base URL for a script?
To me Opera 11.5, Firefox, and Chromium's behaviour does make sense by keeping the base URI of elements to the href attribute of the base element after a pushState event.
Can anyone shed some light?
I have a similar problem with using jQuery Mobile with Opera 11.60. Opera 11.50 and all other browsers work correctly, while the Opera 11.60 broke links after loading a jQuery Mobile page, and after that Opera 11.60 set document.baseUri to a wrong value. I have no idea what to do since document.baseUri is read-only. The only one workaround I could imagine is to change href attribute of all links exactly for Opera 11.60, but it doesn't seem to me like a good idea.
13. January 2012, 11:15:46 (edited)
I'm also disappointed, and it's a nasty problem, because it's not about a misplaced pixel or some rendering artifacts, (they do occur as a side effect), it's seriously BREAKING websites.
Everybody is touting that HTML5 and ECMA script 5.1 is increasing cross browser compatibility,
` Once all browsers have HTML5 parsers, the same markup will produce the same DOM across all conforming browsers. `
http://dev.opera.com/articles/view/labs-100-ragnarok-n-roll
and now it's implemented: it's NOT true.
If at least somebody can acknowledge this is a bug: OK, we see it fixed in 12 or 11.62.
Filed bugs by my company:
DSK-349834
DSK-350296
Everybody is touting that HTML5 and ECMA script 5.1 is increasing cross browser compatibility,
` Once all browsers have HTML5 parsers, the same markup will produce the same DOM across all conforming browsers. `
http://dev.opera.com/articles/view/labs-100-ragnarok-n-roll
and now it's implemented: it's NOT true.
If at least somebody can acknowledge this is a bug: OK, we see it fixed in 12 or 11.62.
Filed bugs by my company:
DSK-349834
DSK-350296
