Prevent battery slider XAML startup crash - #516
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
_frontendis null.Root cause
DevicePageis created directly byMainWindow. DuringSlider.Minimuminitialization, WinUI may coerce the initial value and raiseValueChangedbefore later-named XAML elements have been created. The battery handler previously touchedBatteryChargeLimitValueTextwithout the existing frontend-startup guard, causing the UI process to fail duringMainWindow.InitializeComponent().Validation
Scope
This is a narrow UI startup hotfix. It does not change the battery hardware protocol, runtime lifecycle, persistence, IPC, or unrelated UI behavior.