5 ms·
NYT actually takes the page-down/lines of text problem into account. Odd that others haven't copied. Now that both position: sticky and Scroll Snap Points from
by Andrex 9y ago
NYT actually takes the page-down/lines of text problem into account. Odd that others haven't copied.
Now that both position: sticky and Scroll Snap Points from CSS are landing in browsers, those complaints will hopefully be resolved. Scrolling is much better off left in the hands of CSS than JS.
- steve-howard 9y agoNYT is pretty obnoxious in other ways, though, especially with a touchscreen. If you click and drag to highlight something, it navigates to a different article. If you double-click to select a word, it changes the text size. If you accidentally hit the left or right arrow key while trying to scroll up or down, it again tries to load the next article.
- dredmorbius 9y agoAnd it's not possible to select text at all on Mobile. I've taken to using alternative links (archive.is, archive.org, outline.com) for sharing the articles simply because it's too much of a PITA to manage the NYTimes.com page itself.
- awinter-py 9y agonytimes.com also hijacks the left/right arrow to advance to the next article, and used to do a thing where if you multi-click to select a paragraph it would jiggle the font size.
- abrowne 9y agoFirefox takes full-width fixed headers (and footers?) into account when you scroll with page up/down or space bar.