4 ms·

Yeah, gross. jk gg G all stopped working. Checking archive.org, it looks like the scrolljacking was just added on October 12.

maddyboo 8y ago
Glad I'm not the only one. Where in the MDN source is the scrolljacking code?
- regecks 8y ago
  It seems to be caused entirely by `scroll-behavior: smooth;` on the `html` element. Try add that style to this (HN) comments page. Same problem. Seems like the vim addons aren't dealing with browsers' implementations of that style. Whoops. For the addon I use (Vimium-FF), it appears to have been already reported and fixed: https://github.com/philc/vimium/pull/3111 https://github.com/philc/vimium/pull/3111 but not yet published to AMO.
  - nathancahill 8y ago
    Props to you for actually digging in to the issue instead of the jump-to-conclusions "gross" comments.
  - kbenson 8y ago
    The irony of this is fairly delicious.
  - maddyboo 8y ago
    Thanks for looking into this and finding that PR! I opened an issue with SurfingKeys: https://github.com/brookhong/Surfingkeys/issues/837 https://github.com/brookhong/Surfingkeys/issues/837
rudedogg 8y ago
This is really unfortunate. I use the MDN docs frequently, and I can no longer scroll using the typical vim motion commands via https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ I posted a thread on the MDN discord: https://discourse.mozilla.org/t/scrolling-behavior-on-mdn/32564 https://discourse.mozilla.org/t/scrolling-behavior-on-mdn/32... Edit: Another person pointed out that it's caused by the scroll-behavior: smooth; style. I'm guessing they won't change the MDN website and the extensions will need to ignore/disable the style through CSSOM. The property docs say "User agents are allowed to ignore this property.", so I guess that makes sense.
- bhrgunatha 8y ago
  Dev tools to fix sites during one off visits and Stylus for regular visits. Stylus is an absolutely essential add-on for me in recent years. It's useless trying to convince the world to have sane, readable text size and contrast on desktop. Firefox reader view doesn't work well with interactive pages.

maddyboo 8y ago

Glad I'm not the only one. Where in the MDN source is the scrolljacking code?

regecks 8y ago
It seems to be caused entirely by `scroll-behavior: smooth;` on the `html` element. Try add that style to this (HN) comments page. Same problem. Seems like the vim addons aren't dealing with browsers' implementations of that style. Whoops. For the addon I use (Vimium-FF), it appears to have been already reported and fixed: https://github.com/philc/vimium/pull/3111 https://github.com/philc/vimium/pull/3111 but not yet published to AMO.
- nathancahill 8y ago
  Props to you for actually digging in to the issue instead of the jump-to-conclusions "gross" comments.
- kbenson 8y ago
  The irony of this is fairly delicious.
- maddyboo 8y ago
  Thanks for looking into this and finding that PR! I opened an issue with SurfingKeys: https://github.com/brookhong/Surfingkeys/issues/837 https://github.com/brookhong/Surfingkeys/issues/837

rudedogg 8y ago

This is really unfortunate. I use the MDN docs frequently, and I can no longer scroll using the typical vim motion commands via https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/ I posted a thread on the MDN discord: https://discourse.mozilla.org/t/scrolling-behavior-on-mdn/32564 https://discourse.mozilla.org/t/scrolling-behavior-on-mdn/32... Edit: Another person pointed out that it's caused by the scroll-behavior: smooth; style. I'm guessing they won't change the MDN website and the extensions will need to ignore/disable the style through CSSOM. The property docs say "User agents are allowed to ignore this property.", so I guess that makes sense.

bhrgunatha 8y ago
Dev tools to fix sites during one off visits and Stylus for regular visits. Stylus is an absolutely essential add-on for me in recent years. It's useless trying to convince the world to have sane, readable text size and contrast on desktop. Firefox reader view doesn't work well with interactive pages.