feat(useMeasure): support custom measurers in order to support border-box and others#1603
Merged
xobotyi merged 1 commit intoJul 25, 2026
Merged
Conversation
xobotyi
requested changes
Jan 30, 2025
Contributor
|
Thanks for contribution! |
xobotyi
changed the title
ResizeObserverEntry matcher callback
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1603 +/- ##
==========================================
+ Coverage 82.97% 83.01% +0.04%
==========================================
Files 62 62
Lines 828 830 +2
Branches 151 151
==========================================
+ Hits 687 689 +2
Misses 16 16
Partials 125 125 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Measures came from the content box only, so consumers laying out in border-box read sizes without paddings and borders. A second parameter takes a measurer deriving `Measures` from the observer entry: `contentBoxMeasurer` stays the default, `borderBoxMeasurer` ships next to it for opt-in border-box sizing. Re-measurement still rides on the shared observer's default box, so a padding-only change that leaves the content box intact emits no new measurement. Closes: react-hookz#1548
xobotyi
force-pushed
the
feat/use-measure-matcher
branch
from
July 25, 2026 22:35
34b5df0 to
ef74bf4
Compare
Contributor
|
🎉 This PR is included in version 25.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
2 participants
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.
What is the current behavior, and the steps to reproduce the issue?
Current implementation of the
useMeasurehook calculates the element bounds based on content-box model only.It is a little unexpected behavior when the project and all the layout is based on border-box model and trying to calculate measures of the element has paddings.
Thus, current hook ignores paddings calculating element's width and height.
What is the expected behavior?
Giving the possibility to define custom measure matcher model to take the values needed.
How does this PR fix the problem?
By adding the additional optional function argument receives the
ResizeObserverEntryvalue and returns the new measures should be applied ornull. If function returnsnull, the default behavior is applied and content-box measures will be returned.Checklist
useMeasurehook elements box-sizing option #1548