Decouple EventWithLatencyInfo from WebInputEventTraits
Only EventWithLatencyInfo uses [Can]Coalesce() from WebInputEventTraits. WebInputEventTraits gets used for IPC stuff so is kinda sensitive, but EventWithLatencyInfo isn't involved with IPC. So, coupling these together also makes refactoring unnecessarily difficult. E.g. the coupling means that if we want to move EventWithLatencyInfo to a component, then WebInputEventTraits and a bunch of dependencies that EventWithLatencyInfo doesn't care about need to come as well. To decouple, the guts of [Can]Coalesce() moves to a new .cc file for EventWithLatencyInfo. The types are known, so we get some added type safety versus WebInputEventTraits which isn't templatized in the .h. The instantiations in the .cc become a bit simpler and the runtime type checks and static casts behind in web_input_event_trait.cc's Apply(..) are not required. BUG=615948 TBR=jochen@chromium.org (iwyu) Review-Url: https://codereview.chromium.org/2111593003 Cr-Commit-Position: refs/heads/master@{#403402}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment