Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uMatrix iframes not scrollable #23

Open
BlueMax opened this issue Sep 20, 2020 · 1 comment
Open

uMatrix iframes not scrollable #23

BlueMax opened this issue Sep 20, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@BlueMax
Copy link

BlueMax commented Sep 20, 2020

Hallo,
iframes of uMatrix are not detected as scrollable area.

Steps To Reproduce

  1. Go to uMatrix settings (click addon symbol -> top black bar).
  2. Make sure 'hide blocked elements' is not enabled.
  3. Visit https://fastaddons.com
  4. Scroll down to the (blocked) youtube iframe.
  5. The gray checkered area is not scrollable (see pic below) and you have to move the mouse cursor outside the iframe first to be able to scroll again.

Device info:

  • Arch Linux 5.8.10
  • Firefox 80.0.1
  • ScrollAnywhere 8.4

umatrix

@BlueMax BlueMax added the bug Something isn't working label Sep 20, 2020
@fastaddons
Copy link
Collaborator

So, this will be hard. It seems that the uMatrix will replace (or clear?) the iframe and somehow my extension won't be running inside. That's unexpected behavior since my extension should be executed in all frames.
The same problem should however affect also other iframes with blocked javascript even without the uMatrix. Such iframes are not very common on the web, but still possible.

The only solution I can think of is identify all frames where my script is not running and "somehow" block them.

However there is a good chance it will not be possible. All mouse events inside iframe are captured by iframe and parent window doesn't see them. All I could do is block all interactions with the iframe but then user will not be able to interact with iframe at all, which is not good because in this case the link inside wouldn't be clickable anymore...

I will investigate this further before releasing new version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant