502f22686cf88af95f8da0af9b5a8feb4c170f98
PresShell::HandleEvent dispatch preceding pointerrawupdate event r=smaug,dom-core,edgar
This patch tries to dispatch `ePointerRawUpdate` with `PresShell::EventHandler::DispatchPrecedingPointerEvent` as same as usual pointer events. For using the path, this patch adds 2 internal events, `eMouseRawUpdate` and `eTouchRawUpdate` which are never dispatched into the DOM because `PresShell::EventHandler::DispatchPrecedingPointerEvent` will return `false` for that and then the caller will stop handling the internal events. There are 3 dispatchers of the internal raw update events. One is `PresShell::EnsurePrecedingPointerRawUpdate()`. This dispatches the internal event if and only if the coming event of `PresShell::HandleEvent` will cause `ePointerMove`. The reason why `PresShell::HandleEvent` handles the preceding raw-update event is, we should support `ePointerRawUpdate` events for synthesized events for tests (in-process ones) and in the main process. Additionally, if a `pointerrawupdate` event may destroy the target `<iframe>`. In such ase, the following `pointermove` may need to be dispatched on its parent window or another `<iframe>` window. Therefore, we need to dispatch the internal raw update event before considering the target window (`PresShell`) and handling the capturing element. The others are `BrowserChild::RecvRealMouseMoveEvent` and `BrowserChild::RecvRealTouchMoveEvent`. They dispatch the internal events when they won't dispatch the received event immediately to coalesce with further similar input. For avoiding to dispatch the internal event for same source event, this adds `WidgetPointerHelper::convertToPointerRawUpdate` member to check it in `PresShell::HandlePrecedingPointerRawUpdate`. Differential Revision: https://phabricator.services.mozilla.com/D243404
Bug
1963727 - Set dlltool when building rust code while targeting mingw. r=firefox-build-system-reviewers,sergesanspaille
Bug 1932150 - Allow using flat tree order for point comparing in selection r=jjaschke,smaug,dom-core
…
…
…
…
…
…
Bug 1872229 - Move mozilla-lint-rules to tooling-lint r=tcampbell,android-reviewers,adhingra,mcarare
An explanation of the Firefox Source Code Directory Structure and links to
project pages with documentation can be found at:
https://firefox-source-docs.mozilla.org/contributing/directory_structure.html
For information on how to build Firefox from the source code and create the patch see:
https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
If you have a question about developing Firefox, and can't find the solution
on https://firefox-source-docs.mozilla.org/, you can try asking your question on Matrix at chat.mozilla.org in `Introduction` (https://chat.mozilla.org/#/room/#introduction:mozilla.org) channel.
Nightly development builds can be downloaded from:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://www.mozilla.org/firefox/channel/desktop/#nightly
Keep in mind that nightly builds, which are used by Firefox developers for
testing, may be buggy.
Description
Languages
JavaScript
32.6%
C++
25.1%
HTML
20.9%
C
10.6%
Python
2.8%
Other
7.6%