I feel like we should still reduce the width for viewer-composed multimedia messages so all the multimedia messages have a consistently smaller size,
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 15 2023
fix maxWidth for chat bubble so it's not poking out anymore (see test plan for visulization)
With the red border, is that a parent component of the message box? (Generally I would expect the parent component to enclose the child component.)
Have you made sure that that the height measurement code is still working correctly?
thanks for doing this!
Mar 14 2023
Okay sounds good i'll have an update out shortly with a cleaner syntax
address feedback
address feedback
Mar 13 2023
Mar 12 2023
Mar 10 2023
Mar 9 2023
Not an expert in C++ but your code follows the pattern I used when writing the C++ message spec for reactions. Would be helpful to get a second pair of eyes here
I think we should consider if we also need shimUnsupportedMessageInfo and unshimMessageInfo. These functions will help us support older native clients that haven't been updated yet.
Accepting, but if what I suggested doesn't take too long might be worthwhile to update
Mar 8 2023
Mar 2 2023
rebase before landing
rebase before landing
Feb 28 2023
address feedback
Does D6632 need to be updated so that getEmojiKeyboardPosition no longer looks at emojiKeyboard.getBoundingClientRect()?
I attempted to address the feedback above, but still running into one issue where the node passed through the ref still has a height and width of zero. (I saw this by logging node.getBoundingClientRect() in emojiKeyboardRef
address feedback
Feb 27 2023
Feb 26 2023
rebase before landing
rebase before landing
rebase before landing
rebase before landing
Feb 24 2023
address ashoat's comments
address ashoat's comments
Feb 23 2023
address ashoats comments
address ashoat's comments