Forum Discussion
Holy cow yes!!
This is driving me mad. Microsoft, spell check has been in right-click context menu for DECADES, and not just in word but EVERYWHERE.
There is NO REASON to move the spell check menu to left click, in fact, there are many reasons against it!
- It has been in the right click menu with no issues for decades
- What if I want to place my cursor inside the word to edit it without a menu coming up
- There is no common software that I am aware of that brings up a context menu with a left click
- All your current desktop and online applications have spell check in the right click menu, meaning word online experience is FRACTURED. As I'm typing this I am correcting spelling with right click. When I move to a different program it will be right click, when I go to word on desktop it will be right click.
- This change isn't intuitive, it doesn't improve anything, it doesn't solve an existing problem, it doesn't make the users life easier, it doesn't make the IT managers life better, it causes headache, confusion, frustration, and an overall distaste for your products.
This is not some woke change like Apple removing the headphone jack. This is not for the betterment of future iterations of Word. This is not even change for the sake of change, it LITERALLY WOULD HAVE COST YOU NOTHING TO NOT CHANGE THIS. In fact, it probably cost you thousands to change this because now you have to moderate all the complaints from your users, pay someone to make the change for no reason, pay someone to QA the change (although no one probably did because WTF would they say, "yeah I think this is a great change." without using it to try and type a document for longer than 10 seconds without loosing their mind because of the missing context menu and the little popup in their face every time), you have to pay to host the content of all the complaints, and I can almost guarantee (unless you foolishly double-down on this hideous oversigt/idiotic design decision) that you will be paying someone to change it back to the way it was.
Fire the designer that came up with this change. Fire the Project Manager who decided it was even remotely a good idea to toy with the idea and throw it up on the project board, fire the QA team who didn't stand up for their honor and tell you this was an awful change, and fire the dev that pushed this garbage to production. Swallow your pride, this was a bad change, we all make mistakes.
As the old proverb goes, "no need to reinvent the wheel and turn it into a cube."