New issue
Advanced search Search tips

Issue 824521 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 824772



Sign in to add a comment

Scrolling when touch down starts on OOPIF slow and jittery

Project Member Reported by fsam...@chromium.org, Mar 21 2018

Issue description

1. Go to slashdot.org
2. Open up devtools and go into device emulation mode
3. Emulate a Pixel2 XL.
4. Try to scroll, when you see an OOPIF start the scroll from there.
5. Notice that the scroll is bouncy and slow.
 
Cc: dgozman@chromium.org
fsamuel@ ... mcnee@ and I need to send you cake or flowers or something! ;-)

This is the repro we've been looking for for issue 818214 ...

But this is a separate issue: dev tools doesn't use the normal event routing pathway for touch events, i.e. they don't go through RenderWidgetHostInputEventRouter at all ... instead mouse events get converted to touch events and directly sent to the oopif's renderer ... so scroll bubbling gets all messed up.

We really need to fix how devtools converts mouse to touch events and then sends them to the oopif's renderer.
[87974:87974:0321/182110.609816:FATAL:render_widget_host_input_event_router.cc(799)] Check failed: resending_view != bubbling_gesture_scroll_target_.target (0x31882f41bd80 vs. 0x31882f41bd80)
#0 0x7fc78ad8b49c base::debug::StackTrace::StackTrace()
#1 0x7fc78adb562b logging::LogMessage::~LogMessage()
#2 0x7fc788668c13 content::RenderWidgetHostInputEventRouter::BubbleScrollEvent()
#3 0x7fc7883f069d content::CrossProcessFrameConnector::BubbleScrollEvent()
#4 0x7fc788675ff6 content::RenderWidgetHostViewChildFrame::GestureEventAck()
#5 0x7fc788661414 content::RenderWidgetHostImpl::OnGestureEventAck()
#6 0x7fc7885bd709 content::GestureEventQueue::AckCompletedEvents()
#7 0x7fc7885bcb25 content::GestureEventQueue::ProcessGestureAck()
#8 0x7fc7885c10cb content::InputRouterImpl::GestureEventHandled()

Blockedon: 824772
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Status: Fixed (was: Assigned)
I think this is fixed now, potentially on account of 824772 being fixed. Can anyone else still reproduce this? I'm going to tentatively close it, but please re-open if it still repros.

Sign in to add a comment