Launchpad has imported 20 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=39417.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://documentation.ubuntu.com/launchpad/user/reference/bugs/multi-project-bugs/about-multi-project-bugs/#bugs-in-external-trackers.

------------------------------------------------------------------------
On 2010-05-20T10:28:17+00:00 morrita wrote:

Created attachment 56580
a repro

Derived from http://crbug.com/44435 but the problem is applicable all
browsers that support fullscreen view.

How to reproduce:
- switch to fullscreen view
- open attached html
- select text with mouse, dragging it to right side of the view

Expected result:
- The view scrolls to right
What happens instead:
- The view doesn't scroll

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/1

------------------------------------------------------------------------
On 2010-05-21T01:57:46+00:00 morrita wrote:

Created attachment 56659
patch v0

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/3

------------------------------------------------------------------------
On 2010-05-21T09:18:59+00:00 tkent wrote:

Comment on attachment 56659
patch v0

LayoutTests/fast/events/autoscroll-border-margin-vertical-body.html:67
 +  This is vertically large box...
I don't like tests and results have many empty lines.
How about using CSS height like <pre id="line" style="height:1000px;"> ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/5

------------------------------------------------------------------------
On 2010-05-25T03:02:51+00:00 morrita wrote:

Created attachment 56964
patch v1

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/6

------------------------------------------------------------------------
On 2010-05-25T03:04:53+00:00 morrita wrote:

Hi Kent-san, thank you for the feedback and sorry for a slow reply.
I updated the patch.

> LayoutTests/fast/events/autoscroll-border-margin-vertical-body.html:67
>  +  This is vertically large box...
> I don't like tests and results have many empty lines.
> How about using CSS height like <pre id="line" style="height:1000px;"> ?
Agreed. fixed to use style instead of blank lines.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/7

------------------------------------------------------------------------
On 2010-05-25T05:31:09+00:00 morrita wrote:

Created attachment 56973
rebased to make bots work

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/8

------------------------------------------------------------------------
On 2010-05-25T05:34:06+00:00 webkit.review.bot wrote:

Attachment 56973 did not pass style-queue:

Failed to run "['WebKitTools/Scripts/check-webkit-style', '--no-squash']" 
exit_code: 1
WebCore/platform/graphics/IntRect.h:156:  More than one command on the same 
line  [whitespace/newline] [4]
Total errors found: 1 in 44 files


If any of these errors are false positives, please file a bug against 
check-webkit-style.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/10

------------------------------------------------------------------------
On 2010-05-25T06:23:09+00:00 webkit.review.bot wrote:

Attachment 56973 did not build on chromium:
Build output: http://webkit-commit-queue.appspot.com/results/2268641

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/11

------------------------------------------------------------------------
On 2010-05-25T06:26:21+00:00 morrita wrote:

Created attachment 56976
fixed style violation, chromium build error

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/12

------------------------------------------------------------------------
On 2010-05-28T06:38:41+00:00 morrita wrote:

Created attachment 57295
patch v0

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/13

------------------------------------------------------------------------
On 2010-05-28T06:41:20+00:00 webkit.review.bot wrote:

Attachment 57295 did not pass style-queue:

Failed to run "['WebKitTools/Scripts/check-webkit-style', '--no-squash']" 
exit_code: 1
WebCore/platform/graphics/IntRect.cpp:61:  Tab found; better to use spaces  
[whitespace/tab] [1]
WebCore/platform/graphics/IntRect.cpp:63:  Tab found; better to use spaces  
[whitespace/tab] [1]
WebCore/platform/graphics/IntRect.cpp:65:  Tab found; better to use spaces  
[whitespace/tab] [1]
WebCore/platform/graphics/IntRect.cpp:67:  Tab found; better to use spaces  
[whitespace/tab] [1]
WebKit/chromium/src/WebViewImpl.cpp:1670:  Tab found; better to use spaces  
[whitespace/tab] [1]
WebKit/chromium/src/WebViewImpl.cpp:1681:  Missing spaces around /  
[whitespace/operators] [3]
WebKit/chromium/src/WebViewImpl.cpp:1690:  Tab found; better to use spaces  
[whitespace/tab] [1]
Total errors found: 7 in 7 files


If any of these errors are false positives, please file a bug against 
check-webkit-style.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/14

------------------------------------------------------------------------
On 2010-05-28T06:41:59+00:00 morrita wrote:

Comment on attachment 57295
patch v0

Cancelling due to wrong bug id. I'sorry for disturbing you...

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/15

