[web] Migrate Flutter Web DOM usage to JS static interop - 2#32910
[web] Migrate Flutter Web DOM usage to JS static interop - 2#32910joshualitt merged 1 commit intoflutter:mainfrom
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
flutter-dashboard
bot
added
platform-web
joshualitt
force-pushed
the
html_2
branch
2 times, most recently
from
801cb0c to
1bfd654
Compare
|
Gold has detected about 1 new digest(s) on patchset 2. |
joshualitt
force-pushed
the
html_2
branch
2 times, most recently
from
167ebcc to
17c9873
Compare
|
@srujzs @eyebrowsoffire ptal. I'm not sure if this is the best way to get a dependent pr reviewed, but please only look at CL 2, or use this link: joshualitt/engine@html_1...joshualitt:html_2 |
|
LGTM |
|
test-exempt: code refactor with no semantic change |
|
@eyebrowsoffire friendly ping in case this slipped between the cracks. |
5 participants
This is CL 2 in a series of CLs to migrate Flutter Web DOM usage to the new JS static interop API.