Complete typography support across PowerBGInfo - #70
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
BoldandUnderlineinputs while making the explicit numeric/style properties authoritative when both are suppliedExample
Compatibility and release boundary
Bold/ValueBoldandUnderline/ValueUnderlineremain supported. ExplicitFontWeightandUnderlineStylevalues take precedence. Numeric weights accept the full 100-900 range, including intermediate CSS weights such as 550 and 650.ChartForgeX 1.7.0 is now published and contains the shared typography API used by this change. PowerBGInfo consumes that public three-part release directly and has been revalidated through the normal package restore path; no unpublished dependency or downstream compatibility shim is used.
Validation
Fixes #69