-
Notifications
You must be signed in to change notification settings - Fork 94
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
Word add-ins steal focus from document #316
Comments
@fergiemcdowall thanks for reaching out about this. @JuaneloJuanelo are you able to provide input on this issue? (Please let me know if this should be directed to someone else.) |
as correctly answered on stack this is not supported today. @fergiemcdowall if this is a pressing issue please open (or upvote) a new request in our uservoice channel https://officespdev.uservoice.com/ |
I am experiencing the same issue today, three years later in December 2021. It really disturbs the flow! |
Do you know if there is a plan to support that? |
Same here, will this issue never be approached? |
is this issue is going to be adressed or not? |
@fergiemcdowall @JuaneloJuanelo an update would be highly appreciated as this heavily disturbes UX. |
After performing an action in an add-in, there seems to be no way to send focus back to the main document. The user is forced to manually click on the document.
(related: https://stackoverflow.com/questions/39888050/how-to-send-back-ms-word-cursor-focus-on-current-document-after-click-in-task-pa)
Expected Behavior
I would expect there to be some way for the add-in to assign focus back to the document
Current Behavior
Currently this works as expected on Word Online but doesn't work on latest versions of Word for Windows or Mac
Steps to Reproduce
Context
I am a developer for SmartLawyer Writer, a commercial lawtech add-in in the Norwegian add-in Store. Our users are legal professionals who write long documents. This problem means that our add-in (and other add-ins) can be seen as breaking a user's "flow" when they are writing.
Your Environment
This bug seems to affect recent versions of Word on Windows and Mac, but works as intended on Word Online in all browsers.
The text was updated successfully, but these errors were encountered: