Opera 139 Developer Adds Native Right-Click Page Element Blocking

Announced on October 14, 2026, in the Opera 139 Developer release blog post, the new capability expands Opera's built-in ad blocker—which the company has bundled with its desktop browser since 2016 —with point-and-click element removal. For longtime Windows power users and browser tinkerers, the concept immediately recalls the iconic element picker popularized by the uBlock Origin extension. By baking this workflow directly into the browser's context menu, Opera is attempting to give everyday users surgical control over webpage clutter with zero initial setup.

How Opera’s New Element Blocker Works​

According to Opera's Desktop team announcement for Opera 139 Developer, the feature is integrated directly into the browser's native ad-blocking engine and requires no configuration to enable. Instead of digging through extension menus or inspecting Document Object Model (DOM) trees, users interact with unwanted page components straight from the right-click context menu.

Opera’s implementation offers two primary workflows alongside a built-in safety net:

• Single-Element Removal (Block this element): When you encounter a stray banner, floating box, or distracting page widget, you can right-click it directly and select Block this element. Opera makes the selected container disappear immediately.
• Batch Cleanup (Block multiple elements): If a webpage is littered with clutter, choosing Block multiple elements switches the cursor into an interactive crosshair mode. Users can highlight and remove several distinct page sections one by one in a single session.
• Pattern Matching via Slider: Inside the multi-element workflow, Opera includes a small adjustment slider. According to the release notes, this slider helps users broaden or refine their selection to catch repeated structural blocks—such as entire rows of advertisements or recurring promotional card lists—all at once.
• Per-Site Persistence and Instant Undo: Every blocked item is saved on a per-site basis, meaning the clutter stays hidden the next time you load that domain. If you accidentally nuke a navigation bar or an essential login box, Opera provides an immediate Undo button to reverse the action on the spot.

Section Summary: Opera 139 Developer introduces native Block this element and Block multiple elements context-menu commands, complete with a crosshair selector, a repetition slider, an Undo button, and per-site memory.

Native Convenience vs. uBlock Origin’s Element Picker​

As Neowin noted when highlighting the update, anyone who has spent time taming the web with uBlock Origin will find Opera’s new tool very familiar. While Opera has not stated whether uBlock Origin inspired its design, comparing the two reveals an important distinction between surface-level UI convenience and deep filter architecture.

According to uBlock Origin’s official GitHub documentation, the extension actually divides manual page cleanup into two separate tools: the Element zapper (which temporarily removes an element until you reload the page) and the Element picker (which creates a permanent network or cosmetic filter saved to your custom rules list). When you click an item with uBlock Origin's eye-dropper tool, it opens a modal dialog proposing specific network rules or CSS cosmetic selectors. It also provides two distinct sliders: one on the left to adjust DOM traversal depth (how large an area of the page to target) and one on the right to adjust filter specificity (how narrowly or broadly to match similar elements). Power users can preview the result, manually edit the generated rule syntax, or add wildcards before clicking Create.

Opera’s announcement describes a much more streamlined, consumer-facing abstraction. While it replicates the core benefit of uBlock Origin’s picker—persistent per-site hiding and a slider to catch repeated elements —Opera has not disclosed how its underlying rules engine operates. The official release notes do not specify whether Opera is simply applying local CSS cosmetic hiding or blocking underlying network requests, nor do they indicate whether users can view, edit, or export a custom list of the elements they have blocked.

For users who already rely on uBlock Origin—which remains available in the Opera Add-ons store, and which Opera previously pledged to keep supporting alongside other Manifest V2 extensions even as Google Chrome moved to disable them —Opera's native tool will not replace a full-fledged filtering framework. However, for casual users who just want to banish an obnoxious sidebar widget without learning what a CSS selector is, Opera's right-click approach lowers the barrier to entry considerably.

Section Summary: While uBlock Origin exposes raw network and cosmetic filter creation with dual depth/specificity sliders, Opera packages persistent element hiding into a simpler, zero-setup right-click tool aimed at everyday convenience.

The Cat-and-Mouse Reality of Manual Element Blocking​

Will a manually blocked element stay gone forever? In theory, per-site persistence means you only have to zap an annoying box once. In practice, veterans of the ad-blocking wars know that manual element targeting can be fragile.

As uBlock Origin’s documentation explains when troubleshooting why removed elements sometimes reappear after a page reload, modern websites frequently use dynamically generated URLs or randomized CSS class and ID attributes that change every time a page loads. Furthermore, as Neowin points out, major web platforms actively rotate ad wrappers and scripts to defeat static blocks. When a website redesigns its layout or randomizes its DOM structure, a rigid selector saved by an element picker can stop matching. While uBlock Origin allows experienced users to inspect the DOM and manually craft wildcard rules to counter variable selectors, it remains to be seen how resilient Opera's automated slider and per-site memory will be against shifting page markup.

Broader Improvements in Opera 139 Developer and How to Test It​

Beyond the ad-blocker upgrade, the October 14 Opera Desktop blog post outlines several notable under-the-hood improvements and bug fixes arriving in this cycle:

• Pop-up Protection Upgrade: Opera enabled #popup-protection, restricting sites to displaying only one pop-up at a time and extending the mechanism to cover all pop-ups.
• Vertical Tabs & Sidebar Polish: Users can now drag and drop tabs within the auto-hiding vertical tabs panel both inside the same window and across separate browser windows. Opera also fixed a bug that left a 4-pixel strip of the sidebar visible after auto-hiding.
• Media & Touch Fixes: The build resolves WebCodecs H.264 encoder errors on WhatsApp Web (web.whatsapp.com), fixes an "Error 100" video playback failure on Paramount+, and restores touch responsiveness on websites when using touchscreens.
• Stability & Settings: The release includes a Chromium bump (the post's regular release notes reference Chromium 154.0.8037.17), restores missing options that broke Opera account synchronization, polishes React Settings pages, and patches crashes across autofill, the AI panel, DevTools, tab collections, and the Windows installer.

If you want to test the element blocker on your PC today, you will need to download Opera 139 Developer, which is available via standard and portable installers for Windows, alongside builds for macOS and Linux (deb and RPM packages). Keep in mind that Opera has not announced when—or if—this tool will graduate to the Stable channel. As Opera cautions on its official Developer channel page, pre-release builds are intended for advanced users and testing; features are still in development, builds can occasionally crash, and not every experiment makes the cut for the final stable browser.

For Windows users who prefer a clean browser without managing third-party extensions, Opera's native element blocker is a smart, pragmatic addition to its built-in privacy toolkit. If it proves reliable during Developer testing, right-clicking page clutter into oblivion could soon become second nature.