deepseek.com: breakage

[jasonbu]

Prerequisites

• This is NOT a YouTube, Facebook, Twitch, Spotify or a shortener/hosting site report. These sites MUST be reported by clicking their respective links.
• I read and understand the policy about what is a valid filter issue.
• I verified that this issue is not a duplicate. (Use this button to find out.). Comment in the old issue threads even when they are closed or even if you have a different problem.
• I did not remove any of the default filter lists, or I have verified that the issue was not caused by removing any of the default lists.
• I did not enable additional or non-default filter lists, or I have identified which specific stock list is causing the issue.
• I have disabled the Developer mode in uBO Lite's settings and the issue still persists.
• I have verified that the issue still exists after using the Optimal or Complete filtering mode.
• I have verified that the web browser's built-in content blocker/tracking protection, network wide/DNS blocking, or my VPN is not causing the issue.
• I have turned off all other extensions and the issue still persists.
• If this is about a breakage or detection, I have verified that it is caused by uBO Lite and isn't a site or browser issue.
• I have verified that the browser I am using is up to date with no pending updates.
• I did not answer truthfully to ALL the above checkboxes.

URL address of the web page

https://api-docs.deepseek.com/

Category

breakage

Description

Find when I open this page, will automaticly be closed, check all extentions, and found the rootcause is from UBO lite. Can solve by temporarily change the filter level at *.deepseek.com from full to none. then problem solved.

Browser name and version

edge 150.0.4078.50 arm64

Other extensions used

should not relative

Country

CN

Screenshot(s)

Screenshot(s)

Configuration

Details

name: uBlock Origin Lite
version: 2026.705.2152
browser: Edge 150 (mac)
filtering:
 default: complete
permission: all
rules: 25118
rulesets:
 chn-0
 easylist
 easyprivacy
 pgl
 ublock-badware
 ublock-filters
 urlhaus-full
scripting:
 ublock-filters.main
 ublock-filters.isolated
 easyprivacy.main
 easyprivacy.isolated
 ublock-badware.main
 ublock-badware.isolated
 chn-0.main
 chn-0.isolated
 css-generic-all
 css-generic-some
 prevent-popup
 toolbar-icon
 css-specific

[gothic-bum]

Please confirm the issue by testing using a new browser profile with only uBO Lite and its default settings.

[jasonbu]

Please confirm the issue by testing using a new browser profile with only uBO Lite and its default settings.

hi, thanks for reply,
double confirmed the issue still happen, in my environment. but chrome( 150.0.7871.47) looks work correct, maybe I should report it to the edge browser also?

The problems/reproduce steps is:

1. create new profile.
2. open https://api-docs.deepseek.com, should open correctly.
3. install uBlock Origin Lite.
4. open new tab, tap url https://api-docs.deepseek.com/quick_start/pricing, and enter works.
5. command + click the link here

6. We have 4 optimize levels, on none & basic, the background open works correctly, optimized & full, the background tab will be closed automatically.

[gothic-bum]

Can you test again after you disable (un-check) Enable pop-up blocking from the Settings pane in the uBO Lite dashboard.

[jasonbu]

Can you test again after you disable (un-check) Enable pop-up blocking from the Settings pane in the uBO Lite dashboard.

This Enable/Disable pop-up blocking also can solve my problem. After un-check it, full filter will no longer block my command + click

[himetuki]

I'm encountering the same page-closing issue, but it's affecting multiple DeepSeek subdomains, not just api-docs.deepseek.com. Specifically, I see the problem on:

platform.deepseek.com

download.deepseek.com

chat.deepseek.com

My environment:

Browser: Microsoft Edge Version 150.0.4078.48 (Official build) (64-bit)

uBOL Version: 2026.705.2152 (matching the report above)

I noticed my Edge version is slightly older (150.0.4078.48) than the one mentioned in the original report (150.0.4078.50). Since the reporter mentioned the issue might be Edge-specific, I wonder if this minor version difference is relevant.

What I've tried:

Disabling "Enable pop-up blocking" in uBOL dashboard does fix the automatic page closing for me, as others have confirmed.

However, I cannot apply the domain-wide workaround (- *.deepseek.com) — the line simply disappears when I try to save it in the custom rules list. This happens consistently across all the subdomains listed above.

Is the inability to save wildcard domain rules a known limitation of uBOL's custom rules engine? Or am I missing a specific syntax requirement? Any guidance would be greatly appreciated.

Thanks for looking into this!

[stephenhawk8054]

@gorhill Hmm... About #33581 (comment) , if I turn off Badware list, the issue does not occur. Not sure if it's because of this filter:

uAssets/filters/badware.txt

Line 5218 in 0d512cf

||deepseek.$all,to=deepseek.app|deepseek.top|~deepseek.com

?

||deepseek.$all,to=deepseek.app|deepseek.top|~deepseek.com

I can make it 2 filters (back then I was not sure how many TLDs there would be, hence I made it 1 filter)

||deepseek.app^$all
||deepseek.top^$all

but don't know why the issue occurs with the old filter.

[jasonbu]

After grilling my OpenCode & Kimi get these content — possible as some reference.

---

Analysis: Background tabs on deepseek.com subdomains auto-close in Edge + uBO Lite

