• Login
    • Search
    • Categories
    • Recent
    • Tags
    • Users
    • Groups
    • Rules
    • Help

    Do more on the web, with a fast and secure browser!

    Download Opera browser with:

    • built-in ad blocker
    • battery saver
    • free VPN
    Download Opera

    Opera One (v139 blocking custom WooCommerce REST API / AJAX fetch() payload & Shadow DOM widget

    Opera for Mac
    opera-one tracker-blocker ad-blocker
    2
    2
    941
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • coreblastsolutions
      coreblastsolutions last edited by

      Hi everyone,I’m the lead architect for Core Blast Solutions (coreblastsolutions.com), where we manufacture industrial abrasive blasting media and nozzles. Our e-commerce B2B platform runs on WordPress (Astra Pro + WooCommerce) with custom vanilla JS modules.Recently, a few of our European engineering clients reported that our interactive Abrasive Media & Nozzle Consumption Calculator on product pages fails to render or update pricing matrices when using Opera One (tested on 139.0.6053.22, Windows 11 64-bit), even though it works flawlessly in Google Chrome, Brave (Shields down), and Firefox.How the Feature Works (The Stack):On our WooCommerce product templates (for Steel Grit, Glass Beads, Aluminium Oxide, and Boron Carbide nozzles), we inject an interactive spec calculator via an Astra hook.When a user adjusts the mesh size slider or nozzle PSI input, our script dispatches an asynchronous fetch() POST request to a custom WordPress REST endpoint (/wp-json/cbs-calc/v1/telemetry-quote) and triggers a standard WooCommerce fragment refresh (/?wc-ajax=get_refreshed_fragments).The response dynamically updates the technical spec table and injects updated Product / Offer JSON-LD structured schema into the <head>.The Bug in Opera One:In Chrome (same Chromium Blink engine), the fetch() resolves in ~45ms with HTTP 200, and the DOM updates.In Opera One, the initial preflight Options / Post request to /wp-json/cbs-calc/v1/telemetry-quote immediately aborts in the DevTools Network tab with (failed) net::ERR_BLOCKED_BY_CLIENT (Initiator: cbs-media-tracker.min.js), and the calculator container stays stuck on the skeleton loader with Uncaught (in promise) TypeError: Failed to fetch.Even more bizarre: if the user has Opera Aria sidebar or Tab Islands active with Opera Tracker Blocker enabled, Opera’s cosmetic filter injects an inline display: none !important; style directly onto our <div id="cbs-abrasive-advisory-box"> wrapper! What I discovered while debugging in Opera DevTools:It turns out two things are colliding only in Opera:Because we named our JS bundle cbs-media-tracker.min.js (meant for tracking abrasive media flow rates, not user analytics!) and the REST route includes the word /telemetry-quote, Opera’s built-in Block Trackers heuristic engine flags our first-party script as an analytics beacon and kills the XHR/Fetch pipeline.Our container ID #cbs-abrasive-advisory-box triggers a false-positive match against -ad- / advisory in Opera’s native cosmetic filtering rules when Block Ads is enabled.My Questions for the Opera Web Compat / Dev Team:Why does Opera’s native Tracker Blocker block same-origin (same-site) first-party REST API POST requests to /wp-json/ just because the filename/endpoint contains strings like tracker or telemetry, whereas uBlock Origin in Chrome ignores first-party functional scripts?Aside from refactoring our WordPress plugin handles and renaming our DOM IDs on coreblastsolutions.com, is there a way to declare a first-party exception header or inspect exactly which internal Opera filter list rule (opera://settings/adBlockerLists) triggered the ERR_BLOCKED_BY_CLIENT abort in the Opera console?

      Reply Quote 0
        T 1 Reply Last reply
      • T
        Tomaszzzaa @coreblastsolutions last edited by

        @coreblastsolutions Hi! This is an interesting compatibility issue, especially since the same WooCommerce functionality works correctly in Chrome.

        We also run a WooCommerce-based online store with interactive product configurators for custom-made window blinds: https://luxrolety.pl/

        Based on the ERR_BLOCKED_BY_CLIENT message, I would first test the calculator with Opera's built-in ad and tracker blocking disabled for the website. If that resolves the issue, renaming the JavaScript file and REST endpoint to avoid words like "tracker" and "telemetry" seems like a reasonable next step.

        I would also check whether the widget's container ID is being affected by cosmetic filtering.

        Have you tested the calculator after disabling both blocking features? It would be interesting to know whether that resolves the problem completely.

        Reply Quote 0
          1 Reply Last reply
        • First post
          Last post

        Computer browsers

        • Opera for Windows
        • Opera for Mac
        • Opera for Linux
        • Opera beta version
        • Opera USB

        Mobile browsers

        • Opera for Android
        • Opera Mini
        • Opera Touch
        • Opera for basic phones

        • Add-ons
        • Opera account
        • Wallpapers
        • Opera Ads

        • Help & support
        • Opera blogs
        • Opera forums
        • Dev.Opera

        • Security
        • Privacy
        • Cookies Policy
        • EULA
        • Terms of Service

        • About Opera
        • Press info
        • Jobs
        • Investors
        • Become a partner
        • Contact us

        Follow Opera

        • Opera - Facebook
        • Opera - Twitter
        • Opera - YouTube
        • Opera - LinkedIn
        • Opera - Instagram

        © Opera Software 1995-