------------------------------------------------------------------------
On 2010-05-28T06:43:00+00:00 morrita wrote:

Comment on attachment 56976
fixed style violation, chromium build error

This patch is for review. (I had cancelled this accidentally.)

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/16

------------------------------------------------------------------------
On 2010-06-04T02:40:57+00:00 pkasting wrote:

Comment on attachment 56976
fixed style violation, chromium build error

> --- a/WebCore/platform/graphics/IntRect.h
> +++ b/WebCore/platform/graphics/IntRect.h
> @@ -136,6 +136,29 @@ public:
>          m_size.setHeight(m_size.height() + dy + dy);
>      }
>      void inflate(int d) { inflateX(d); inflateY(d); }
> +
> +    void deflateX(int dx)
> +    {
> +        m_location.setX(m_location.x() + dx);
> +        if (dx + dx < m_size.width())
> +            m_size.setWidth(m_size.width() - (dx + dx));
> +        else
> +            m_size.setWidth(0);
> +    }
> +    void deflateY(int dy)
> +    {
> +        m_location.setY(m_location.y() + dy);
> +        if (dy + dy < m_size.height())
> +            m_size.setHeight(m_size.height() - (dy + dy));
> +        else
> +            m_size.setHeight(0);
> +    }
> +    void deflate(int d)
> +    {
> +        deflateX(d);
> +        deflateY(d);
> +    }

It seems like instead of adding these, it might be better to use the
existing inflate() functions, and have IntSize::set{Width,Height}()
clamp the minimum size to zero.

However, you'd have to make sure we don't actually rely on negative
sizes anywhere.  (It seems like a bug if we do.)  Might want to run this
idea past Darin Adler.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/17

------------------------------------------------------------------------
On 2010-06-04T03:35:31+00:00 tony wrote:

Comment on attachment 56976
fixed style violation, chromium build error

> +++ b/LayoutTests/fast/events/autoscroll-border-margin-horizontal-body.html
> +                    var endY = startY;
> +                    eventSender.mouseMoveTo(endX, endY);
> +                }
> +
> +                setTimeout(afterDragging, 1000);

Is it possible to avoid this timeout (maybe by using
eventSender.leapFoward)?  Is there an event we can get instead?  Or
maybe we can poll every 50ms to check for changes?

Also, is it possible to merge some or all of these tests into the same
.html file?

