New Opera developer 39

[rstacey]

rstacey last edited by

Very happy to confirm VPN is working great again. Thanks, guys!

[donq]

donq last edited by

In the previous release comments, you have reported general slowness when browsing with the ad-blocking feature on. This has been fixed – please check out the newest version and let us know if everything is OK for you.

Seems to be fixed, thanks a lot

[donq]

donq last edited by

Custom ad-blocking rules
Since we introduced native ad blocker, we have got a lot of requests to have a possibility to add custom lists. First we introduced an option to load them from a local file, today we add functionality to load it from any URL. Just make sure you have advanced settings turned on, then in the “Custom block lists…” dialog you can add any address, which contains ad-blocking rules in EasyList format.
Usually, such files contain modification date as well as the update frequency. These values determine how often the list will be automatically updated. If the list definition says that the list expires in 4 days, that means it will be updated every 4 days starting from the last modification date mentioned in the document.

This looks somewhat broken. My localised list (is it in correct format? I don't know) doesn't seem to have modification date and update frequency included; when I load it from disk, everything is well, but using url (http://gurud.ee/ab.txt) makes Opera to push CPU at 33% or 50% load constantly (i5 here). No activity is seen in Opera task manager.

[vroomen]

vroomen last edited by

Hi Guys,

Since the upgrade to 39.02245.0 my Opera Developer won't function anymore in Sandboxie. It does function fine outside of the Sandbox though.

Hope you can get it fixed asap.

Kind regards,
Peter

[l33t4opera]

l33t4opera last edited by

New build - Opera developer 39.0.2248.0, the change log, and the announcement

Here’s a fresh update of our Developer stream, available for you. It contains some improvements, and bug fixes.

Power saver mode – phase 2

Progressive timer throttling. Timers are throttling a little bit to start with, and then increased after a 10s delay. This affects background tabs, both with and without power save mode. Without power save mode, we throttle to 10s after the delay, and with power save mode to 30s.

Timers originating from cross-origin iframes, are now throttled in foreground frames. These are throttled to 1s at first, and 10s after the delay. This is mostly targeted at ads, but might affect other use cases.

Personal news

As you can see in the change log, this team is not wasting time! Many changes, and bug fixes are listed there. All to improve the experience with your own, personal news.

\m/ :cheers: