750839 - nytimes.com image slider doesn't slide (and prevents normal panning)

Status: RESOLVED INVALID

(Web Compatibility :: Site Reports, defect)

Description

[Kartikaya Gupta (email:[e-mail])]

1. Load nytimes.com
2. Scroll down to the image slider halfway down the page, this has 6 images in a row across the page just under the heading "INSIDE NYTIMES.COM"
3. Try to fling the images left or right

expected results: the images slide in the direction of fling (you can see this behaviour by using Chrome for android)

actual results: nothing happens

There are actually a bunch of touch listeners that get triggered and run on this page. They do a preventDefault on the touch events delivered, which is why it's actually not possible to pan the nytimes.com page if you start with a touch down on that row of images. However, the touch listeners are supposed to allow sliding the images leftwards/rightwards, and that doesn't work on Fennec. It works fine in Chrome for android.

The script that appears to implement this behaviour is at http://js.nyt.com/js2/build/homepage/bottom.js but it's minified/obfuscated so getting anything out of it is going to be a pain. Therefore I don't know if this is a bug in Fennec or a bug on the page.

Comment 1

[Wesley Johnston (:wesj)]

I see them setting:

webkitTransitionProperty
webkitTransitionTimingFunction
webkitTransitionDuration
webkitTransform
webkitTransitionDelay

and listening for:

webkitTransitionEnd

along with a super awesome call to:

if(Prototype.Browser.WebKit) { // scroll }

and no fallbacks for anyone else, so I'm fairly confident this is an evang issue.

Comment 2

[Kartikaya Gupta (email:[e-mail])]

That's what I suspected as well, but wasn't sure. Thanks for looking into it; moving to evangelism. Also updating this title to trap dupes. Note that trying to pan nytimes.com by putting your finger down on the image row doesn't work in Chrome either.

Comment 3

[Mike Taylor [:miketaylr]]

I don't see the image slider component on their home page anymore (in Chrome or F4A), so closing as Invalid, likely due to a redesign in their mobile site over the past year. Please reopen if I'm mistaken!