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

false positive in the floating list obscures a heading in play.google.com/books #500

Open
acolbeck opened this issue Mar 14, 2023 · 0 comments

Comments

@acolbeck
Copy link

URL(s) where the issue occurs

https://play.google.com/books

Describe the issue

Normal usage of this page has tiles representing the books already in the user's library. There is a navigation bar above the tiles for Last Read, Progress, Search, Upload etc (screenshot 1) and as the user scrolls down the page, this navigation bar does not float, it scrolls off the screen with the tile content, (screenshot 2).

There is an unwanted behaviour in the floating list which makes the tiles obscure the navigation bar. The features of the navigation bar are slightly visible but unclickable.

The entry in the floating list is google.com###js-header, #searchform, .O-j-k, .header:not(#menu.header--primary):not(.column-section):not(.viewed):not(.ng-star-inserted):not([class*="_ngcontent"]):not([role="heading"]), .js-header.chr-header, .mobile-action-bar, body > .ng-scope, #flt-nav, .gws-flights__scrollbar-padding.gws-flights__selection-bar, .gws-flights__selection-bar-shadow-mask:style(position: absolute !important;)

Screenshot(s)

screenshot 1, default behaviour
image

screenshot 2, default scrolling behaviour
image

screenshot 3, the floating filter entry causing the navigation bar to be obscured
image

Versions

  • Browser & Version: Google Chrome 110.0.5481.180
  • Adblocker (uBlock Origin, Adguard, Nano Adblocker, etc.) & Version: uBO 1.47.4

Settings

  • Web Annoyances ultralist Github link added as a Custom Filter list

Notes

In my own browser, I've neutralized the specific filter in the uBO My Filters section by inserting an @ sign between the second and third # signs that denote a DOM filter, e.g.

google.com#@##...

I do not know the intended feature or scope of the filter line, so I can't suggest whether the specific filter should be dropped or how it should be amended for everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant