Posts made by Opera-QA-Team

Starting the discussion

@kenedsf: Hello, for VPN Pro issues please contact our dedicated team at vpn-pro@support.opera.com

@simcard78: Hi, thanks for spotting. It's a known issue, RNA-1606 and it's awaiting fix.

@pkap1: Thanks for the feedback - we are happy to hear it!

@jojo0587: Hi, thanks for sharing. This is already known issue and as it's written in the blog post, "Some opera://settings sections may behave incorrectly due to the ongoing Settings rewrite". Will be fixed of course.

@blacksunray: Hello, we apologize for misleading you. The search box in the address bar was removed from version 126 and won't be available again.

@krishnakrverma: Thank you for your feedback about deprecating the Beta version of Opera and introducing the Early Bird program in the stable stream. We understand this is a significant change, and we want to clarify what it means for you.

First, this change will not impact the quality of the regular stable stream. The stable version remains our primary, fully tested release, and it continues to go through the same rigorous quality assurance, automated checks, and manual testing as before. Stability, performance, and reliability of the main browser remain our top priorities.

Second, the Early Bird program is entirely optional. It is meant for users who want earlier access to new features within the stable stream and are comfortable with the possibility of minor issues. If you prefer the most stable and predictable experience, you can simply stay on the regular stable version and ignore Early Bird.

Third, we are not removing our Developer stream. Opera Developer continues to exist as our earliest, most experimental channel, where new ideas and features are introduced and tested first. The new flow looks like this:
Developer → Early Bird (in stable) → Stable
By removing the separate Beta channel, we can shorten the time it takes to deliver product updates. Instead of maintaining three parallel consumer channels (Developer, Beta, Stable), we now focus on Developer for early experimentation and Early Bird within Stable for broader real‑world testing. This reduces duplication of work and allows improvements and fixes to reach all users faster, without lowering the bar for quality in the stable stream.

We truly appreciate everyone who has used Beta over the years and helped us improve Opera. Your feedback remains crucial, and the combination of Developer + Early Bird is designed to keep that testing spirit alive while making our release process more efficient and responsive.

@max1c: Thank you for your feedback about deprecating the Beta version of Opera and introducing the Early Bird program in the stable stream. We understand this is a significant change, and we want to clarify what it means for you.

First, this change will not impact the quality of the regular stable stream. The stable version remains our primary, fully tested release, and it continues to go through the same rigorous quality assurance, automated checks, and manual testing as before. Stability, performance, and reliability of the main browser remain our top priorities.

Second, the Early Bird program is entirely optional. It is meant for users who want earlier access to new features within the stable stream and are comfortable with the possibility of minor issues. If you prefer the most stable and predictable experience, you can simply stay on the regular stable version and ignore Early Bird.

Third, we are not removing our Developer stream. Opera Developer continues to exist as our earliest, most experimental channel, where new ideas and features are introduced and tested first. The new flow looks like this:
Developer → Early Bird (in stable) → Stable
By removing the separate Beta channel, we can shorten the time it takes to deliver product updates. Instead of maintaining three parallel consumer channels (Developer, Beta, Stable), we now focus on Developer for early experimentation and Early Bird within Stable for broader real‑world testing. This reduces duplication of work and allows improvements and fixes to reach all users faster, without lowering the bar for quality in the stable stream.

We truly appreciate everyone who has used Beta over the years and helped us improve Opera. Your feedback remains crucial, and the combination of Developer + Early Bird is designed to keep that testing spirit alive while making our release process more efficient and responsive.

@rnghwdbcs: Thank you for your feedback about deprecating the Beta version of Opera and introducing the Early Bird program in the stable stream. We understand this is a significant change, and we want to clarify what it means for you.

First, this change will not impact the quality of the regular stable stream. The stable version remains our primary, fully tested release, and it continues to go through the same rigorous quality assurance, automated checks, and manual testing as before. Stability, performance, and reliability of the main browser remain our top priorities.

Second, the Early Bird program is entirely optional. It is meant for users who want earlier access to new features within the stable stream and are comfortable with the possibility of minor issues. If you prefer the most stable and predictable experience, you can simply stay on the regular stable version and ignore Early Bird.

