You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test case as reported in original bug: https://boards.4chan.org/g/. Many css resources are being reported in the behind-the-scene context (the unified logger made the issue obvious, whereas it would go unnoticed before unless specifically observing behind-the-scene requests).
uBlock suffers the same issue. This was fixed in uMatrix by no longer relying on shouldLoad, since uMatrix does not consider embedded frames as specific context.
The fix for uBlock will have to be different.
The problem with requests being wrongly categorized as behind-the-scene is that some requests which may have been blocked in the proper context won't be blocked if evaluated in the behind-the-scene context.
The text was updated successfully, but these errors were encountered:
gorhill
changed the title
Many network requests wrongly cateegorized as behind-the-scene
Many network requests wrongly categorized as behind-the-scene
May 17, 2015
This was first reported for uMatrix: gorhill/uMatrix#165.
Test case as reported in original bug: https://boards.4chan.org/g/. Many
css
resources are being reported in the behind-the-scene context (the unified logger made the issue obvious, whereas it would go unnoticed before unless specifically observing behind-the-scene requests).uBlock suffers the same issue. This was fixed in uMatrix by no longer relying on
shouldLoad
, since uMatrix does not consider embedded frames as specific context.The fix for uBlock will have to be different.
The problem with requests being wrongly categorized as behind-the-scene is that some requests which may have been blocked in the proper context won't be blocked if evaluated in the behind-the-scene context.
The text was updated successfully, but these errors were encountered: