Opera stable 70 - news
-
l33t4opera last edited by sgunhouse@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.
-
A Former User last edited by
@l33t4opera Thanks.
Opera\launcher.exe --force-color-profile=srgbhas a space between.exeand--forceNo space or ... is not accepted. #forced-colors does nothing on my system.
-
l33t4opera last edited by l33t4opera
@vegelund The space beetwen the path and switch is mandatory - necessary to make is work. If there's no spaces in the path, the quotation marks should not be needed.
The flag seems to be working here with or without quotes, also with different values e.g. "color-spin-gamma24".
Maybe you can check if it works, when you put "srgb" in quotation marks.
Anyway, AFAIK "srgb" may not work for every graphics card. -
A Former User last edited by
No worries, I’ll just wait for
#force-color-profileto return.sRGB has always worked before under normal settings, HWA on.
Chrome 84.0.4147.105 has it.
-
l33t4opera last edited by sgunhouse
@vegelund I have read your previous comments now, so it's working for you when the HWA is disabled?
Yes, the flag is present in the latest Chrome stable and beta (85.0.4183.48), but not in Opera stable/beta. Perhaps it's disabled for some reasons in the Opera, or it's just a matter of different versions of Chromium.
Nevertheless, there should not be a difference if you enable the feature thought the flag or using the switch, if it works it should work in both cases. -
A Former User last edited by
With HWA on, switch is not working. Flag worked as intended before removed.
-
l33t4opera last edited by sgunhouse
@vegelund Can you leave the HWA enabled, and launch the Opera with "--disable-gpu-compositing" switch, and then with "--disable-dwm-composition" (one at the time). Does any of that help? I mean if you run it together with "--force-color-profile" switch. Don't forget to add a space between the switches too.
Edit: They say here the issue is fixed on Chrome .105 for all platforms, so it looks like it should work also in the Opera, when it will be updated to that Chromium version. Of course if it's the same issue as in your case.
-
l33t4opera last edited by l33t4opera
@iamkarthik, @vegelund The flag #force-color-profile is back in the stable .95, so you can update and check if it works for you
;-) -
l33t4opera last edited by
New build (also security update) - Opera stable 70.0.3728.95
;-)
The change log and the announcement.
It includes a small stability update and other minor fixes.
Chromium is updated to version 84.0.4147.105.
-
A Former User last edited by
@l33t4opera said in Opera stable 70 - news:
@iamkarthik, @vegelund The flag #force-color-profile is back in the stable .95, so you can update and check if it works for you
;-)Jolly good! Thanks for your support and update @l33t4opera
#force-color-profileis back inopera://flags/and all is well.
-
l33t4opera last edited by l33t4opera
New, minor update - Opera stable 70.0.3728.106
;-)
The change log and the announcement.
@vegelund You're welcome;-) -
A Former User last edited by
@leocg Allowing users to search in their open tabs shouldn't require the replacement of an efficiently designed core feature with a version that's slower, more difficult to use, and less efficient.
-
l33t4opera last edited by l33t4opera
Small update - Opera stable 70.0.3728.119
;-)
The change log and the announcement.
-
-
-
l33t4opera last edited by
New build (also security update) - Opera stable 70.0.3728.133
;-)
The change log and the announcement.
Chromium is updated to version 84.0.4147.125.
-
l33t4opera last edited by l33t4opera
New, small (also security) update - Opera stable 70.0.3728.144
;-)
The change log and the announcement.
Chromium is updated to version 84.0.4147.135.
