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
refactor: tooltips using CSS solution to JS solution #639
Merged
Merged
Changes from all commits
Commits
Show all changes
64 commits
Select commit
Hold shift + click to select a range
f7d0dab
build(shared): tooltip library with lazy loading
sshanzel 9fa8872
feat: LazyTooltip with animation and base design
sshanzel 92a9c14
refactor(shared): button component to accommodate forwardedRef
sshanzel 6ec95fd
refactor(shared): lazytooltip default placement
sshanzel 20cd1b4
fix(shared): tooltip right placement out animation
sshanzel a3b7dfc
refact(shared): forwardRef for buttons as default
sshanzel df2588a
refactor(shared): migrate all existing tooltip implementations using …
sshanzel 10965c4
fix(shared): button support for both forwarded and non-forwarded impl…
sshanzel 618ba35
refactor(shared): tooltip accessibility support
sshanzel 488d430
fix(shared): tooltip usage of forwardedRef
sshanzel 7aa0ab9
refactor(shared): tootlip using dynamicParent
sshanzel 9d84bc7
refactor(shared): usage of lazy tooltip with dynamic parent
sshanzel 75c1bb5
Revert "refactor(shared): migrate all existing tooltip implementation…
sshanzel 3d417a9
revert: ForwardedButton implementations
sshanzel a38f34a
feat: sample usage of tooltip
sshanzel e174e16
Merge branch 'master' of github.com:dailydotdev/apps into DD-229-refa…
sshanzel bc4d2ba
fix: allowed tags
sshanzel 03be114
refactor: avoid loading tooltip on touch devices
sshanzel a4a7dfd
revert: changes on utilizing tooltip
sshanzel 4959781
refactor: primary components for tooltip
sshanzel 64fa9df
fix: components not using forward ref
sshanzel b81e8ec
refactor: forward ref
sshanzel bb372a4
fix: build issues
sshanzel cf97262
wip: sample failing tests on implementation
sshanzel 081960d
refactor: button properties
sshanzel 52c0b73
fix: disabling of tooltip on test env
sshanzel 42fa76c
fix: usage of dynamic tooltip
sshanzel 7c64bd4
refactor: tooltip component less code
sshanzel 4a8db7e
refactor: webapp css tooltip to js
sshanzel 7915055
refactor: extension css tooltip to js
sshanzel 1254a80
fix: propert placement
sshanzel 6173283
refactor: clickable text as forwarded ref
sshanzel aa6394f
refactor: unnecessary prop
sshanzel ba22ec4
refactor: should load tooltip as function
sshanzel c36c690
refactor: complete transition to js tooltip
sshanzel a2d4411
fix: comment tooltip placement
sshanzel 2e2af96
Merge branch 'master' into DD-229-refactor-tooltips
sshanzel e0587af
refactor: unnecessary changes
sshanzel de4cfb5
refactor: unnecessary changes
sshanzel c6bf1a7
refactor: unnecessary changes
sshanzel 0a96ddf
refactor: unnecessary changes
sshanzel 0d8d764
refactor: unnecessary changes
sshanzel fc2d13d
refactor: test env variable
sshanzel c9fe179
ci: test env
sshanzel 6fd37a3
fix: unnecessary ref
sshanzel b21e683
refactor: unused default export
sshanzel 8d45085
refactor: proper tooltip name
sshanzel 2f3154b
feat: next link with tooltip
sshanzel 659426f
refactor: tooltips using ref
sshanzel e1ac00f
refactor: conditional tooltip on tooltip itself
sshanzel 0a6515e
refactor: unnecessary env variable
sshanzel 056eaf5
fix: build issue
sshanzel 200f091
fix: build issue
sshanzel b741621
refactor: translate3d utilization
sshanzel d52a0a0
refactor: will-change property on tooltip
sshanzel 4a02314
fix: ref bug on multiple pass
sshanzel 93abdd1
Merge branch 'master' into DD-229-refactor-tooltips
sshanzel b2634f9
refactor: encapsulate tooltips
sshanzel 5a41eff
refactor: unnecessary dynamic loading
sshanzel a9b6571
refactor: type name
sshanzel 8f053bd
refactor: export link with tooltip
sshanzel 126df7e
fix: left option placement
sshanzel c51d08c
Merge branch 'master' into DD-229-refactor-tooltips
sshanzel 5514b38
Merge branch 'master' into DD-229-refactor-tooltips
sshanzel File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
Just throwing this one out here:
Is there no way to have the SimpleTooltip determine if the direct child is a
<Link>
and then do something else?Think it would be super cool if we could just have 1 sole component for the tooltip usage.
If it's not possible, this seems like a good first step!
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.
Thank you for the review! 🚢
That's a cool idea. Though the part where it got me separating the two is the way we will be handling the trigger element itself. The other one, we will be wrapping the children, and the other one will be utilizing the
ref
of the actual element sincenext/link
has problems with accepting custom components.Combining them in a single component might provide quite a bit of complexity (as having multiple conditions whether to apply a ref or not). To keep things simple and easier to understand for each scenario, I had separated them.