Open jerry-knight opened 4 years ago
Hey, I found this issue too, you can encode spaces using new line (%0A
) and then use <br/>
for any new lines. Not sure if it is better than your solution but it might be useful 👍
I've had issues with using <br />
, as the message gets truncated after it. However, using the HTML entity for a space ( 
, or %26%2332;
in the URL) does appear to work.
It also appears to work in the title, whereas %0A
didn't for me.
I've had issues with using
<br />
, as the message gets truncated after it. However, using the HTML entity for a space ( 
, or%26%2332;
in the URL) does appear to work.It also appears to work in the title, whereas
%0A
didn't for me.
I've verified that this works in the title and body. It doesn't appear to work in the location, but I still think this is a better solution overall than thin spaces. There's no telling how non-standard spaces will affect other Outlook features, like indexing, searching, sharing, etc. I stopped my thin space testing when it looked right in the edit page and calendar view.
Thanks for this solution.
It seems that drop rru=addevent
could fix the issue. Not sure if there are any other side effects.
Good catch, looks good for strings with spaces encoded as %20
(i.e. not as +
)
The combination of removing rru=addevent and encoding spaces as %20 works for me.
Removing rru=addevent and %20 didnt work for me, issue only occurs on first redirect after login though, subsequent loads if already logged in are ok. %0A
worked for me in all cases
For line breaks Im finding <br>
is working well instead of <br/>
Feels like this https://outlook.live.com/calendar/0/deeplink/compose
link is broken again?
Maybe this is tapping in at too deep a level and it prone to break?
The OWA level seems to work still
In Chrome and Firefox, when creating Outlook calendar events using a URL like your example:
https://outlook.live.com/calendar/0/deeplink/compose?path=/calendar/action/compose&rru=addevent&startdt=2020-12-31T19:30:00Z&enddt=2020-12-31T22:30:00Z&subject=Birthday&body=With%20clowns%20and%20stuff&location=North%20Pole
Outlook converts all spaces to plus signs in the subject and body. No amount of encoding the spaces in the URL (%20 vs +) makes any difference.
The only workaround I've found is to convert spaces to thin space. The URL encoding is %E2%80%89, and from my testing, Outlook properly renders the thin spaces. No telling whether it affects other Outlook functions, but it's better than plus signs everywhere.
Additional note: I haven't done extensive browser testing, only Chrome and Firefox. I'm not sure if this issue is browser-dependent.