> diff --git a/WebCore/page/Settings.h b/WebCore/page/Settings.h
> index 
> dc3b50fb7ad8e423733754deb6ecf03974ef29e6..cc9f35780219435e9d3bc2a2e8252c84b8f35097
>  100644
> --- a/WebCore/page/Settings.h
> +++ b/WebCore/page/Settings.h
> @@ -311,6 +311,9 @@ namespace WebCore {
>          void setHTML5ParserEnabled(bool flag) { m_html5ParserEnabled = flag; 
> }
>          bool html5ParserEnabled() const { return m_html5ParserEnabled; }
>  
> +        void setAutoscrollBorderMargin(unsigned value) { 
> m_autoscrollBorderMargin = value; }
> +        unsigned autoscrollBorderMargin() const { return 
> m_autoscrollBorderMargin; }
> +

I don't know if this should be a setting or not.  For example, the
minimum drag distances (hysteresis) are hard coded in EventHandler.cpp.
I bet this is a platform specific value.

> --- a/WebKitTools/DumpRenderTree/qt/LayoutTestControllerQt.h
> +++ b/WebKitTools/DumpRenderTree/qt/LayoutTestControllerQt.h
> @@ -187,6 +187,8 @@ public slots:
>      */
>      void setScrollbarPolicy(const QString& orientation, const QString& 
> policy);
>  
> +    void setautoscrollbordermargin(unsigned);
> +

This being in lowercase is probably causing the QT bot to be red.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/18

------------------------------------------------------------------------
On 2010-06-10T02:08:24+00:00 morrita wrote:

Created attachment 58322
patch v6

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/19

------------------------------------------------------------------------
On 2010-06-10T02:16:48+00:00 morrita wrote:

Kasting, Tony, thank you for your feedback, and I'm sorry for my slow
response.

> > +    void deflate(int d)
> > +    {
> > +        deflateX(d);
> > +        deflateY(d);
> > +    }
> 
> It seems like instead of adding these, it might be better to use the existing 
> inflate() functions, and 
have IntSize::set{Width,Height}() clamp the minimum size to zero.
Fixed to implement deflate(x) with inflate(-x).

> However, you'd have to make sure we don't actually rely on negative sizes 
> anywhere.  (It seems like a bug if we do.)  Might want to run this idea past 
> Darin Adler.
Agreed. In this case, "inflate" might be just no longer a good name.

(In reply to comment #14)
> > +                setTimeout(afterDragging, 1000);
> 
> Is it possible to avoid this timeout (maybe by using eventSender.leapFoward)? 
>  Is there an event we can get instead?  Or maybe we can poll every 50ms to 
> check for changes?
Done.

> 
> Also, is it possible to merge some or all of these tests into the same .html 
> file?
Done.

> > +        void setAutoscrollBorderMargin(unsigned value) { 
> > m_autoscrollBorderMargin = value; }
> > +        unsigned autoscrollBorderMargin() const { return 
> > m_autoscrollBorderMargin; }
> > +
> 
> I don't know if this should be a setting or not.  For example, the minimum 
> drag distances (hysteresis) are hard coded in EventHandler.cpp.  I bet this 
> is a platform specific value.
Agreed. I moved it to ScreenView::m_autoscrollBorderMargin and gave it to
platform specific value. (It's currently only for chromium.) I left its setter 
for testing purpose.

> >  
> > +    void setautoscrollbordermargin(unsigned);
> > +
> 
> This being in lowercase is probably causing the QT bot to be red.
Oops. fixed.

According to the feedback, the behavior goes stateless, instead of 
fullscreen-specific.
Although no other browser cares this issue, I think it's worth to care it 
because
Fullscreen-like usage will grow on more lightweight devices such as netbooks.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/20

------------------------------------------------------------------------
On 2010-06-10T04:07:29+00:00 tony wrote:

I tested this on IE and Firefox.

Firefox 3.6 only autoscrolls if you are over a scrollbar.  This means
it's not possible to autoscroll a selection left when maximized or
fullscreen because there's no autoscroll area.  Another way to describe
this is that hovering over a scrollbar is treated as being outside the
content area, therefore it triggers autoscrolling.

IE 8 also autoscrolls when you are over a scrollbar, but it also
autoscrolls if you are within about 3 pixels of an edge.  This happens
even when not in fullscreen mode.  If there's a scrollbar, this happens
within about 3 pixels of the scrollbar.  This also applies to iframes,
but doesn't seem to apply to div's with scrollbars (see URL for test
case, the div case is probably a bug).

So I think there are 2 bugs:
1) We should not count scrollbars as part of the content area when computing 
the drag speed.  It looks like WebKit currently determines the drag speed based 
on the mouse pointer distance outside the page.  Fixing this would fix the 
original bug report at http://crbug.com/44435

2) If within 3 pixels of an edge, autoscroll like IE.  I'm not 100% sure
we should do this on all platforms because IE is the only application
that seems to do this.  Wordpad (win) and TextEdit (mac) don't do this.
Maybe windows only.  Anyway, it seems like this should be a separate
bug.

Your patch seems closer to (2), but it doesn't take into account
scrollbars and seems to be too big (30 instead of only 3).  Maybe we
should fix (1) first?

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/21

------------------------------------------------------------------------
On 2010-06-10T06:12:16+00:00 morrita wrote:

Hi Tony, thank your for your investigation!

> Your patch seems closer to (2), but it doesn't take into account scrollbars 
> and seems to be too big (30 instead of only 3).  Maybe we should fix (1) 
> first?
That's totally makes sense!
I filed (1) as Bug 40403.
It looks good idea to tackle 40403 first because it is apparently a bug .
 
Anyway, I'll cancel this review due to pixel width issue you mentioned.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/22

------------------------------------------------------------------------
On 2026-10-09T13:33:23+00:00 fred.wang wrote:

(In reply to Hajime Morrita from comment #0)
> Created attachment 56580 [details]
> a repro
> 
> Derived from http://crbug.com/44435 but the problem is applicable all
> browsers that support fullscreen view.
> 
> How to reproduce:
> - switch to fullscreen view
> - open attached html
> - select text with mouse, dragging it to right side of the view
> 
> Expected result:
> - The view scrolls to right
> What happens instead:
> - The view doesn't scroll

Tested with Safari 27.0.1 on macOS. For me the view still scrolls when
dragging the text after entering fullscreen, so resolving. But feel free
to reopen if you still see the issue.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/582165/comments/24


** Changed in: webkit-open-source
       Status: New => Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582165

Title:
  Mouse drag doesn't scroll horizontally when selecting long line in
  maximized window

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/582165/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to