[Bug] Replace with title #15998

Activity

1. noname-nikke

   added

   bug

   on Sep 15, 2026
2. huangj1e commented on Sep 15, 2026

   

   huangj1e

   on Sep 15, 2026

   More actions

   我把 v4.9.130 手动下载并安装之后所有的问题就都消失了。
3. Arteiimis commented on Sep 15, 2026

   

   Arteiimis

   on Sep 15, 2026

   More actions

   I hit the same regression and tracked down the cause — it is not site-specific, it is a network-layer bug in 4.9.131.

   44218ebf ("Use targetAddressSpace property") makes getOKResponse() declare targetAddressSpace: 'public' on every cross-origin fetch (src/utils/network.ts). When the browser's traffic goes through a proxy, Chrome cannot resolve the target address space, reports it as unknown, and rejects the request before sending it:

   Access to fetch at 'https://g.alicdn.com/idle-pc/xy-site/0.0.175/css/main.css' from origin 'chrome-extension://<id>'
   has been blocked by CORS policy: Request had a target IP address space of `public` yet the resource is in address space `unknown`.
   

   Every cross-origin stylesheet and image Dark Reader fetches in the background then fails (net::ERR_FAILED / InvalidLocalNetworkAccess), so pages keep their light-theme styles. That explains why a large number of sites broke at once, and why the Safari version (and Firefox) is unaffected — they ignore the option.

   Measured on the two sites you listed (fresh profile, default settings, proxy enabled):

   Site	4.9.131	with the fix	failed cross-origin fetches
   https://www.goofish.com/	light background rgb(245,247,249)	rgb(29,31,32)	6 → 0
   https://www.52pojie.cn/	14 Dark Reader stylesheets	18 Dark Reader stylesheets	4 → 0

   Fix: #16002. Workarounds until it ships: stay on 4.9.130 (which you already did), or start the browser without the proxy — the same 4.9.131 build renders correctly with --no-proxy-server.

   Could you confirm whether you are using a proxy/VPN client (for example Clash, v2ray, or anything listening on 127.0.0.1)? That is the trigger condition, and confirming it would help the maintainer reproduce this.
4. noname-nikke commented on Sep 15, 2026

   

   noname-nikke

   on Sep 15, 2026

   Author

   More actions

   I hit the same regression and tracked down the cause — it is not site-specific, it is a network-layer bug in 4.9.131.

   44218ebf ("Use targetAddressSpace property") makes getOKResponse() declare targetAddressSpace: 'public' on every cross-origin fetch (src/utils/network.ts). When the browser's traffic goes through a proxy, Chrome cannot resolve the target address space, reports it as unknown, and rejects the request before sending it:

   Access to fetch at 'https://g.alicdn.com/idle-pc/xy-site/0.0.175/css/main.css' from origin 'chrome-extension://<id>'
   has been blocked by CORS policy: Request had a target IP address space of `public` yet the resource is in address space `unknown`.
   

   Every cross-origin stylesheet and image Dark Reader fetches in the background then fails (net::ERR_FAILED / InvalidLocalNetworkAccess), so pages keep their light-theme styles. That explains why a large number of sites broke at once, and why the Safari version (and Firefox) is unaffected — they ignore the option.

   Measured on the two sites you listed (fresh profile, default settings, proxy enabled):

   Site 4.9.131 with the fix failed cross-origin fetches
   https://www.goofish.com/ light background rgb(245,247,249) rgb(29,31,32) 6 → 0
   https://www.52pojie.cn/ 14 Dark Reader stylesheets 18 Dark Reader stylesheets 4 → 0
   Fix: #16002. Workarounds until it ships: stay on 4.9.130 (which you already did), or start the browser without the proxy — the same 4.9.131 build renders correctly with --no-proxy-server.

   Could you confirm whether you are using a proxy/VPN client (for example Clash, v2ray, or anything listening on 127.0.0.1)? That is the trigger condition, and confirming it would help the maintainer reproduce this.

   我确实使用了代理，在使用4.9.130是完全没有遇到这种问题，只有使用4.9.131时才遇到现在的问题
5. alexanderby commented on Sep 15, 2026

   

   alexanderby

   on Sep 15, 2026

   Member

   More actions

   We've temporarily disabled the new fetch API to prevent the issues for proxy server users. The fix is currently being reviewed. In the meantime please use Firefox browser.