I tried to think up the most neutral sounding name possible <| sep |> ella vos white noise <| sep |> Ok , let ' s say you ' re doing some sort of parallax animation with a fixed background attachment . Testing reveals that on an Android tablet on Chrome , the background stutters and fails to keep up with the scroll . It ' s not down to performance , because every other device works fine . You figure the device is trying to optimize something and recalculating stuff less often . You could spend the next 6 hours on Google trying to figure out what is causing this behaviour , but the deadline is in a few days and you still have a bunch of other stuff to do . What feature detection will you use to solve this problem ? Let me answer that for you . You use device detection , and disable the animation on Android Chrome . Next week rolls around and you get a bug report that the sticky element you implemented with some jQuery library is broken on mobile Safari the element disappears entirely while the user is scrolling . Admittedly , it ' s a pretty rare thing because the user needs to have a screen size of above some breakpoint on a mobile Safari device , so probably landscape mode , but regardless it ' s ugly and the client isn ' t happy . Now you could dig into the jQuery plugin ' s source code , try to figure out what ' s going on assuming you even can , because probably that device is again doing some weird optimization . BUT you ' ve got 2 other projects and this looks like a bug that you ' ll debug for a long time , so it ' s not worth it . Besides , the client already told you that you can just go ahead and disable that functionality on ipads . So what do you do ? Well , I know what I ' ll do . I ' ll hack together some userAgent regex check and disable the sticky element behaviour for mobile Safari .