Highlighting Tool Won't Stay On Word For Mac 2011
Jul 17, 2009 Version: 2008 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel. I received a document in which a lot of text had been highlighted. I need to remove it but when I select the text and on the Format Palette select None on the shading icon or click on File>Undo Highlighting. > I can't remove the highlighting from certain sections in my word document - > I've tried selecting and highlighting all the text and then removing the > highlighting, but these sections stay yellow. Version: 2008 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel. I received a document in which a lot of text had been highlighted. I need to remove it but when I select the text and on the Format Palette select None on the shading icon or click on File>Undo Highlighting, nothing happens.
- In older versions and in Word for the Mac, you hit “Merge Documents” on the Tools menu. In older Word, it’s sometimes hard to figure out which doc the software will treat as the original and which as the revised version. But that won’t help you if you sign the wrong terms. You can avoid the problem by running your own.
- Tab not working on Microsoft Word 2011. Turn on the highlight field code preferences in the same preference pane. Share improve this answer. Edited Feb 28 '15 at 0:38. 13.4k 3 25 47. Curve text in Microsoft Word for Mac 2011. Microsoft Word on MacBook Pro: Tab problems.
- Highlight the row in excel mac 2011 when a cell has a specific word. Ask Question. Another small question. If I have 'Student, PostDoc' the formula won't highlight Student or the row. Step 6 - Highlight desired Cells and take note of the current cell. (D3) Step 7 - Use formula.
The text cursor, or caret, is normally in the visible form in applications at the start of its display cycle. It then goes to the flashing sequence once you stop moving it with arrow keys or typing. However, in Word 2011 I'm constantly frustrated because the cursor disappears, or defaults to the invisible state of the flashing sequence, while I'm typing or moving it. This makes it painfully difficult to edit text without using the mouse. As I write this post and keep going back to word I'm noticing that it seems erratic as to what behavior it's acting. I think that it stays in whichever state it was last in, which 50% of the time is invisible.
I've since changed the blink rate to 200ms via changing the default in Word's plist file. This helps a little in my frustration, but the behavior really needs fixed.
Update 2014-09-02
It doesn't appear to be a problem on documents created locally. It seems to be an issue with documents I've got from elsewhere, quite possibly from other operating systems.
5 Answers
I noticed the problem when I tried working on a document I created working on a PC using Windows 8. So your theory on operating systems may be valid.
I opened a blank document and copied the content out of the dysfunctional one and voila.. my cursor came back.
In my case, the copy/paste of the document did not work. But after a bunch of tries, I found a workaround:
Move the mouse pointer outside the Table area!
Yeah I know it sounds weird. But if I use the keyboard arrows to move the cursor in a table cell while the mouse pointer is located inside that table, the cursor will annoyingly start disappearing.
This seems related to the Move icon appearing in the upper-left corner of the table when you move in the mouse pointer, which keeps switching on/off when you use the keyboard.
BTW I'm using Word 2011 v14.4.8 (latest as of now).
If it's not affecting locally created documents, could it have to do with Compatibility mode? Try re-saving the doc in the latest native .docx format and re-opening.
I had the same issue but it was solved easy. You are probably using a .docx extension if you save as your file to a .doc format the issue will go. I did not test but i think it will work if your original file is a .doc format and you save it as a .docx.
My screw up appeared to be from copy from gmail into word doc for mac yosemite, google search that worked was: copy the faulty doc into a new 'local' file. fixed it.
bmike