First Opera 12.50 'Marlin' snapshot released


Recommended Posts

First bite of 12.50 ?Marlin?: Clipboard API, redesigned key event handling, -webkit- CSS, and Notification Center

It?s bright, warm, and sunny in Oslo. Naturally all the hardcore geeks are indoors making you the next version of Opera Next. Opera 12.50 will be codenamed ?Marlin? and it is starting off strong. Here are some of the highlights that are still works-in-progress: An implementation of the Clipboard API, support for some -webkit prefixed CSS properties, a redesigned keyboard event handling,and integration with Mac OS X 10.8?s Notification Center. Lets dive into it!

Clipboard API exposes the following new events: copy, cut, and paste; for text/plain and text/html content.

Opera?s keyboard event handling has been updated to DOM Events Level 3 and includes various changes to improve our compatibility in the area of key handling.

As previously announced, a subset of widely used -webkit- prefixed CSS properties are now mapped to their -o- counterpart. The supported properties include -webkit-box-shadow, -webkit-transform, -webkit-transform-origin, -webkit-border-radius, -webkit-border-top-left-radius, -webkit-border-top-right-radius, -webkit-border-bottom-left-radius, -webkit-border-bottom-right-radius, -webkit-transition, -webkit-transition-delay, -webkit-transition-duration, -webkit-transition-property, and -webkit-transition-timing-function. You should, however, not rely solely on -webkit- prefixes!

Users on the yet-to-be-released Mac OS X 10.8 ?Mountain Lion? will see notifications integrated into the system wide Notification Center instead of seeing notifications through Growl. Older system versions will still see notifications through Growl. Settings are available in Preferences: Advanced: Notifications as well as in System Preferences: Notification Center: Opera Next.

Known issues:

  • Key event handling on Mac has some remaining legacy issues

WARNING: This is a development snapshot: It contains the latest changes, but may also have severe known issues, including crashes and data loss situations. In fact, it may not work at all.

Download Opera Next

Distribution note: Starting with the auto-update for this build, 64-bit capable Macs will receive a 64-bit only binary instead of the Universal Binary.

Source: Opera Desktop Team blog

Link to comment
Share on other sites

Whoa, hell just froze over! Opera actually making use of OS X provided APIs instead of reinventing the wheel themselves? I can't believe I'm reading this.

Link to comment
Share on other sites

This is stupid but not really Opera's fault :/

As previously announced, a subset of widely used -webkit- prefixed CSS properties are now mapped to their -o- counterpart. The supported properties include -webkit-box-shadow, -webkit-transform, -webkit-transform-origin, -webkit-border-radius, -webkit-border-top-left-radius, -webkit-border-top-right-radius, -webkit-border-bottom-left-radius, -webkit-border-bottom-right-radius, -webkit-transition, -webkit-transition-delay, -webkit-transition-duration, -webkit-transition-property, and -webkit-transition-timing-function.
Link to comment
Share on other sites

This is stupid but not really Opera's fault :/

I hate it when browsers use the prefixes...I don't want to see -o-, -moz-, -webkit- or -ms-...They should just all suppose the CSS standard...

Nice list of items...Though now I have to figure out how to disable the Clipboard API's...One thing I liked about Opera, they didn't support it before lol

Link to comment
Share on other sites

I hate it when browsers use the prefixes...I don't want to see -o-, -moz-, -webkit- or -ms-...They should just all suppose the CSS standard...

Those prefixes are there for reason. They are there for the parts of CSS that hasn't been finalized yet. When they are finally finalized, the browser vendors will support non-prefixed versions too. It's just to make sure each vendor supports the final draft instead of everyone supporting different versions of the standard. It would be a massive mess with no prefixes and each browser just supporting random versions of drafts.

Granted, there has been issues with this approach too (buggy implementations) but it's the best way there is to provide a way to add incoming standards support to browsers so that people can start trying them out.

Link to comment
Share on other sites

Those prefixes are there for reason. They are there for the parts of CSS that hasn't been finalized yet. When they are finally finalized, the browser vendors will support non-prefixed versions too. It's just to make sure each vendor supports the final draft instead of everyone supporting different versions of the standard. It would be a massive mess with no prefixes and each browser just supporting random versions of drafts.

Granted, there has been issues with this approach too (buggy implementations) but it's the best way there is to provide a way to add incoming standards support to browsers so that people can start trying them out.

it's a massive mess right now. moreso than if prefixes wheren't used, and coders instead properly checked for support.

Link to comment
Share on other sites

Those prefixes are there for reason. They are there for the parts of CSS that hasn't been finalized yet. When they are finally finalized, the browser vendors will support non-prefixed versions too. It's just to make sure each vendor supports the final draft instead of everyone supporting different versions of the standard. It would be a massive mess with no prefixes and each browser just supporting random versions of drafts.

Granted, there has been issues with this approach too (buggy implementations) but it's the best way there is to provide a way to add incoming standards support to browsers so that people can start trying them out.

I would say that it's good in theory. But it's not. Most times when people add it to their site, they only add some of the browsers. Most often webkits, sometime moz. And most times leave out the CSS without the prefix, or IE's or Opera's, so browsers like Opera, who do support those features now, can't see them. I've seen a lot of examples like that when trying to learn some more CSS3. I've been having to use an extension that adds support.

Link to comment
Share on other sites

This topic is now closed to further replies.