| Commit-Queue | +1 |
Hello Robert, this is the CL that fade-out scrollbars without forwarding wheel events.
Could you please take a look? Thank you!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The browser test is flacky. I'll rewrite the test and activate this CL again.
Sorry for the confusion!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Hello Robert,
This is the CL that fade-out scrollbars without forwarding wheel events. (I submitted new CL to simplify the patch set history, and abandoned the old one)
The flaky browser test is guarded with IS_MAC build flag since the wheel scroll latching browser test is flaky on android even if it is an empty test.
Could you please review this? Thank you again!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Byungwoo Lee abandoned this change.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
DROP_EVENT_AND_FADEOUT_SCROLLBARS,I'm not comfortable adding a special one-off disposition for these events that is essentially equivalent to DID_NOT_HANDLE_NON_BLOCKING - i.e. the main thread needs to be sent the events and they aren't cancellable.
There must be a better way to prevent the unexpected behavior.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
(just a driveby review)
void FadeOutScrollbarsOnCurrentFrame();nit: we typically would name this something like FadeOutScrollbarsInternal if it's just a helper called from the public function
event.wheel_ticks_x = event.delta_x / 10;nit: is 10 a magic number? why 10?
DROP_EVENT_AND_FADEOUT_SCROLLBARS,This sounds more like a directive than a disposition. That doesn't seem correct. This should still be a DROP_EVENT and necessary other plumbing needs to be added to schedule a scrollbar fade out
return DROP_EVENT_AND_FADEOUT_SCROLLBARS;I think we can just directly request a scrollbar fadeout here maybe?
event_disposition = InputHandlerProxy::DROP_EVENT;This confirms that FADEOUT_SCROLBLAR part seems to just a way to get from input_handler to widget_input_handler_manager and post a task. Maybe we can do direct plumbing instead