@simcard78: I feel your pain.

koimark
@koimark
Nerd from Finland. Registered Opera user since 2001.
Best posts made by koimark
- Blogs
-
RE: Opera 67 developer update comes with an experimental new workspace featureBlogs
Tab stack are back, kind of. There should be option to "Move tab to Workspace X" in somewhere.
-
RE: Opera 97.0.4704.0 developer updateBlogs
@pepik110: I just came here to inform the same. Random crashes occurs.
-
RE: Opera 98 developerBlogs
@ralf-brinkmann: Excellent news. I hope next weeks version bring this to Developer version too. It would ne nice to see what kind of actual code changes this fix needed.
-
RE: Opera 101.0.4829.0 developer updateBlogs
I'm not sure if this is related to this build but I updated my browswer with two windows open. After update the second window (which have only 3 tabs) does not allowed clicking tabs. Address bar etc. works but I cannot change tabs and tabs does not contain close x's - I could close those tabs via CTRL+W and window closed after the last one. Reopening last closed tab opened new windows and then tab contains closing button. It's weird and could be coincidence but thought to share it anyway.
-
RE: Opera 113.0.5222.0 developer updateBlogs
@ralf-brinkmann: I think I would like this feature IF i could teach myself to use fa less tabs.
I've switched from Workspaces to Tab Island but still quite a mess. I like that Opera allows many ways to arragen tabs - problem is me.
-
RE: Opera 121.0.5572.0 developer updateBlogs
@krishnakrverma: Opera is based on Chromium - and adds features and modifications to that. New features or popup-windows or changes are made of Chromiums. => all of those should be inspected and if necessary modified by Opera. So herecould be the BUG: Sometimes all of those changes are not noticed and this can happen.
But also we all know that we are using Developer version - which allows testing of premature version of Opera. It's better to allow big changes to being tested than waiting that every single detail has been fixe. When Developer moves to Next it's still unfinished and will contain bugs. And so called stable version always contains bugs too. -
RE: Opera 121.0.5572.0 developer updateBlogs
@pclaudel1: I think she meant that bug is identified and fixed internally and we see the fix when next developer build is published. Probably next monday or tuesday. Very annoying bug - I forgot that and always crashed twice when searching for tab. (That's a problem with tab-o-holic with about 250 tabs
Latest posts made by koimark
-
RE: Opera 122.0.5643.59 beta updateBlogs
@koimark: And still not. No problem, I'm waiting developer build anyway...
- Blogs
-
RE: Opera 123.0.5658.0 developer updateBlogs
This is not a bug but suggestion. Could there be a way to change location of tab strib scrolling area. It's now on the top of tab strib and It's annoying when Windows 11 have those screen selection or settings area there and also often whole app get selected or changing between windowed mode and full screen mode. Normally you can scroll with mouse wheel that tab strip and it's working nice. But when there are scrolling available you must use cursor.....
For me that is caused by good old Logitech Trackman Marble Mouse which does not have scrolling but it still best for me.
Does anyone else have similar wish. Put tab strip scrollin bar under to tab strip.
I have so many tabs that tab scrolling must be enabled. -
RE: Opera 123 developerBlogs
Fascinating that Chrome has been in stable version 138.0.7204.158 in 15.7. and now is on stable 140.0.7339.881. Of course Opera must test their own code with it but still I would think that at least Opera Developer could(should) be quite near the Stable version of Chrome. But of course this is neverending race. I still occasionally test Vivaldi but always come back to Opera. Other options are not for me.
It would be fascinating to see under the hood how the process is done in Opera. Who decides that version is selected for next branch and can they jump over something. (OK we will skip 139 branch completely etc. - OK Chrome 139 was released month ago and Chrome 140 two days ago. So I will already regret this message but the sake of conversation send it anyway. -
RE: Opera 122.0.5629.0 developer updateBlogs
Just the sake of curiosity because of Opera user since 3.6 - I have missed something but what are meaning of RNA in changelog? I think CHR is Chrome/ium and DNA is normal bugs but RNA seems to start in smaller number and it started couple of builds ago in 122-series?
-
RE: Opera 121.0.5572.0 developer updateBlogs
@pclaudel1: I think she meant that bug is identified and fixed internally and we see the fix when next developer build is published. Probably next monday or tuesday. Very annoying bug - I forgot that and always crashed twice when searching for tab. (That's a problem with tab-o-holic with about 250 tabs
-
RE: Opera 121.0.5572.0 developer updateBlogs
@krishnakrverma: Opera is based on Chromium - and adds features and modifications to that. New features or popup-windows or changes are made of Chromiums. => all of those should be inspected and if necessary modified by Opera. So herecould be the BUG: Sometimes all of those changes are not noticed and this can happen.
But also we all know that we are using Developer version - which allows testing of premature version of Opera. It's better to allow big changes to being tested than waiting that every single detail has been fixe. When Developer moves to Next it's still unfinished and will contain bugs. And so called stable version always contains bugs too. -
RE: Opera 121.0.5572.0 developer updateBlogs
I did'n (as far as I know) change any settings but I have too much tab and tab islands and with this version when I choose tab the tab bar does not always stay in that place at alla. So I have island with couple of tabs in same domain and I choose one but after that tab bar does not show this tab island and I must scroll tab bar to find it. Has anyone noticed this kind of behaviour? After update I have used ai to arrange tabs to tab island.
- Blogs
-
RE: Opera 121.0.5565.0 developer updateBlogs
@koimark: Continuing my monologue. Disabling all the extension did not help. Version 121.0.5558.0 works but 5565 and 5566 does not work. I would like to keep my tabs, passwords etc. intact.