-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
No hints on cookie banner #4068
Comments
I tried the SurfingKeys extension and it seems to work with it. So it doesn't seem to be a technical but an implementation issue. Would love to see it in Vimium, too! |
I've noticed it with a lot of cookie banners and newsletter popups that can't be closed via hints. Might try if I can find out why this happens (and possibly a fix), if time allows 😬 |
I had a quick look at the cookie banner gallery linked in #4068 (comment) and this seems to be a z-index issue. 🤔
|
@ravindUwU That's a great finding! I made a fork and changed the z-index to the maximum possible value of 2147483647. https://github.com/JulianDeal/vimium/tree/new-z-max So far it works on the websites I tested and had no issues. @philc What is the reason for several layers of link hints? One z-index seems to work just fine, even with overlapping. Edit: |
@JulianDeal I can't seem to find a cookie banner on the page you linked, but there is a "try in sandbox" button that redirects to https://try.devowl.io, which shows a cookie banner. This one is shown within a |
Regarding the layers: I found the reason for stacking the layers: #757. Hitting To fix this issue I am making changes to the code right now, so that if the max z-index of the link hints parent elements is greater than 240000001, it will increase Vimium's z-index above this max value. So in fringe cases the rotation won't work anymore, but that's better than not seeing the link hints in the first place. Will continue this weekend. @ravindUwU Maybe I got the cookie banner because I am located in the EU. Or try deleting your cookies. |
This PR should fix the issue with obscured elements. The page mentioned by @lornajane shows it perfectly. After accepting the cookies, there still is a button with z-index of 2147483646 in the left bottom corner. The new logic places its link hint on top while the overlapping link hints in the top right corner are still able to rotate. We could also change the code to only place the link hint a layer above. This would also hide most link hints of non visible links. But I wanted to change the original functionality as little as possible. |
Sidenote: reading about how stacking occurs without |
@ravindUwU: This is a good solution, too. I will mention it in as an alternative implementation in the PR. |
Guys, this is great investigative work. Thanks @JulianDeal for the PR. Looking at the PR and @ravindUwU's proposed change, it seems to me simpler overall if we could manage rotation by modifying the child's index within its parent. Then we wouldn't need to manage z-indices, or document how fringe cases are expected to work. So in summary:
As a side note, we should confirm that this modification doesn't unintentionally modify the current stacking UX (i.e. if today link A is shown on top of link B in a stack on some example page, this PR shouldn't change that). @JulianDeal can you modify your PR to take this approach? |
This has been fixed by #4315. |
Describe the bug
Cookie banner containing one link and two buttons pops up, but vimium doesn't hint those controls so I can't dismiss the banner and use the site. I assumed this was just people using span tags or some nonsense, but it's a site I control and it has a proper hyperlink and button tags. Is there a way I can make this available to me? I am not sure if the popup is loading after vimium, or something else?
To Reproduce
Steps to reproduce the behavior:
Include a screenshot if applicable.
Browser and Vimium version
Firefox 94.0
Vimium 1.67.1
This definitely could be more of a question than a bug report, either way I'm hoping there's an easy fix!
The text was updated successfully, but these errors were encountered: