-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2022-11-02] [Bug] [$500] HTML formatted messages render incorrectly #11320
Comments
Triggered auto assignment to @aldo-expensify ( |
@mvtglobally can you detail a bit more what you mean by: "send some HTML messages", ideally providing some content we could copy paste to reproduce? I tried sending a message with HTML like |
@aldo-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Tested again in web mobile / web not mobile/ android and IOS, couldn't reproduce. Maybe it fails with some specific html layout. @mvtglobally do you know from where that html was copied from? |
@aldo-expensify This is a Concierge message composed in the Concierge tool. (I just checked my messages in a test account and I wasn't able to find one like this). |
@JmillsExpensify thanks, I didn't consider that. I tested sending some copy/pasted html message from wikipedia, with links and lists, and the look fine. I looked for some of the text we can see in the message from the screenshots of the GH issue, but I couldn't find it in the code.. so I supposed it is not an automatic Concierge message. |
Yeah, I think this message came during one of our VIP projects. Hmm, maybe we should close then. I'm also not seeing this either. |
@JmillsExpensify hehe i just noticed you reported this by looking at the slack conversation. Is it possible for you to get to this same conversation and check if now it is looking fine? |
Yep! Sure thing, I'll go ahead and assign myself. |
thanks! |
I didn't get a chance to test this so far, will come back soon. |
Ok jumping back in to test this now. |
My next move is to head back to the original thread and see if this is still visible for those that were participating there. |
@aldo-expensify You want to assign yourself again? |
it could be that that specific response had invalid html, and one browser was doing a better job than the other in fixing it. Can you reproduce this with any other pre-saved response (if we don't find the original one anymore)? Thanks for updating the steps, it is much clearer now |
Interestingly enough, I thought the same. I even deleted the old saved repeatable response and then manually created a new one. But even the new, non-copy/pasted one I created still had the same problem. So it was just super super weird that it still happened despite that. |
Can you send me the response in an email or file? 🙏 |
ProposalProblemThe RenderHTML add the flex property to some element Solutionwe can set an initial flex property to the config so the RenderHTML will use it instead of adding new one
- const defaultViewProps = {style: [styles.alignItemsStart, styles.userSelectText]};
+ const defaultViewProps = {style: [styles.alignItemsStart, styles.userSelectText,styles.flexInherit]}; then add the new App/src/styles/utilities/flex.js Lines 6 to 9 in d0f0dd5
+ flexInherit:{
+ flex: 'inherit'
+ }, Test |
@parasharrajat thoughts on @fedirjh's proposal above? |
@parasharrajat Safari too |
Yeah @fedirjh , Safari is chromium based browser. I have a better proposal. This is happening due to Line 79 in 7044ab2
I traced back this change and it was added by me in #5364. As I mentioned in the proposal it was optional at that time. So I think we can just remove |
@parasharrajat if that fixes it and doesn't break anything else, I would prefer your solution for simplicity. |
let me test this on IOS and safari web. it's working on others (chrome, firefox, android, android chrome). And does not cause the old issue. |
Looking good everywhere. |
Ok so @aldo-expensify are we hiring @parasharrajat for this job? @chiragsalian are you good with this plan? As a reminder, the upwork job is here when we get there: https://www.upwork.com/jobs/~01521563b8fd74ea23. |
I vote for @parasharrajat 's solution, but leaving it up to @chiragsalian since he is the CME |
Yes, I like @parasharrajat solution as well since its simple, and you've worked on this before and it seems to be working fine everywhere. Feel free to create the PR @parasharrajat. |
Invited @parasharrajat to the Upwork job. Then as a more general update, the linked PR has been merged and should reach production in the next day or so. At that point we'll kick off the regression period hold before paying. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.19-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-11-02. 🎊 |
Don't see any regressions at this point, so I will circle back tomorrow for payment. |
Waiting on @parasharrajat to accept the Upwork invite before job can be paid and issue closed. |
@parasharrajat sent you an offer on Upwork. Will pay out as soon as you're able to accept. |
Payment issued! Closing this one out. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
replies+<report_id>@expensify.com
. The<report_id>
can be obtained from a URL of a chat between your account and some other account. The subject of the email can be any.Video of steps reproducing the bug:
Screen.Recording.2022-10-11.at.11.52.42.AM.mov
Expected Result:
Messages should be properly formatted
Actual Result:
HTML formatted messages render incorrectly
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.12-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1663173660551449
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: