@burnout426: Since I have no vimeo account, I cannot watch this "unrated" video. However, I can just press F11 on any website, also here or in opera settings, to trigger the crash. So while I recognised it first when trying to fullscreen a video with its webplayer GUI, it is irrelevant, as the issue seems in the fullscreen "backend" of the browser. Toggling hardware acceleration and any ANGLE backend does not solve it. ID if the last crash upload: 3cce6274-f34f-4eb3-b1be-4696d2240521
Interestingly, while automatic uploads were disabled before, and no OPERA_CRASH_EMAIL was set, I see a lot of older crash IDs and uploads from earlier May. Not great in terms of privacy, but a different topic.
Best posts made by MichaIng
-
RE: Opera 112 developerBlogs
-
RE: Opera 112 developerBlogs
However, as said, it does not matter how or from where fullscreen is enabled. The crash report was done hitting F11 from the crash reports page.
-
RE: Opera 112 developerBlogs
@burnout426
Not "some" non-video pages trigger it, too, but literally all pages, no matter how fullscreen is enabled, including clicking the fullscreen option on "any" video webplayer GUI and F11. -
RE: Opera 112 developerBlogs
@burnout426: Yes. just tested a fresh standalone Opera developer, and it crashes, too.
-
RE: Opera 112 developerBlogs
@burnout426: For completeness: I also tried to toggle the 3 fullscreen related flags (typing "fullscreen" into the flag search), but they have no effect on it either.
-
RE: Opera 112 developerBlogs
@burnout426: Thank you very much. Until then, reverting to 111.0.5159.0 works very well, just replacing opera.exe and renaming the autoupdate folder. A native downgrade option would be still nice :).
Latest posts made by MichaIng
-
RE: Opera 112 developerBlogs
@burnout426: Thank you very much. Until then, reverting to 111.0.5159.0 works very well, just replacing opera.exe and renaming the autoupdate folder. A native downgrade option would be still nice :).
-
RE: Opera 112 developerBlogs
@burnout426: For completeness: I also tried to toggle the 3 fullscreen related flags (typing "fullscreen" into the flag search), but they have no effect on it either.
-
RE: Opera 112 developerBlogs
@burnout426: Yes. just tested a fresh standalone Opera developer, and it crashes, too.
-
RE: Opera 112 developerBlogs
@burnout426
Not "some" non-video pages trigger it, too, but literally all pages, no matter how fullscreen is enabled, including clicking the fullscreen option on "any" video webplayer GUI and F11. -
RE: Opera 112 developerBlogs
However, as said, it does not matter how or from where fullscreen is enabled. The crash report was done hitting F11 from the crash reports page.
-
RE: Opera 112 developerBlogs
@burnout426: Since I have no vimeo account, I cannot watch this "unrated" video. However, I can just press F11 on any website, also here or in opera settings, to trigger the crash. So while I recognised it first when trying to fullscreen a video with its webplayer GUI, it is irrelevant, as the issue seems in the fullscreen "backend" of the browser. Toggling hardware acceleration and any ANGLE backend does not solve it. ID if the last crash upload: 3cce6274-f34f-4eb3-b1be-4696d2240521
Interestingly, while automatic uploads were disabled before, and no OPERA_CRASH_EMAIL was set, I see a lot of older crash IDs and uploads from earlier May. Not great in terms of privacy, but a different topic. -
RE: Opera 112 developerBlogs
Doing any video (webplayer GUI) of website (F11) fullscreen crashes the browser here, on Windows 11. Not sure whether its hardware or driver related, or how to debug. It is an AMD Ryzen 5 PRO 7530U with internal graphics and latest official AMD drivers+software. It worked well on Opera developer 111.0.5159.0.
-
RE: Opera 111.0.5159.0 developer updateBlogs
@kened: Right. Disabling the enhanced address bar in settings, i.e. the address bar suggestions, fixes it. I think the suggestions GUI element invisibly overlays the address bar, so that only the very first mouse click goes through. That one lets the suggestions pop up, making any further click impossible. This also breaks double clicks, hence selecting individual words from the URL is not possible.
-
RE: Opera 111.0.5151.0 developer updateBlogs
@leocg Yes it is a Chromium flag. Not sure whether it is intended that some of those have no effect in Opera, but if Opera decided to hardcode enabled tab mute via audio indicator, despite the fact that this flag exists in underlying Chromium code, then I consider this a faulty decision, especially mostly breaking the pinned tabs feature.
-
RE: Opera 111.0.5151.0 developer updateBlogs
Two bugs:
- Since a longer time, regardless whether "#enable-tab-audio-muting" flag is enabled or not, the tab audio indicator always functions as mute button. I find this annoying, especially audio-playing pinned tabs are very difficult to select/switch to, unintentionally toggling audio instead.
- Since a few developer versions, selecting individual words of the URL in the address war does not work anymore. Despite clicking multiple times, the whole URL remains selected. Strangely, it works for opened tabs after a browser (re)start, but once any new tab is created, it is not possible anymore in any tab.