Custom root for sites that break scrolling? notion.site, etc #4517
Comments
|
Allowing a custom root per site seems like a reasonable idea. I'm not sure, but this might be a bug in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rationale
I'm posting this because I had some success in 15 minutes of learning how to fix scrolling for notion sites. Practically speaking, it's currently not even a workaround. I want to raise my finding to the attention of someone who could quickly, easily confirm this diagnosis and proposed solution.
Describe the bug
Notion and some other sites that break vimium interaction seem to perform scrolling in a custom viewport of the main document. I would like to manually set the activated element interactively, and eventually, specify a custom default scrolling element for
*.notion.sitesites, the user sites that break browser (Space/Shift-Space) and vimium (j/k+d/u,...) scrolling by default.To Reproduce
Currently, when I click on the page, the browser, per notion's defaults, sets
document.activeElement = <body class="notion-body vsc-initialized">...If I instead set the active element to the root tag of their client reader hierarchy, browser scrolling works as expected, though vimium scrolling stays broken.
console:
document.activeElement = $('main'), then return focus to the page without clicking,C-lselects URL bar,Console, sayElements, tab open.Esc, toggling closedConsole.Ctrl-L, focusing the URL bar.Esctwice, first deselecting the URL bar, and after the second, input is handled by the page.Space/Shift-Space, expected to workj/kord/u, still brokenBrowser and Vimium version
1.67.123 Chromium: 126.0.6478.126 (Official Build) (64-bit)/ Linux2.1.2The text was updated successfully, but these errors were encountered: