Skip to content

Conversation

@TooTallNate
Copy link
Member

This gives a slight performance boost, since before we would potentially be calling getBoundingClientRect() twice.

Now the TextRectangle is being re-used, and works with more types of Nodes. So now component/tip should be compatible with regular DOM Elements, TextNode instances and Ranges.

Also removes a TODO: extract this into a standalone module comment from the now-deleted dimensions() function.

This gives a slight performance boost, since before we would
potentially be calling `getBoundingClientRect()` twice.

Now the TextRectangle is being re-used, and works with more
types of Nodes. So now `component/tip` should be compatible
with regular DOM Elements, TextNode instances and Ranges.
TooTallNate added a commit that referenced this pull request Dec 16, 2014
…-module

Use "bounding-client-rect" component
@TooTallNate TooTallNate merged commit 7c1c02a into master Dec 16, 2014
@TooTallNate TooTallNate deleted the update/use-bounding-client-rect-module branch December 16, 2014 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants