New Opera developer 43
-
l33t4opera last edited byNew update - Opera developer 43.0.2420.0
The change log, and the announcement.
"Here is a weekly update on the developer stream.
There are a lot of fixes included. I listed the most important below:
– Video pop-out displayed subtitles, and it’s possible to detach Hangouts window.
– Aspect ratio is kept while resizing the video pop-out.
– Speed dial fixes, such as: redraw in a new tab after resizing window, suggestions displayed twice, scroll bar hardly visible, when hovering over it.
We’re still working on prerendering. Next week hopefully you’ll be able to test the whole feature.
Grab the builds, and let us know if you find something interesting. We have hope for your active feedback as always."
The Chromium has been updated to version 56.0.2906.0.
\m/ :cheers: -
viewer2012 last edited by
Please Support Check box or shift/CTRL For select multiple URLs in History Page.
and
this future:
https://ituku.tk/di/LM3M1/capture.pngyou can find this future in Yandex Browser.
-
bor-fox last edited by
In full screen, no buttons - "minimize and maximize"
Ubuntu 16.04Please help me
-
joakimwallden last edited byIf you mean real full screen (F11), there is not supposed to be any window buttons, like in all other browsers.
In maximised mode, I have close, minimise and restore buttons, as expected. Ubuntu 16.10.
-
l33t4opera last edited by
New update - Opera developer 43.0.2423.0
The change log, and the announcement.
"Hi, please grab fresh developer builds, that we have prepared for you.
Full change log contains all the details, but the most important fixes are as follows:
– Crash, when closing settings during importing data from other browsers was fixed.
– New translations are integrated to Opera 43.
– There is no strange behaviour, when dragging a folder from the bookmarks bar to the tab bar.
– Close button was moved to the left on video pop-out window (we don’t know why it wasn’t done before).
Known issue: missing Opera icon in O-menu (Linux only)."
\m/ :cheers: -
l33t4opera last edited by
New update - Opera developer 43.0.2431.0
The change log, and the announcement.
"In the first Opera 43 developer blog post we announced new feature coming in: Address bar speculative prerenderer. Here are some more details:
When you browse the web a lot of time is spent waiting for pages to load, and a lot of energy has gone into optimizing page load, both from browser makers, and from site makers. Today that is highly optimized, and it is hard to make big improvements.
So let us think outside the box, what is the best way to complete a task earlier? To start earlier! And that is the whole trick in the “prerendering” feature.
Predict
There are two ways we can predict what page the user will soon load. When the current page tells us so, and when we can determine from the users actions, that they are about to load something.
Pages can use the < link rel=prerender … > tag, and for instance Google uses that for search results, if they are pretty sure of what you will load next.
When someone writes in the address bar, they are humanly slow. Sometimes it is obvious what they will write after just 1-2 characters, but they will just keep writing or arrowing through suggestions for millions, or billions of wasted clock cycles.
Result
We expect this feature to results in an average of 1 second faster loads from the address bar. This means, that instant page loads become much more common. Of course this depends a lot on how predictable the user is, and how fast the user is. I expect you who read this to benefit less, than the average user, but I might be wrong.
Security/Privacy
We try hard to not load anything, that would be bad to load. Should you notice anything else, let us know right away!
There are also settings in the privacy section to disable this completely.
Monitor
If you want to see how predictable you are, fire up Opera, browse some, then load opera:predictors, and see what green lines there are (that is when we “know” what you are about to do). You can also look at the prerender section in opera:net-internals, and see when we are prerendering right now and historically.
Limitations
Some studies indicate about 80% of prerendered pages become used, which means, that 20% of the prerender page loads are for nothing, and has wasted electrons. Therefore, we don’t do this in battery saving mode (could argue, that we should still do it).
Since every preload (currently) needs to spawn a new process, it also won’t work, if you have reached the process limit, or if you are not predictable enough in your use of the address bar."
The Chromium has been update to version 56.0.2914.3.
\m/ :cheers: -
rocky-iv last edited by
Opera Developer 43: Extension - Background worker
Support Needed
Is there a way to disable (Background worker) extension?
I'm using Manjaro Linux operating system.Background worker doesn't appear in Extension List, but is present in Opera Task Manager.
Thanks
Rocky-IV -
joakimwallden last edited by
Opera 43 restarts on Ubuntu 16.10 64-bit:
Run Opera with --ssl-version-max=tls1.3.
Go to a site that uses TLS 1.3 (e.g. https://www.cloudflare.com/).
Click on the padlock. Opera restarts.It still restarts (43.0.2431.0), e.g. https://istlsfastyet.com/.
-
iamonkara last edited by
When starting an episode on Netflix I get this error
Whoops, something went wrong...
Unexpected Error
There was an unexpected error. Please reload the page and try again.
Error Code: M7121-1331-P7
Version information
Version: 43.0.2431.0 - Opera is up to date
Update stream: developer
System: Mac OS X 10.12.1 64-bit
Browser identificationMozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2914.3 Safari/537.36 OPR/43.0.2431.0 (Edition developer)
-
viewer2012 last edited by
Please change Opera://history page Like chrome://history (Chrome Browser) For selecting Custom URLs.
-
joakimwallden last edited by
Opera 43 restarts on Ubuntu 16.10 64-bit:
Run Opera with --ssl-version-max=tls1.3.
Go to a site that uses TLS 1.3 (e.g. https://www.cloudflare.com/).
Click on the padlock. Opera restarts.Or just go to a site (Google’s) which uses QUIC (and TLS 1.3) and click on the padlock. Make sure QUIC is used; it isn’t always.
