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
When replying or forwarding an email body.getAsync() returns an incorrect value #4392
Comments
@bchenhs we are not able to repro the issue on our side. Could you please share a repro video of the issue? |
Hi @anjalitp I've updated the description and sample script to better demonstrate the issue. The missing step in the original description was calling |
Thanks for updating the issue. We are able to repro the issue with body.setAsync call. It seems like body.setAsync call is not replacing the quoted text in the original body, hence the subsequent getAsync call shows the quoted text twice. |
@anjalitp Can you please elaborate on how this looks like expected behaviour for The example on the API documentation site states:
This is also a recent change in behaviour. Prior to a few day ago, it was working as expected and followed the API spec. |
Hi @anjalitp @exextoc, just to add to this report, the symptoms here fully match the other issues linked (#3988 and #4360), where the add-in team was able to confirm there was a regression. Tagging in @ajays-msft in case he can add context as well. |
In OWA, getBody or setBody reflects what can be possible in from the UI. For example, if the messages are grouped by conversation, reply/forward will show quoted text (... which requires user to expand to see the full message). When there is quoted text, get/set body will only get/set the editable content in the email. |
Provide required information needed to triage your issue
Similar symptoms as:
#3988
#4360
item.body.getAsync
returns mismatched and duplicated contents afteritem.body.setAsync
Your Environment
Expected behavior
Appropriately get the value of the mail body for reply/forward emails.
Current behavior
The mail body is incorrect and contains duplicating contents after
item.body.setAsync
.Steps to reproduce
item.body.getAsync
, and sets the same content back withitem.body.setAsync
Link to live example(s)
These are taken from #3988
Javascript
HTML
Provide additional details
elementToProof
which doesn't exist on subsequent getAsync results.The text was updated successfully, but these errors were encountered: