New Opera developer 57
-
A Former User last edited by
Have you fixed the bug in bookmarking? Versions 55 & 56 will not bookmark in the normal manner because the doorhanger coming from the heart symbol is blank.
-
l33t4opera last edited by l33t4operaHi @concretable, I do not experience this issue by myself, please add some more details, like e.g. screenshot, or file a
report here. -
A Former User last edited by
I filed a bug report, but I can also describe what happens here.
- Try to bookmark a page from Bookmarks > Add to Bookmarks
- Doorhanger drops down from heart symbol in address bar. The door hanger should contain an image plus a folder selector.
- Click to drop down a list of folders and click the one desired. The bookmark should then be saved in there.
That result does not happen because the doorhanger is completely blank.
-
spaceshipone last edited by
Opera 57 dev PC.
how restore old (55.0) setting panel, in opera://flags is not possible because crashed and restarted, cannot set new value and after reload open setting panell. Only see error and crash. I want old Opera setting not f... chrome crap, when I cannot find anything and not see where is setting witch I want in that moment.Way You remove cookies setting - on, on without 3 party c, off, remove all etc. In 57 is gone, I cannot sett in on or off, clean it or do anything in this f... chrome panell.
Cannot login to my mail site beacose I must cookies on this, cannot open any site with ddos protection, I installed cookies add on but is not helped.
Fix this and remove chrome anoying from opera. -
-
-
-
spaceshipone last edited by
how fix to normal panel in old opera, I hate this chrome f... crap.I can't find the anything and can't normal use like old browser where I had everything set for myself and clearly, legibl I had everything set for myself, had everything knew where what is and how it is, Opera worked great wonderful as gold is. Maybe some extension can fix this madness and back normal opera settings.
-
-
spaceshipone last edited by
No i can't disable this beacose opera crashed and restarted when I try open settings after changes value in opera://flags.
How fix this issue and get old settings in this opera 57.0, From what I see is opera beta and opera stable also have a new (worse) settings panel. -
-
l33t4opera last edited by l33t4opera
New update - Opera developer 57.0.3098.1
;-)
The change log, and the announcement.
"This is the last Opera 57 developer update. Next week we’re rolling out 58 cycle.Hearing your voices, we’ve added the possibility to close pinned tabs, without having to first unpin them. You can do it from tab’s context menu on all operating systems. Furthermore, macOS users can do that from the File menu in the menu bar."
Important changes, and fixes:
- DNA-72331 [Mac] Shift+click on reload button should reload page bypassing cache.
- DNA-72657 Unable to play video content in macOS Mojave 10.14.
- Crash caused by deleted bookmarks.
- DNA-72812 Make TLS 1.3 enabled by default.
- Translations fix on the Settings page."
-
A Former User last edited by
I'm not sure if it was reported already, but I'm experiencing two problems with Opera Developer:
- After opening it, the first time the browser interacts with a text box it freezes for around 10 seconds and CPU usage rise to 100%;
- Opera Developer crashes on certain downloads, mainly small files. Downloads from Discord reliably make Opera Developer crash.
I suppose those are related to Problems with certain types of navigation triggers?
I'm using Xubuntu 18.04.
-
l33t4opera last edited by
Hi @furret29, I'm not experiencing that issues by myself, perhaps you can report them using Opera's bug report wizard.
-
l33t4opera last edited by
Hi again @furret29, I have an idea regarding freezing text boxes, open the opera:flags, and type "idle" in the search box. You should see 3 flags: #infinite-session-restore, #page-almost-idle, and #proactive-tab-freeze-and-discard. Disable the last one, relaunch the Opera, and check if it helps, and if not, try to disable all three flags, and if it still doesn't help, try to revert back to build 57.0.3082.0, and if the issue is gone, you can wait until it will be fixed in one of the further builds - one of the users wrote here, that similar problem appeared, after he updated to latest version.
