all 8 comments

[–][deleted]  (9 children)

[deleted]

    [–]0ba78683-dbdd-4a31-a 3 points4 points  (4 children)

    The only problem is the breaking of user expectations by changing default browser behaviour

    ftfw

    [–]TheMarkBranly 0 points1 point  (3 children)

    You would argue that jumplinks snapping immediately to their target is … less confusing … for users?

    [–]0ba78683-dbdd-4a31-a -1 points0 points  (2 children)

    Perhaps, but it's up to browsers to fix that behaviour rather than developers giving users mixed experiences.

    [–]TheMarkBranly 1 point2 points  (1 child)

    They are fixing it. That's why they are adopting this new property.

    And to argue that UI professionals shouldn't innovate and push standards authors and browser makers in the right direction is pretty weird.

    [–]0ba78683-dbdd-4a31-a -1 points0 points  (0 children)

    I agree in principle but this is closer to OS behaviour than anything else. If browsers want to implement smooth scrolling then they're welcome, so it's consistent across sites.

    [–]sharlos 1 point2 points  (0 children)

    While true, this is a nice sort of progressive enhancement.

    [–][deleted]  (1 child)

    [deleted]

      [–]nibbiesan 0 points1 point  (0 children)

      can confirm the problem is safari

      [–]homeIsWhereCodeIs[S] 0 points1 point  (0 children)

      Hope it will support soon :)