Third, we are not removing our Developer stream. Opera Developer continues to exist as our earliest, most experimental channel, where new ideas and features are introduced and tested first. The new flow looks like this:
Developer → Early Bird (in stable) → Stable
By removing the separate Beta channel, we can shorten the time it takes to deliver product updates. Instead of maintaining three parallel consumer channels (Developer, Beta, Stable), we now focus on Developer for early experimentation and Early Bird within Stable for broader real‑world testing. This reduces duplication of work and allows improvements and fixes to reach all users faster, without lowering the bar for quality in the stable stream.

We truly appreciate everyone who has used Beta over the years and helped us improve Opera. Your feedback remains crucial, and the combination of Developer + Early Bird is designed to keep that testing spirit alive while making our release process more efficient and responsive.

@derschlingel: Thank you for your feedback about deprecating the Beta version of Opera and introducing the Early Bird program in the stable stream. We understand this is a significant change, and we want to clarify what it means for you.

First, this change will not impact the quality of the regular stable stream. The stable version remains our primary, fully tested release, and it continues to go through the same rigorous quality assurance, automated checks, and manual testing as before. Stability, performance, and reliability of the main browser remain our top priorities.

Second, the Early Bird program is entirely optional. It is meant for users who want earlier access to new features within the stable stream and are comfortable with the possibility of minor issues. If you prefer the most stable and predictable experience, you can simply stay on the regular stable version and ignore Early Bird.

Third, we are not removing our Developer stream. Opera Developer continues to exist as our earliest, most experimental channel, where new ideas and features are introduced and tested first. The new flow looks like this:
Developer → Early Bird (in stable) → Stable
By removing the separate Beta channel, we can shorten the time it takes to deliver product updates. Instead of maintaining three parallel consumer channels (Developer, Beta, Stable), we now focus on Developer for early experimentation and Early Bird within Stable for broader real‑world testing. This reduces duplication of work and allows improvements and fixes to reach all users faster, without lowering the bar for quality in the stable stream.

We truly appreciate everyone who has used Beta over the years and helped us improve Opera. Your feedback remains crucial, and the combination of Developer + Early Bird is designed to keep that testing spirit alive while making our release process more efficient and responsive.

@rick2: Thank you for your feedback about deprecating the Beta version of Opera and introducing the Early Bird program in the stable stream. We understand this is a significant change, and we want to clarify what it means for you.

First, this change will not impact the quality of the regular stable stream. The stable version remains our primary, fully tested release, and it continues to go through the same rigorous quality assurance, automated checks, and manual testing as before. Stability, performance, and reliability of the main browser remain our top priorities.

Second, the Early Bird program is entirely optional. It is meant for users who want earlier access to new features within the stable stream and are comfortable with the possibility of minor issues. If you prefer the most stable and predictable experience, you can simply stay on the regular stable version and ignore Early Bird.

Third, we are not removing our Developer stream. Opera Developer continues to exist as our earliest, most experimental channel, where new ideas and features are introduced and tested first. The new flow looks like this:
Developer → Early Bird (in stable) → Stable
By removing the separate Beta channel, we can shorten the time it takes to deliver product updates. Instead of maintaining three parallel consumer channels (Developer, Beta, Stable), we now focus on Developer for early experimentation and Early Bird within Stable for broader real‑world testing. This reduces duplication of work and allows improvements and fixes to reach all users faster, without lowering the bar for quality in the stable stream.

We truly appreciate everyone who has used Beta over the years and helped us improve Opera. Your feedback remains crucial, and the combination of Developer + Early Bird is designed to keep that testing spirit alive while making our release process more efficient and responsive.

@andrew84: Yes, that's correct it's our latest release of beta before January 14.

Starting the discussion

@blacksunray: Hi, thanks for spotting the issue. It is already reported and will be fixed.

@kamil777b: Hello, we know the issue, but thanks for the reminder!

@max1c: Good to hear, thanks for letting us know : )

@whisperer: Hi, thanks for reporting, we know this issue and it's awaiting fix.

@max1c: Hello, what OS is it? I checked at Windows11 and can't reproduce it.

@donq: Thanks for letting us know!

Starting the discussion