fix: Windows FrameView always appearing inactive #38468
Merged
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 of Change
Closes #38385.
Refs CL:4435695.
Fixes an issue where Windows
FrameView
s always appeared inactive regardless of focus status. This was happening because Chromium added extra plumbing to set active state as a function of whether or not indelegate_->ShouldPaintAsActive();
wastrue
inHWNDMessageHandler::PaintAsActiveChanged()
, and we'd overridden it to return false.Confirmed not to regress #24647.
Checklist
npm test
passesRelease Notes
Notes: Fixes an issue where Windows
FrameView
s always appeared inactive regardless of focus status.