-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Feature: Tooltip for workspace chat #45390
Feature: Tooltip for workspace chat #45390
Conversation
Update: I had several issues:
|
@tienifr did you fix those issues or ask for help if you need it? We want to keep this PR moving. CC: @dukenv0307 as you'll have some context on this. |
@tienifr Can you update the PR and let me know what's your blocker right now? Thanks |
@tienifr you have conflicts. Can you fix those and confirm this is ready for a review today? |
@dukenv0307 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
@tienifr Is it ready for review? |
Bump, @tienifr please confirm this is ready for re-review? |
Other than the bug, the videos above looked good to me! |
<View style={pointerStyle} /> | ||
</View> | ||
</Animated.View> | ||
<Portal hostName={!shouldUseOverlay ? 'modal' : undefined}> |
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.
Teleport the portal to the modal layer, otherwise, the tooltip in any modal/popover would be obscured by that modal. For example the tooltip for QAB.
return; | ||
} | ||
setShouldUseOverlay(false); | ||
hideTooltip(); |
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.
Interacting with shouldRender
prop causes the target component to re-render thus leads to flickering. I move the logic to hide tooltip from the target component (i.e. composer) to inside the tooltip itself to avoid such flickering.
@dukenv0307 I fixed the Android bug above and also discovered several other bugs. Added explanations for them above ^. Ready for review. |
…oltip-for-workspace-chat
@dukenv0307 Thanks for the suggestions. Updated. |
LGTM |
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.
Looks good, thanks!
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by https://github.com/deetergp in version: 9.0.18-0 🚀
|
This PR is failing for Desktop app because of issue #47169 |
🚀 Deployed to production by https://github.com/mountiny in version: 9.0.18-10 🚀
|
}} | ||
wrapperStyle={styles.reportActionComposeTooltipWrapper} | ||
shiftHorizontal={variables.composerTooltipShiftHorizontal} | ||
shiftVertical={variables.composerTooltipShiftVertical} |
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.
On mobile safari, the viewport is scrolled when the keyboard is shown. We should also add the topOffset
here to avoid this bug.
More details: #53976 (comment)
Details
Display a tooltip the first time user views the workspace chat.
Fixed Issues
$ #45046
PROPOSAL: #45046 (comment)
Tests
new.expensify.com
link from the email in a different browserGet started! Submit your first expense
or¡Empecemos! Presenta tu primer gasto
Offline tests
NA
QA Steps
See Tests
PR Author Checklist
### Fixed Issues
section aboveTests
sectionOffline steps
sectionQA steps
sectiontoggleReport
and notonIconClick
)myBool && <MyComponent />
.src/languages/*
files and using the translation methodSTYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
)Avatar
is modified, I verified thatAvatar
is working as expected in all cases)Design
label and/or tagged@Expensify/design
so the design team can review the changes.ScrollView
component to make it scrollable when more elements are added to the page.main
branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTest
steps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop