-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(logical-size): Implement the LogicalSize property in Axe.Windows #1020
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1020 +/- ##
==========================================
- Coverage 73.70% 72.13% -1.57%
==========================================
Files 398 424 +26
Lines 12046 13216 +1170
Branches 0 1420 +1420
==========================================
+ Hits 8878 9534 +656
- Misses 3168 3265 +97
- Partials 0 417 +417 ☔ View full report in Codecov by Sentry. |
22b5ee0
to
c7ce931
Compare
Co-authored-by: Dave Tryon <45672944+DaveTryon@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but it might make sense to add some tests for this new logic. One obvious example would be the ToStringTest for the A11yProperty.
I've added a unit test for the
|
…1024) Axe.Windows follows semantic versioning, which states: > Given a version number MAJOR.MINOR.PATCH, increment the... MINOR version when you add functionality in a backward compatible manner I think 6d72b85 and d2a5c65 qualify as "new functionality" for these purposes, justifying a minor version bump. Also includes a small fix-up of #1020 to prevent execution of `a11yProperty.ToSize` on properties other than `LogicalSize`.
private PropertyType() : base() | ||
{ | ||
// Explicitly add pseudo-properties | ||
Dic[Axe_LogicalSizePseudoPropertyId] = GetNameInProperFormat("Axe_LogicalSizePseudoPropertyId", Axe_LogicalSizePseudoPropertyId); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should PropertyTypesTests.cs be updated to check that the pseudo-property exists and that the contents make sense? Abstracting out the screen DPI could get interesting...
Details
This PR adds a "pseudo-property",
LogicalSize
, a normalized size based on an element'sBoundingRectangle
to aid in touch size calculations.Motivation
Part of Feature 2152841 (internal access required to view).
Pull request checklist