This repository was archived by the owner on Feb 25, 2025. It is now read-only.
[web] Migrate Flutter Web DOM usage to JS static interop - 11. #33190
Conversation
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
joshualitt
force-pushed
the
html_11
branch
3 times, most recently
from
84e18eb to
d3729e2
Compare
Contributor
Author
|
@yjbanov ptal. Please only look at CL 11: Or using compare: joshualitt/engine@html_10...joshualitt:html_11 |
joshualitt
force-pushed
the
html_11
branch
2 times, most recently
from
6790d4b to
530ccff
Compare
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/flutter
that referenced
this pull request
May 16, 2022
houhuayong
pushed a commit
to houhuayong/engine
that referenced
this pull request
Jun 21, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This is CL 11 in a series of CLs to migrate Flutter Web DOM usage to the new JS static interop API.