Opera stable 70 - news

l33t4opera

l33t4opera @andrew84

Hi @andrew84, I will give my two cents on that only once, because unfortunately talking more about this particular case makes no sense for many reasons as in my opinion.

You are right that some flags should not be removed too early, because sometimes a feature still needs some work to be finished (and or some real bugs could last unnoticed during the development tests, that can be discovered by the users using the browser, while it's released).
The second thing is what also some others mentioned already. Some people like the old solutions in their browsers, like for example they like to use the old feature, not the new one with similar functionality, but not so quite appropriate for their way of using the browser.

I see two reasons for which a flag/old feature is removed from the code: First is that there's not enough resources and time to maintain it (together with the new one, offering similar functionality), and adjust it accordingly to the changes in the new versions of Opera. The second is the management decided about it for some own reasons.

A Former User @sgunhouse This post is deleted!

A Former User @sgunhouse

@sgunhouse said in Opera stable 70 - news:

As replied to your other post, the flag was removed as redundant. Sidebar extensions work.

But keyboard shortcuts still do not open sidebar extensions directly.
It’s a two-fase task. First open sidebar, then click chosen option or use chosen extension shortcut.

l33t4opera

l33t4opera @Guest

Hi @vegelund, yes it's two steps task unless the Sidebar is already active, so it should be considered as a drawback. Perhaps it can be kinda fixed in the way, that if you press the shortcut to activate Sidebars' extension, it will automatically activate the Sidebar, then the extension itself. Alternatively, when the Sidebar is closed, it could activate the extension in the toolbar, of course if the extension is allowed to do that.

A Former User @l33t4opera

@l33t4opera said in Opera stable 70 - news:

Hi @odinprokhozhiy, I just checked and it still works here on Linux (I can check it on Windows and Mac in few days, but I think the OS doesn't matter in this case): clicking the button in the Sidebar opens the extensions panel, changing the options works as well, opening folders, bookmarks, etc. works.
You can make more space for the websites by reducing the panel size - just hover your mouse over right edge of it, hold the mouse and move it to the left. Also, you can make the panel a bit more narrowed by changing few extension options.
By the way: try to enable opera:flags#extensions-toolbar-menu, restart the browser, disable the flag, restart again, and check if it's working. If not, I can check it again in few days, and try to figure out what is wrong in your case, that it doesn't work.

However, I would not recommend to use this extenstion for now, since it's really outdated (last update Nov. 24, 2017), and because of that can be very buggy (meaning that, not adjusted to recent Opera's version, several bugs are not fixed since years).

Instead of it, you can try another extension V7 Bookmarks, that is quit often updated and offers quite similar functionality.

Hi @l33t4opera, Thanks for the answer. I'll try V7 Bookmarks. Regarding Bookmarks By The Side, yes, it works, but only within the native opera's sidebar, and yes, the sidebar can be resized, but its minimal width is too large, some 350 pixels
or so. It may be fine for resolutions of 1920 pixels or more, but a lot of people including me still have to use lesser resolutions. In my case, it occupies approx. 30% of the screen width, it's way too much. In many cases all I need to see in the left panel is just the site icons and may be a few first letters of their names, 50 or 100 pixels would be quite sufficient. With the flag opera://flags/#sidebar-extensions-in-browser-sidebar one could see the Bookmars by the Side without the native sidebar and make it any width they liked. It was much more convenient. Now I have to consider migrating to another browser or reverting to an older version of Opera.

A Former User @l33t4opera

@l33t4opera Here's how it looked before and I'd like to keep it this way in the the future (I mean the width of the left pane)

l33t4opera

l33t4opera @Guest This post is deleted!

iamkarthik

iamkarthik

Hi,

The opera://flags/#force-color-profile seems to have disappeared. The browser is now unable to use the color gamut of my monitor fully. Colors look drab compared to how they were previously.

l33t4opera

l33t4opera @Guest

@odinprokhozhiy If you want to try a workaround for your extension (it should make it work from the toolbar), you can follow the below steps:
1. Download "manifest.json" and "neat.css" (also "neat-dark.css" if you use the dark theme) from here,

2. Run the Opera, go to opera:about, and make a note of the path to profile (or copy it), close the Opera,

3. Open your file explorer, navigate to that path, open "Extensions", there you should see "nfmcmkgigcijhkhpogobfhkdokdecjmb" and under it "2.1.5_0". Copy it to somewhere else, but outside "Extensions" (that is important to make it work) - you can copy it to Opera's profile folder, then rename it to e.g. "bmsbyside",

4. Open the renamed folder, delete "_metadata" subfolder, and copy the downloaded files to it (overwrite the original files),

5. Run the Opera, go to Settings > Extensions (Ctrl+Shit+E), and disable your installed extension (to don't be confused, when you enable modified one).
Enable "Developer Mode", click "Load unpacked", select the "renamed folder", and click "Open".

Now, you should see it on the list as "Bookmarks by the Side - toolbar", and you should be able to use it from the toolbar.

l33t4opera

l33t4opera @iamkarthik

Hi @iamkarthik, you can try to run the Opera with "--force-color-profile" switch, for example --force-color-profile=srgb.
The other accepted values can be e.g. "generic-rgb" or "color-spin-gamma24".

iamkarthik

iamkarthik @l33t4opera

@l33t4opera said in Opera stable 70 - news:

Hi @iamkarthik, you can try to run the Opera with "--force-color-profile" switch, for example --force-color-profile=srgb.
The other accepted values can be e.g. "generic-rgb" or "color-spin-gamma24".

Hi, thanks. I've done just that. I used "argb" (which I assume is how to write adobe RBG) and the colors pop now. A bit too much actually, I didn't realise my browser colors could be so saturated (⊙_⊙;). I was on DCI-P3 previously.

A Former User @l33t4opera

@l33t4opera Thank you, but it did not work for me. I must have done something wrong. However now I've restored Opera v69 and now everything works fine, so don't worry.

A Former User @iamkarthik

@iamkarthik said in Opera stable 70 - news:

The opera://flags/#force-color-profile seems to have disappeared. The browser is now unable to use the color gamut of my monitor fully. Colors look drab compared to how they were previously.

+1, I also miss #force-color-profile flag.

In Chrome 84.0.4147.105 it is there.

A Former User @Guest

I have been trying to get forced sRGB back to see correct colors on my monitor.

This is the solution I’ve found on Opera 70.0.3728.71, Windows 10.

Add --force-color-profile=srgb to target line after Opera\launcher.exe
Turn off hardware acceleration.

If HWA is on, colors briefly flash correctly upon browser startup, but then revert to duller presentation.
So, for some reason HWA influences color management.

Source: https://techdows.com/2020/07/chrome-84-force-color-profile-srgb.html

A Former User @Guest

Oh well, if you have HWA disabled, Google Maps 3D does not work (no Globe option).

So now I must choose between normal functionality and correct color reproduction
(as close as you can in WIN10 browser outside Adobe environments, that for my setup was forced sRGB).

iamkarthik

iamkarthik @Guest

@vegelund said in Opera stable 70 - news:

I have been trying to get forced sRGB back to see correct colors on my monitor.

This is the solution I’ve found on Opera 70.0.3728.71, Windows 10.

Add --force-color-profile=srgb to target line after Opera\launcher.exe
Turn off hardware acceleration.

If HWA is on, colors briefly flash correctly upon browser startup, but then revert to duller presentation.
So, for some reason HWA influences color management.

Source: https://techdows.com/2020/07/chrome-84-force-color-profile-srgb.html

I had the same problem of colours briefly correcting and then reverting to dull. This was when I used --force-color-profile=dcip3

I then tried --force-color-profile=argb, and this has made the wide color gamut permanent.

Of course, it does not make sense why this should make a difference, but it seems to be the case.

I did not try srgb, and I am loathe to try anything else in case it breaks the current working situation, so sorry about that.

I have HW acceleration turned on.

A Former User

Thanks, I tested but to no avail.

Since #force-color-profile is back in latest Chrome, I expect it to return in Opera soon.

@l33t4opera said:

you can try to run the Opera with "--force-color-profile" switch, for example --force-color-profile=srgb.

Am I doing correct by editing the shortcut?

C:\Users\vegel\AppData\Local\Programs\Opera\launcher.exe --force-color-profile=srgb

Opera.exe does not have a target field to change:

C:\Users\vegel\AppData\Local\Programs\Opera\70.0.3728.71\opera.exe

iamkarthik

iamkarthik @Guest

@vegelund Are you per chance launching Opera by clicking the automatically created shortcut on the desktop or pinned to taskbar? That shortcut generally points to the specific Opera ver 70.0.3728.71 etc, instead of to the launcher.

Try creating a shortcut to the launcher itself, on your desktop or taskbar, and launch Opera using that. In that case the argument appended to the launcher shortcut should apply.

l33t4opera

l33t4opera @Guest

@odinprokhozhiy Perhaps it wasn't clear enough. In point 3 I meant the "2.15x" folder, which you need to copy outside the "Extensions" directory, and rename it to something else. It should work, it's working here. Anyway, since you are reverted to Opera 69 and you are fine with it, it's ok. However, please keep in mind, that it's not recommended to use older main version mainly for the security reasons.

l33t4opera

l33t4opera @Guest

@vegelund It looks correct. It could be wrong, if the path to the launcher.exe includes some spaces. In that case, you should put it within "...".

Anyway, have you tried already to enable another flag the "opera:flags#forced-colors" ? Some people say, that it helped them in such of cases.