Closed Bug 652240 Opened 14 years ago Closed 3 years ago

Mouse event forwarding needs to take content views into consideration

Categories

(Core :: DOM: Content Processes, defect, P5)

Product:
Core
Component:
DOM: Content Processes
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: stechz, Unassigned)

References

Details

Fennec has to generate its own mouse events in the content process because the offsets will be incorrect for mouse events for the default forwarded ones. Platform needs to account for the offsets in content views before forwarding the events.
What is a content view?
Blocks: 656114
do we still need it ?
Not need, but yes, this would be a good for Fennec because we could remove some code that should be handled by the platform.
What is a content view? Would this fix bug 678193?
A content view contains the scale and the scroll position of content in the chrome process. This is asynchronous with the content process. Fixing this bug is a refactoring, and maybe not even that useful for Fennec. It makes the platform work out of the box when clicking on things in our asynchronous scrolling case. I thought it might mean we could get rid of our target finding code in Fennec, but we still need to do our bounds hit testing to make sure the user clicked on something useful. This is low priority.
Component: IPC → DOM: Content Processes
Blocks: 1030721
No longer blocks: 656114
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5

The blocked bug has been fixed without this and nobody ever asked for it again.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.