Closed
Conversation
flutter/engine@c1e322b Dart cherry-picks for 1.12.13 37f9c54 Use RenderSliverPadding to inset SliverFillViewport
* flutter/engine@6955b06 Cherry-picks for 1.12.13 * flutter/engine@3e6d6bc add pointer data santizing in flutter web engine * 09126ab Enable Android embedding v2 on the beta, dev and stable channel * 4c95bbd Re-enable hostonly tests on non-master branches * 066a992 Ensure that docker tag is legal * 4484ae4 [flutter_tool] Do not continue with a no-op 'upgrade'
* flutter/engine@ac93919 v1.12.13+hotfix.3 cherry-picks * flutter/engine@73da385 Disable a11y on detach * d88345e only run codecov on master * 6d848eb Name the docker_builer shard * e98acc7 [flutter_tool] Print version info on a no-op upgrade * 8eb6a92 Always compile with isysroot on iOS to point to SDK root * fb69a39 Add bitcode and architectures to App.framework build ios framework command
* flutter/engine@2994f7e v1.12.13+hotfix.5 cherry-picks * flutter/engine@57afd86 Remove specificity on Android and iOS * flutter/engine@253851e Move Fuchsia unit test runners into engine repo
* b63683b Update configuration for flutter features
* flutter/engine@a677925 Cherry pick infra testing updates into hotfixes * flutter/engine@b1bb773 Raise API level for reportFullyDrawn * flutter/engine@a433ed9 v1.12.13+hotfix.7 cherry-picks * google/skia@a640745 Disable QCOM_tiled_rendering while we wait for test devices * flutter/engine@bcb8267 Revert "Do not default to downstream affinity on iOS insertText" * d345a3b Revert "Track and use fallback TextAffinity for null affinity platform TextSelections. (#44622)" * bd25f70 Upgrade dartdoc to 0.29.3 * 7915e58 Change firebase Pixel3 version from Q-beta3 to 29
fluttergithubbot
added
engine
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 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.
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change. If you're changing visual properties, consider including before/after screenshots (and runnable code snippets to reproduce them).
Related Issues
Replace this paragraph with a list of issues related to this PR from our issue database. Indicate, which of these issues are resolved or fixed by this PR.
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?