Page MenuHomePhabricator

[native] introduced fixed location option for tooltip toolbar
ClosedPublic

Authored by ginsu on Oct 24 2022, 9:31 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Oct 25, 10:43 PM
Unknown Object (File)
Fri, Oct 25, 10:43 PM
Unknown Object (File)
Fri, Oct 25, 10:43 PM
Unknown Object (File)
Fri, Oct 25, 10:43 PM
Unknown Object (File)
Fri, Oct 25, 10:42 PM
Unknown Object (File)
Fri, Oct 25, 10:37 PM
Unknown Object (File)
Oct 15 2024, 2:40 AM
Unknown Object (File)
Sep 26 2024, 10:29 PM

Details

Summary

Will not land diff until all diffs in stack are accepted

introduced fixed as a loction option for the tooltip toolbar. The following tooltips will be using the fixed option: multimedia-message.react, robotext-message.react, and text-message.react


Linear Task: ENG-2037

Test Plan

Please watch the demo to see that multimedia-message.react, robotext-message.react, and text-message.react now only get the tooltip placed below the message, this is to be expected and will be addressed later:

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu requested review of this revision.Oct 24 2022, 9:43 AM
native/chat/multimedia-message.react.js
146 ↗(On Diff #17866)

Doesn't seem like we need a variable for this anymore. Let's move it to where it's used

native/navigation/tooltip.react.js
318 ↗(On Diff #17866)

Where does 32 come from?

native/navigation/tooltip.react.js
318 ↗(On Diff #17866)

it's the fixed margin to the bottom of the chat window- i will pull out this number into a variable so that it is more descriptive

atul requested changes to this revision.Oct 24 2022, 10:58 AM

Sending back to your queue while you address feedback

This revision now requires changes to proceed.Oct 24 2022, 10:58 AM

addressed ashoat's comments

planning changes to fixedMargin variable

Would love to understand the 32 number better! I have a suspicion that we shouldn't be hardcoding that... eg. if it's the height of some React Nav component, I think there's an API for that... or if it's the height of one of our components, we should probably keep that constant in the same file as that component (if not something better like what React Nav does)

Would love to understand the 32 number better! I have a suspicion that we shouldn't be hardcoding that... eg. if it's the height of some React Nav component, I think there's an API for that... or if it's the height of one of our components, we should probably keep that constant in the same file as that component (if not something better like what React Nav does)

Will address this in a future diff

just introducing fixed option

ginsu edited the test plan for this revision. (Show Details)
ginsu added 1 blocking reviewer(s): atul.
ginsu edited the test plan for this revision. (Show Details)
This revision is now accepted and ready to land.Oct 26 2022, 12:55 PM