Random highlight color when creating comments

I just noticed that when I create a comment, in whatever color I choose to make it, the actual text in the Editor is given a random highlight color. In this case, it keeps marking my commented text with a blue highlight. I say it’s “random” because I have no idea how it chose blue in the first place.

Note: This only happens in Composition mode, not when adding comments to the actual Editor window.

Here’s the Console app code I copied. Not exactly sure which one denotes the Scrivener action.:

default 14:03:14.039872 -0600 Scrivener Read (Async) options: 80001 – URL: – purposeID: 54DAB032-1BAE-4BF3-B430-C336B26C24AE – claimID: E78956D3-7206-41C8-9762-5F173ECAC7F2
default 14:03:14.049265 -0600 Scrivener Claim E78956D3-7206-41C8-9762-5F173ECAC7F2 granted in client
default 14:03:14.049321 -0600 Scrivener Claim E78956D3-7206-41C8-9762-5F173ECAC7F2 invoked in client
default 14:03:15.015987 -0600 Scrivener Read (Async) options: 80001 – URL: – purposeID: C1E0AB96-F1C2-4D1F-9F29-1552422321F3 – claimID: 5D5805B8-8244-43F3-851F-98D59BA4569A
default 14:03:15.020513 -0600 Scrivener Claim 5D5805B8-8244-43F3-851F-98D59BA4569A granted in client
default 14:03:15.020542 -0600 Scrivener Claim 5D5805B8-8244-43F3-851F-98D59BA4569A invoked in client
default 14:03:24.331246 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.331565 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.332097 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.332614 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.335396 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.335633 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.335794 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.335946 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.336083 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.336212 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.336337 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:24.336464 -0600 Scrivener Making presenter AF5C2F6B-3B9A-46C1-AB0F-54AC3A9D7360 observe change
default 14:03:29.973373 -0600 Scrivener 27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 163 vs 580, 513,

Update: Just noticed this is doing the same thing when I try to search/find words in my manuscript using the Command+F option. Only now, it’s changing to green.
Screen Shot 2019-03-01 at 1.38.28 PM.jpg

I managed to get this to happen by:

  1. Switching to Composition Mode
  2. changing the colour of the base text
  3. leaving the colour picker open
  4. creating an inspector comment.

The comment picked up the colour of the text. It only happened once; I could not reproduce it.

OTOH, once a comment has had its colour changed, that colour will “stick” so that any newer comments created will have that colour until the user changes the comment colour again. This last is expected behaviour, per the manual and my past experience :slight_smile:

The colour picker on macOS is hugely - and annoyingly - sensitive. Whenever you click in coloured text in the editor, it sends a “colour changed” message to the colour picker, which in turn sends a “colour changed” message back to anything else that might be listening. There’s all sorts of spaghetti code in Scrivener just to try to avoid Apple’s over-zealous colour change messages. It sounds as though that is what is happening here. The best way of avoiding such issues is to close the colour picker when you’ve finished using it.

All the best,
Keith