I am a fan of your browser, and I appreciate the innovative features and user-friendly interface that Opera offers. However, I have a suggestion that I believe could significantly enhance the privacy and independence of Opera.

Given the increasing concerns about privacy and data security, especially in light of Google's history of data collection and other controversial practices, I propose that Opera consider developing its own firmware and moving away from its reliance on Google's Chromium platform.

While I understand that Opera has a long-term partnership with Google and benefits from the open Android ecosystem, I believe that creating an independent platform could provide Opera with greater control over its features and privacy settings. This could also help alleviate some of the privacy concerns raised by users[3].

Moreover, Opera's European roots and compliance with the GDPR's robust framework could be leveraged to create a browser that truly prioritizes user privacy and data security. This could set Opera apart from other browsers and attract users who value privacy.

I understand that this is a significant undertaking that would require substantial resources. However, I believe that in the long run, this could enhance Opera's reputation as a secure and independent browser, and ultimately attract a larger user base.

Thank you for considering my suggestion. I look forward to seeing how Opera continues to innovate and prioritize user privacy.

Here is a list of 30 potential benefits of Opera moving away from Google's Chromium platform and developing its own firmware:

1. Enhanced privacy by reducing reliance on Google's infrastructure known for data collection.
2. Increased control over the browser's development direction and feature set.
3. Ability to innovate without constraints imposed by the Chromium project.
4. Differentiation from other browsers, offering a unique selling proposition.
5. Potential for improved security through proprietary technology.
6. Freedom from the Chromium monoculture, contributing to web diversity.
7. Opportunity to tailor the browser to specific user needs and preferences.
8. Possibility to integrate unique features that may not be possible with Chromium.
9. Control over the update cycle and feature rollout.
10. Ability to set new standards for web browsers independent of Google's agenda.
11. Potential to attract users concerned about Google's market dominance.
12. Opportunity to leverage Opera's European roots and GDPR compliance for better privacy.
13. Potential for a more streamlined and optimized browser performance.
14. Ability to offer a more personalized user experience.
15. Greater flexibility in responding to new web technologies and standards.
16. Potential to build a community-driven development process.
17. Opportunity to create a more secure ecosystem for extensions and add-ons.
18. Possibility to offer a more transparent and user-focused data policy.
19. Ability to foster partnerships with other tech entities independent of Google.
20. Potential to create a more robust and resilient browser against cyber threats.
21. Opportunity to develop new revenue streams not tied to Google's ecosystem.
22. Ability to provide a more consistent experience across different devices.
23. Potential to build a stronger brand identity distinct from Google.
24. Opportunity to lead in areas like performance, battery efficiency, and resource usage.
25. Ability to offer a competitive alternative in markets where Google is less dominant.
26. Potential to collaborate with other non-Google platforms and services.
27. Opportunity to set a precedent for tech independence in the industry.
28. Ability to contribute to a more balanced and competitive browser market.
29. Potential to drive innovation in web browsing without Google's influence.
30. Opportunity to align with the growing movement towards digital sovereignty.

without "/" and stil force to search instead of opening

380456067_3670915963156375_8761022607343328471_n.jpg

But there was a time, as they were fiddling with this feature where you could customise it to do something like what you are describing or the tab search. And I think you could also fiddle around with the background config settings.

I'm not happy with the current instant search implementation, as it does both page content and tab titles and I pretty much 100% want just tab titles. It made the operation very fast for me, as it would only pop up a few hits and I could select the right one very quickly. Now I have to type more and/or pause to select what I want.

Similar here was the old vertical Ctrl+Tab behaviour with full page preview. easy to select the right one. In fact this was one of the final features that got me to switch from Firefox's brain-dead horizontal cycler. Then Opera did the same! 😞

Anyway, it's generally really annoying when they remove features you were used to and replace them with inferior substitutes. But, it's subjective, which is why we need customisation.

However, all the software vendors are guilty of this!

Okay, maybe it is supposed to be on the system, lemme download google for a bit.

forget it, i am gonna download microsoft edge

Version information and settings

Android: EMUI 12.0.0
Model: Huawei Mate 20 Pro (LYA-L29)
Opera for Android Version: 73.1.3844.69816
Adblocker: enabled
Data savings: disabled
VPN: Disabled

I might have messed it up. Any help appreciated.

While I'm logged in with my Google Account, after clicking an image on Google Image Search to view the bigger version of it, the "Open Image in new tab", "Save/Copy Image" and "Copy image address" options on the big image disappear, the image isn't clickable, does not change my mouse cursor to a hand, and does not show image size.
Expected behavior on an example image:

Glitchy behavior while logged in (image can't be clicked or accessed, super annoying):

This only happens when I'm logged in, so Google itself is messing something up on the browser and possibly other browsers too.

I inspected elements and it seems like it's an annoying DIV that is blocking me from hovering over or clicking the image, and my extensions are unable to block the unholy DIV element too.

Someone please tell me what is happening or where I should ask for help to fix this, it was working fine until recently, it was fine before when the last Opera GX update was or so.

Example link: https://www.google.com/search?q=mc+color+codes&client=opera-gx&hs=Oe3&source=lnms&tbm=isch&sa=X&ved=2ahUKEwiAnaaq7NT8AhW2rJUCHTRyCs8Q_AUoAXoECAEQAw&biw=1879&bih=939&dpr=1&sfr=vfe#imgrc=4cOqEuqQT2bvJM
Selector to the DIV that seems to be causing me issues: #Sva75c > div.DyeYj > div > div.dFMRD > div.pxAole > div.tvh9oe.BIB1wf > c-wiz > div > c-wiz.n4hgof > div.MAtCL.b0vFpe > div.zHcOi

I don't know if I explained myself correctly... xd