Issue: uBlockOrigin/uAssets#33581

Summary

The background-tab closing is caused by a popup-blocking rule in filters/badware.txt:

||deepseek.$all,to=deepseek.app|deepseek.top|~deepseek.com

uBlock Origin Lite's MV3 build pipeline converts this into a popup content script that incorrectly matches *.deepseek.com because the ~deepseek.com exclusion is dropped during conversion. The actual tab close is triggered by the prevent-popup content script calling self.close(). Edge allows this call for Command+click background tabs, while Chrome does not, which explains the browser-specific symptom.

Source-level root cause

1. The original filter becomes a DNR popup rule

In src/js/static-net-filtering.js:

• $all includes the popup type (L160–L173).
• to= maps to requestDomains (L1990–L2002).
• ~deepseek.com maps to excludedRequestDomains (L2007–L2019).

So the rule is converted into a DNR popup rule roughly like:

{
  "action": { "type": "block" },
  "condition": {
    "urlFilter": "||deepseek.",
    "resourceTypes": ["popup"],
    "requestDomains": ["deepseek.app", "deepseek.top"],
    "excludedRequestDomains": ["deepseek.com"]
  }
}

2. Popup rules are converted to content-script data in make-rulesets.js

File: platform/mv3/make-rulesets.js

Function processPopupRules takes DNR popup rules and builds the preventPopupDetails object used by prevent-popup.js:

const reduceRules = (data, rule) => {
    const { condition }  = rule;
    if ( condition.domainType ) { return data; }
    if ( condition.initiatorDomains ) { return data; }
    // ...
    if ( urlFilter || regexFilter ) {
        if ( rePatternIsHostname.test(urlFilter) ) {
            realm.hostnames.push(urlFilter.slice(2, -1));
            return data;
        }
        let re;
        if ( urlFilter ) {
            re = rePatternFromUrlFilter(urlFilter);
        } else if ( regexFilter ) {
            re = regexFilter;
        }
        // regex stored in data.block.regexes
        // ...
    }
    if ( Array.isArray(condition.requestDomains) ) {
        realm.hostnames = realm.hostnames.concat(condition.requestDomains);
    }
    return data;
};

Critical gap: this function reads requestDomains and urlFilter, but never reads excludedRequestDomains. The ~deepseek.com exclusion is silently discarded.

3. ||deepseek. becomes an overly broad regex

The urlFilter ||deepseek. does not match rePatternIsHostname = /^\|\|[^*/?|^]+\^$/ (it lacks the trailing ^), so it falls into the regex branch.

Using the same rePatternFromUrlFilter logic from make-rulesets.js, ||deepseek. becomes:

^[^:]+://([^:/]+\.)?deepseek\.

This regex matches:

URL	Matches?
https://api-docs.deepseek.com/...	✅
https://platform.deepseek.com/	✅
https://download.deepseek.com/	✅
https://chat.deepseek.com/	✅
https://deepseek.com/	✅
https://deepseek.app/	✅
https://deepseek.top/	✅

So every *.deepseek.com background tab is treated as a blocked popup.

4. Verified in the published build artifact

The published uBO Lite Chromium ruleset (uBOL-home/chromium/rulesets/scripting/popup/ublock-badware.js) contains the generated data, including:

"regexes": [
  // ...
  "^[^:]+:\/\/([^:/]+\\.)?deepseek\\."
  // ...
]

This confirms the broad deepseek\. regex is shipped in the popup-blocking script.

Why it only reproduces in Edge

The mis-matching regex exists in both Chrome and Edge builds, so both browsers receive the same preventPopupDetails. The difference is in what happens inside prevent-popup.js:

if ( shouldClose ) {
    self.close();
}

• Edge: self.close() from a content script successfully closes a background tab opened via Command+click.
• Chrome: Chromium's window.close() restrictions usually prevent a content script from closing a tab that was not opened by window.open() with a non-null opener. The call is ignored, so the tab stays open.

That is why disabling "Enable pop-up blocking" or removing the Badware list fixes it on Edge: the prevent-popup script is no longer injected or has no matching block entry.

Suggested fixes

Immediate filter-list fix (safe)

Replace the single rule with explicit hostname rules:

||deepseek.app^$all
||deepseek.top^$all

||deepseek.app^ matches rePatternIsHostname, so processPopupRules places it in block.hostnames instead of block.regexes. This avoids matching deepseek.com entirely.

Long-term build-pipeline fix

processPopupRules in platform/mv3/make-rulesets.js should honor excludedRequestDomains (and ideally excludedRequestDomains/excludedInitiatorDomains in general). Otherwise, any future rule shaped like ||<entity>.$all,to=<tld>|~<excluded-domain> can trigger the same false positive.

A minimal change would be to skip or negate rules when the excluded domains overlap with the regex pattern, or to emit the exclusions into the generated script data so the runtime can check them before calling self.close().

References

• gorhill/uBlock:platform/mv3/make-rulesets.js — processPopupRules, isPopupRule, splitDnrRules
• gorhill/uBlock:src/js/static-net-filtering.js — $all type bits, FilterToDomainHit/FilterToDomainMiss
• uBlockOrigin/uBOL-home:chromium/rulesets/scripting/popup/ublock-badware.js — shipped popup script containing deepseek\\. regex