What’s new in Opera's snapshots: 7 October 2011
Today ushers in another interesting developer snapshot release of Opera desktop! As per usual, if you are using Opera Next you should already have this update — if not, download the snapshot separately.
You can read a more detailed summary of the updates in the snapshot changelog; the most interesting new additions are as follows:
Radial gradients
Opera has supported linear gradients for some time now, but there was still some way to go before we could claim to support the full gradients section of the CSS Image Values and Replaced Content Module Level 3 working draft. But no more! We now support the full gamut of gradients functionality, plus a little bit of a surprise for secret hunters...
Read more about linear gradients in our new dev.opera article, CSS3 radial gradients.
HTML5 error handling
One of the hotly anticipated fixes to HTML contained in HTML5 is error handling, i.e. what to do with badly formed markup. Previously browser vendors had to work out how to do this by themselves, which lead to differing implementations and therefore inconsistent errors. Earlier on in the year we published an experimental implementation of this in our new HTML5 parser, called Ragnarök — see 100% Ragnarök’n’roll on Opera Labs. Now we are pleased to announce the addition of the Ragnarök parser into our latest snapshot. Say goodbye to the misery of interoperability problems. Well, some of them, anyway.
<style> parsing bug fix
As a requirement to fix the well-known bug whereby <style> elements appended to the document aren't parsed immediately, the BeforeCSS and AfterCSS events are no longer dispatched for <style> elements, only for linked and imported style sheets. This is not a limitation: <style> element can still be retrieved and manipulated using the DOM.
Readers' comments 12
Left under the original article, as archived.
About this article
| Published in | ODIN blog |
|---|---|
| Date | October 7, 2011 |
| Author | Chris Mills |
| Tags | linear gradients, Ragnarök, Opera, snapshot, css3, html5 parser |
| Original | Internet Archive |
Martin KadlecFriday, October 7, 2011 8:25:04 AM
Can we get some hint?
Chris MillsFriday, October 7, 2011 8:40:01 AM
Originally posted by BS-Harou:
Ok then - look carefully at the first live demo in the CSS3 radial gradients article on dev.opera ;-)
Martin KadlecFriday, October 7, 2011 8:52:43 AM
Originally posted by chrismills:
I think I found it. Cool
Patrick O'ReillyFriday, October 7, 2011 9:21:40 AM
Charles SchlossFriday, October 7, 2011 3:55:04 PM
Constantine VesnaFriday, October 7, 2011 6:15:41 PM
NimeshFriday, October 7, 2011 7:33:10 PM
Cross posted from Opera Desktop Team Blog
Originally posted by MossMan:
Yes, weird.
writing <script src="todo.js" type="text/javascript"/> instead of <script src="todo.js" type="text/javascript"></script> is causing the problem, which used to work in earlier builds
http://files.myopera.com/nimeshthakkar/albums/6780452/todomanager_problem_with_build1085.png
Michael A. Puls IISaturday, October 8, 2011 3:50:49 AM
Originally posted by nimeshthakkar:
On an HTML page, that should cause the script to eat the rest of the page (or most of it depending on the markup), because in HTML, script is not a void element. It requires a closing tag.
It not eating the rest of the page in previous versions was a bug (but might have been done on purpose a long time ago to work around some site bugs at the time) that's fixed by implementing the HTML parser.
So, unless the todo manager is using that markup in an XML page, the bug is in the todo manager and it needs to be fixed so that it includes "</script>".
NimeshSaturday, October 8, 2011 6:37:53 AM
One more clarification, closing tag is required even if I'm providing source attribute (src="todo.js")
Michael A. Puls IISaturday, October 8, 2011 7:42:41 AM
Originally posted by nimeshthakkar:
Yes, it's still required. And, on a side, the type attribute isn't needed at all.
More specifically, these are the only elements in HTML that don't have close tags.
NimeshSaturday, October 8, 2011 8:31:40 AM
Originally posted by burnout426:
Thanks. I've updated the extension.
sacudWednesday, October 12, 2011 1:17:55 PM
are they some news about adding bookmark api for extensions?
I really like Opera, but i not using it only because there are no Xmarks extension.
From Xmarks they said that still from more than 10 months they waiting when Opera will add bookmark api for extensions.
Other browsers like Firefox and Chrome have such things but Opera not - why?