[CP-beta] Remove EnableTransparentWindowBackground because it did nothing important and because Windows 10 does not support DWMWA_SYSTEMBACKDROP_TYPE (#187848)#188186
Conversation
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
|
An existing Git SHA, To re-trigger presubmits after closing or re-opeing a PR, or pushing a HEAD commit (i.e. with |
This comment was marked as outdated.
This comment was marked as outdated.
…tant and because Windows 10 does not support DWMWA_SYSTEMBACKDROP_TYPE (flutter#187848) This pull request makes multi-window functional on Windows 10 and removes an unnecessary call during window setup. ## What's new? - Removes call to `EnableTransparentWindowBackground` on `HostWindow` create. In fact, this does not work at all 🎉 Transparency on popups was not implemented with the current implementation. We should do something more complex to make it work, but it has clearly been broken for a while now fixes flutter#186522 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing.
90b4e63 to
672dc44
Compare
|
@LongCatIsLooong This was hitting some weird CI failures (example). I rebased the PR to get a fresh CI run. |
|
CI had a failure that stopped further tests from running. We need to investigate to determine the root cause. SHA at time of execution: 672dc44. Possible causes:
A blank commit, or merging to head, will be required to resume running CI for this PR. Error Details: Stack trace: |
|
auto label is removed for flutter/flutter/188186, Failed to merge flutter/flutter/188186 with Pull request flutter/flutter/188186 could not be merged: Required status check "ci.yaml validation" is expected.. |
|
autosubmit label was removed for flutter/flutter/188186, because - The status or check suite Windows windows_host_engine_test has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
autosubmit label was removed for flutter/flutter/188186, because - The status or check suite Windows windows_host_engine_test has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
Windows windows_host_engine_test is consistently failing for this CP. The beta release is currently blocked by #188075 so this may not be high priority. |
|
I think the test failures are something else:
See also:
I'll cherry pick the revert PR for the Windows stylus buttons. That will need to land before this cherry pick. EDIT: Here's the cherry pick for the revert PR: #188341 |
9281300
into
flutter:flutter-3.46-candidate.0
This is for fixing a flaky test so no changlog entries needed.
Hopefully this resolves #188182
I doubt we can use the auto-CP bot because the initial beta has not been released.
Original PR: #187848
Pre-launch Checklist
///).Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.