Posts made by saidtorres3

@sgunhouse OperaGX

@ricardob Totally agree

In the latest version of OperaGX (114.0.5282.218), the outline border has been moved to the outer edge of the window, instead of the edge of the website. In the legacy design, this border was positioned below the tabs, creating a clear visual separation between the tabs and the website content.

This change has introduced a few usability issues:

1. Reduced Tab Clickability: With the border no longer separating the tabs from the rest of the interface, it’s harder to distinguish and click on tabs.
2. Tab Size Increase: In the new design, the active tab enlarges when selected. This resizing can cause accidental closures of adjacent tabs, especially when toggling between tabs quickly with the mouse. While that is out of the scope of this request, it's worth mentioning to share more context why the new design is bad.

While I understand there’s an "Elements Background" setting to create a visual separation between the tabs and their background, it feels unpolished and visually unappealing.

Also, the outline being on the window boders, give me a feeling that I am on streaming platform like AnyDesk and it give me a feeling like its not in full screen, when it is. It a very strange feeling.

Here are images illustrating the difference:

Legacy:

New degisn:

Suggestion: Please consider restoring the legacy behavior where the border was positioned below the tabs, or provide a cleaner, more visually cohesive way to separate tabs from the rest of the interface. This would improve usability and address the accidental tab closures caused by the current design.

Additional Feedback: Having the outline on the window borders gives the impression that I’m using a streaming platform like AnyDesk, rather than a browser. It creates the sensation that the browser isn’t in full-screen mode, even when it is. This disjointed experience feels quite strange and detracts from the immersive browsing experience.

@burnout426 said in Unclickable Top 40px in Extension Popups on Opera – BUG-906:

DNA-119560 Top area of extension popup window page doesn’t respond to clicks

That indeed fixed the bug, thanks for you hep!

@burnout426 Thank you, that's very helpful!

@burnout426 I tried disabling the opera://flags/#ui-compositor-multithreaded flag on OperaGX, but the issue still remains.

I wanted to bring attention to an issue I've encountered and already reported to Opera Support, but I thought it would be helpful to share it here too, just to keep a public record and see if anyone else has come across it, since opera bugs reports are not public. Here’s what I’ve found:

Summary:
In Opera (both the regular version and Opera GX), extension popups seem to have an issue where the top 40 pixels of the popup window become unclickable. This makes it impossible to interact with any buttons, links, or elements positioned in that area of the popup.

Steps to Reproduce:

1. Install and activate an extension that generates a popup (without a URL bar or typical navigation tools).
2. Open the extension's popup.
3. Try clicking on any interactive element within the top 40 pixels of the popup.

Expected Behavior:
Ideally, everything in the popup should be clickable, no matter where it's located.

Actual Behavior:
Unfortunately, the first 40 pixels from the top remain unclickable, preventing any interaction with elements like buttons or links in that area.

Additional Details:

• This issue only happens in extension-generated popups, not in standard browser windows.
• The issue persists across various extensions and after clearing the cache, disabling other extensions, or using different versions of Opera.
• Interestingly, this doesn’t happen in Google Chrome, which suggests it might be specific to Opera’s handling of extension popups without the URL bar or browsing tools.

Environment:

• Browser Version: Opera 114.0.5282.115 & Opera GX 114.0.5282.106
• Operating System: Windows 11
• Extensions Tested: Popup extension, Bitwarden
• Hardware: 11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz, RTX GPU

Here is footage of the issue:
https://www.youtube.com/watch?v=jfIa0bx7hZI

One of the principal affected extensions by this issue is Bitwarden, you can see the issue here: https://github.com/bitwarden/clients/issues/4270

@Naser007 It is still not fixed on normal Opera

It already got fixed on OperaGX 114.0.5282.93

@williama26 Opera for ARM is here!!: https://press.opera.com/2024/05/16/opera-goes-native-for-windows-on-arm/

@izeven: no