compositor: Remove the CompositorMsg::TouchEventProcessed message#39811
Merged
mrobinson merged 1 commit intoservo:mainfrom Oct 17, 2025
Merged
compositor: Remove the CompositorMsg::TouchEventProcessed message#39811mrobinson merged 1 commit intoservo:mainfrom
CompositorMsg::TouchEventProcessed message#39811mrobinson merged 1 commit intoservo:mainfrom
Conversation
kongbai1996
reviewed
Oct 13, 2025
| result, | ||
| ); | ||
|
|
||
| if let Some(webview) = self.get_webview_handle(webview_id) { |
Contributor
There was a problem hiding this comment.
If the compositor consumes this input event, does it still need to be sent to the webview for processing?
Member
Author
There was a problem hiding this comment.
Yes, this is to inform the embedder that the event was processed and handled so it can stop tracking it.
The renderer needs needs to know when touch events processing has finished in the DOM in order to properly handle them. This was previously done using the `CompositorMsg::TouchEventProcessed` message. This message is now redudant with the general-purpose `EmbedderMsg::InputEventHandled` message. This change removes the former message and instead, has the `TouchHandler` keep a `HashMap` of pending touch events which is uses to finish their processing when they come back from script. The goal here is reduce the number of messages sent and to keep the complexity of touch handling more centered in the `TouchHandler`. Signed-off-by: Martin Robinson <[email protected]>
fe90a05 to
897ca9d
Compare
|
🔨 Triggering try run (#18552253136) for Linux (WPT) |
|
Test results for linux-wpt from try job (#18552253136): Flaky unexpected result (27)
Stable unexpected results that are known to be intermittent (34)
|
|
✨ Try run (#18552253136) succeeded. |
mukilan
approved these changes
Oct 17, 2025
mrobinson
added a commit
to mrobinson/servo
that referenced
this pull request
Oct 20, 2025
A recent PR (servo#39811) introduced an unconditional panic on touch events. This change fixes that issue.
mrobinson
added a commit
to mrobinson/servo
that referenced
this pull request
Oct 20, 2025
A recent PR (servo#39811) introduced an unconditional panic on touch events. This change fixes that issue. Signed-off-by: Martin Robinson <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 20, 2025
A recent PR (#39811) introduced an unconditional panic on touch events. This change fixes that issue. Testing: This can be verified manually by triggering any touch event. Signed-off-by: Martin Robinson <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The renderer needs needs to know when touch events processing has
finished in the DOM in order to properly handle them. This was
previously done using the
CompositorMsg::TouchEventProcessedmessage.This message is now redudant with the general-purpose
EmbedderMsg::InputEventHandledmessage.This change removes the former message and instead, has the
TouchHandlerkeep aHashMapof pending touch events which is uses tofinish their processing when they come back from script. The goal here
is reduce the number of messages sent and to keep the complexity of
touch handling more centered in the
TouchHandler.Testing: This should not change observable behavior, so is covered by existing tests.