Bug 125550 - Horizontal rubber-banding without a horizontal scrollbar is distracting
Summary: Horizontal rubber-banding without a horizontal scrollbar is distracting
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Beth Dakin
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-12-10 16:22 PST by Beth Dakin
Modified: 2014-02-26 09:56 PST (History)
6 users (show)

See Also:


Attachments
Patch (1.29 KB, patch)
2013-12-10 16:26 PST, Beth Dakin
simon.fraser: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Beth Dakin 2013-12-10 16:22:45 PST
Horizontal rubber-banding without a horizontal scrollbar is distracting. We should only allow horizontal rubber-banding when there is content to scroll to.

<rdar://problem/14137306>
Comment 1 Beth Dakin 2013-12-10 16:26:13 PST
Created attachment 218919 [details]
Patch
Comment 2 Beth Dakin 2013-12-10 16:51:36 PST
http://trac.webkit.org/changeset/160397
Comment 3 Andreas Kling 2013-12-11 11:42:51 PST
This is my favorite change ever.
Comment 4 Mehmet 2014-02-25 12:30:15 PST
@Beth Dakin: Is this reverted again in latest Webkit? I do not see the fix any longer in Webkit r164641 :-(
Comment 5 Beth Dakin 2014-02-25 12:40:26 PST
(In reply to comment #4)
> @Beth Dakin: Is this reverted again in latest Webkit? I do not see the fix any longer in Webkit r164641 :-(

It is, sorry about that. I reverted the change as a part of http://trac.webkit.org/changeset/163180

We are still having an ongoing discussion about the best behavior here, so it's not all said and done quite yet. Actually it would probably be best to formalize that discussion in a bug report where multiple people can weigh in (so far it has mostly been in-person discussions).
Comment 6 Mehmet 2014-02-25 13:10:38 PST
(In reply to comment #5)
> (In reply to comment #4)
> > @Beth Dakin: Is this reverted again in latest Webkit? I do not see the fix any longer in Webkit r164641 :-(
> 
> It is, sorry about that. I reverted the change as a part of http://trac.webkit.org/changeset/163180
> 
> We are still having an ongoing discussion about the best behavior here, so it's not all said and done quite yet. Actually it would probably be best to formalize that discussion in a bug report where multiple people can weigh in (so far it has mostly been in-person discussions).

Thanks for the information. Should I open a bug report for the discussion?
Comment 7 Beth Dakin 2014-02-25 15:55:43 PST
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > @Beth Dakin: Is this reverted again in latest Webkit? I do not see the fix any longer in Webkit r164641 :-(
> > 
> > It is, sorry about that. I reverted the change as a part of http://trac.webkit.org/changeset/163180
> > 
> > We are still having an ongoing discussion about the best behavior here, so it's not all said and done quite yet. Actually it would probably be best to formalize that discussion in a bug report where multiple people can weigh in (so far it has mostly been in-person discussions).
> 
> Thanks for the information. Should I open a bug report for the discussion?

That would be great! Thanks!
Comment 8 Mehmet 2014-02-26 09:56:24 PST
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > (In reply to comment #4)
> > > > @Beth Dakin: Is this reverted again in latest Webkit? I do not see the fix any longer in Webkit r164641 :-(
> > > 
> > > It is, sorry about that. I reverted the change as a part of http://trac.webkit.org/changeset/163180
> > > 
> > > We are still having an ongoing discussion about the best behavior here, so it's not all said and done quite yet. Actually it would probably be best to formalize that discussion in a bug report where multiple people can weigh in (so far it has mostly been in-person discussions).
> > 
> > Thanks for the information. Should I open a bug report for the discussion?
> 
> That would be great! Thanks!

Bug 129374 :-)