-
Notifications
You must be signed in to change notification settings - Fork 57
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
Outlook converts spaces to plus signs (with workaround) #20
Comments
Hey, I found this issue too, you can encode spaces using new line ( |
I've had issues with using It also appears to work in the title, whereas |
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 |
Good catch, looks good for strings with spaces encoded 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. |
For line breaks Im finding |
Feels like this 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.
The text was updated successfully, but these errors were encountered: