Are issues regarding uBlock Origin's interaction with other extensions generally accepted?

[partingscientist]

If yes, would there be any prerequisite(s) specific to such cases that need to be met before reporting? I'd assume one of them (assuming they're allowed) would be such issues must be confirmed caused by (changes to) uBlock Origin. I thought I'd ask first before wasting my time exploring further.

Thank you.

[gorhill]

It depends? What's the actual issue?

[Gusted]

Hmm weird, which version was still "buggy"? Not able to reproduce this, anyhow color-scheme has caused various bugs for Dark Reader as well, it's really a black box and documentation is really vague on what the implementation should look like in browsers. I feel you @gorhill regarding this.

[gorhill]

The thing which is difficult to understand is that color-theme works fine with element picker.

[gorhill]

Ok I think I understand the issue -- which is still present. Something I overlooked is that the DOM inspector uses an anonymous (about:blank) frame for the layer, while it's an extension (moz-extension://...) frame with the element picker. Dark Reader has access to the anonymous frame, which it modifies, while it does not have access to the extension frame. Ideally the DOM inspector iframe would be an extension one, but this is not a trivial change. I think this can be fixed by simply ensuring uBO's style inside the frame wins over Dark Reader one's.

[Gusted]

Dark Reader can be quite aggressive about getting priority over other styles. Dark Reader should not add the color-scheme: dark property when it's in a about:blank frame, WDYT? It's easier to patch this on Dark Reader's side as it's ultimately causing this behavior.

[gorhill]

It's fixed in uBO already: gorhill/uBlock@105c7f5 -- it's added as an element style, which has the highest priority.