<story><title>CSS Layout cookbook</title><url>https://developer.mozilla.org/en-US/docs/Web/CSS/Layout_cookbook</url></story><parent_chain><item><author>maddyboo</author><text>Wow, when did MDN start scrolljacking?&lt;p&gt;I use a browser extension [1] which provides vim-like bindings for Chrome, and sites that scrolljack severely mess up the scroll up&amp;#x2F;down functionality.&lt;p&gt;It&amp;#x27;s hard to tell there&amp;#x27;s scrolljacking just by using your mousewheel, but if you try running `window.scrollBy(0, 500);` in your developer console, you&amp;#x27;ll see the easing being applied. Try the same code on a site without scrolljacking (like the HN front page) and you&amp;#x27;ll see it jumps directly to the destination.&lt;p&gt;You&amp;#x27;d think one of the largest advocates for web standards and accessibility would know better!&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;brookhong&amp;#x2F;Surfingkeys&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;brookhong&amp;#x2F;Surfingkeys&lt;/a&gt;</text></item></parent_chain><comment><author>twhb</author><text>MDN isn&amp;#x27;t scrolljacking, they just set “scroll-behavior: smooth;” [1]. It&amp;#x27;s a native CSS property and integrates with native scrolling, which is why mouse wheels, touchpads, touchscreens, etc are working fine. I would open a bug report with the extension, it needs to specify the scrolling mode it wants, rather than defaulting to whatever the website chose.&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;developer.mozilla.org&amp;#x2F;en-US&amp;#x2F;docs&amp;#x2F;Web&amp;#x2F;CSS&amp;#x2F;scroll-behavior&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;developer.mozilla.org&amp;#x2F;en-US&amp;#x2F;docs&amp;#x2F;Web&amp;#x2F;CSS&amp;#x2F;scroll-beha...&lt;/a&gt;</text></comment>
<story><title>CSS Layout cookbook</title><url>https://developer.mozilla.org/en-US/docs/Web/CSS/Layout_cookbook</url></story><parent_chain><item><author>maddyboo</author><text>Wow, when did MDN start scrolljacking?&lt;p&gt;I use a browser extension [1] which provides vim-like bindings for Chrome, and sites that scrolljack severely mess up the scroll up&amp;#x2F;down functionality.&lt;p&gt;It&amp;#x27;s hard to tell there&amp;#x27;s scrolljacking just by using your mousewheel, but if you try running `window.scrollBy(0, 500);` in your developer console, you&amp;#x27;ll see the easing being applied. Try the same code on a site without scrolljacking (like the HN front page) and you&amp;#x27;ll see it jumps directly to the destination.&lt;p&gt;You&amp;#x27;d think one of the largest advocates for web standards and accessibility would know better!&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;brookhong&amp;#x2F;Surfingkeys&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;brookhong&amp;#x2F;Surfingkeys&lt;/a&gt;</text></item></parent_chain><comment><author>ziikutv</author><text>Pardon my ignorance on this. I am not sure if the easing of scroll motion is scrolljacking.&lt;p&gt;&amp;gt; Scrolljacking basically means we replace native scrolling (what you’re used to) with targeted scrolling: when the user initiates a scroll, either with their mouse or keyboard, scrolljacking takes them to an exact vertical point on the screen (for example, the top of the next content container)&lt;p&gt;They aren&amp;#x27;t targeting your scrolling to specific areas on the page, just adding an ease in&amp;#x2F;out. It happens natively on iOS actually.&lt;p&gt;Edit: I do agree that it might hinder accessibility, just dont think the term applies as it does in other cases here.</text></comment>