Hover Scrolling lets you interact with the dropdown menus without ever having to click on them. Sounds cool, right?

Normally, this is not a problem, because you can easily see what has been changed because you've got an object selected. But when working with conditional text, the conditional text indicator visibility is a GLOBAL setting, and thus, hover scrolling over it can change your document, even with nothing selected. And if you're not on a page with conditional text. you'd never even know that your document got changed, until you send it to print!

This has been plaguing me for over four years and there is no way to turn it off.

I write a blog article about this and have been documenting it for four years: https://indesignsecrets.com/hover-scrolling-indesign-cc-feature-bug.php

I have made a video about it here: https://youtu.be/5uBI77mothA

InDesign needs to add a preference to our off this setting. It would be so easy! There are already preferences to disable the other annoying features, like Publish Online the new start workspace, and the new document dialog box. You could put it under "Preferences > General."

Adobe, please fix this!

So basically i cant't use InDesign since updating to the new version. Even if it's idle without anything open, it starts to use up all the system memory in macOs Mojave.

This is what happens:
1. Open InDesign
2. Doesn't matter if im working or it's just open
3. After about 5 minutes, there's a system alert of Mojave saying, InDesign is using 550 GB of system memory and there's nothing left to work with.

System:
iMac Pro (macOS Mojave 10.14)
3 GHz Intel Xeon W (10 cores)
64 GB RAM
Radeon Pro Vega 64

It's a new iMac with a new system and it worked before with InDesign CC 2018 without having even seen this system alert. Since i need this software for my work, i installed 2018 to keep using it. But i can't figure out what's wrong with it.

When i drag and drop a Textframe my Screen flickers black for a second - almost every damn time. This happens for me and most of my colleagues and it is horrible to work with.

I feel like it got worse after installing the latest "Tablehead" fix that fixed the disapearing tableheads.

Build 12.1.0.56
OS X El Capitan 10.11.6
iMac (Retina 4K, 21.5", 2015)
3,3 GHz Intel Core i7
16 GB 1867 MHz DDR3
Intel Iris Pro Graphics 6200 1536 MB

2nd Monior is a DELL U2414H, 23,5" at 1800p

This is happening on quite a lot of machines in my Company and also for Persons i know using a 4K Retina iMac. and Really is a pain to work with. - It is NOT visible in a Screenrecording the only option would be to record a Video from my Smartphone if needed...

Thanks!

I'd like to report a bug. Please follow the scenario below:

1. In a single column with lots of text in it, make two columns for a fragment of text

2. In text within the two-column setup, make a footnote. Add several lines of text to the footnote

3. Turn on the "Span Footnotes Across Columns" feature so that footnote ends up in the same group with the footnotes at the bottom of the page rather than below the two-column fragment

4. Expected behaviour: normal editing can be performed after these manipulations

5. Observed behaviour: any text editing after turning on the "Span Footnotes Across Columns" feature becomes lethargic and near impossible. Turning this option off immediately solves the speed issues.

Please log a bug to fix this behaviour.

CC2018, Windows 10, latest update as of 01/18/18, x64 system with 12GB RAM. I often have to close and reopen documents or InDesign itself for shortcuts and some keys to work. There does not seem to be a common cause or specific file(s) that sets it off and it may or may not happen to all open documents if more than one is open. Generally closing the document and reopening it helps, but there have been times where I have to restart the program for anything to work. The issue includes any shortcuts and sometimes keys such as the arrow keys when trying to edge a graphic or text box over. Generally, I am able to type in the file name if I am trying to save my work before I close the program, but there have been times that my keyboard is disabled there as well and I have to save over what I have open, rely on the auto-backup file, or duplicate the file in Explorer and rename it so I don't lose the original file. This has not been an issue in any other programs except InDesign and has only been in the past few weeks. The crashing since the last update has subsided, but this issue has not. I would love to know how to fix this.

InDesign 14.0.1.209, macOS Mojave 10.14.2

When launched and the following conditions hold, InDesign does not seem to have keyboard focus (i.e.., no keyboard shortcuts work):

1. Show ‘Start’ Workspace When No Documents Are Open is unticked.
2. The Control bar is open in the default workspace.
3. The CC Libraries panel is either not in the default workspace or collapsed.

Note that conditions 2 and 3 are met by several of the standard workspace, for example both Advanced and Typography (but not Book, Essentials or Essentials Classic).

If you choose a menu item or click in an input field, the app gains keyboard focus. Otherwise you seem to be able to type endlessly without any discernible effect.

There are multiple listings of the same font in the Find Font menu in CC2019. All information is the same, all applied characters are the same, but there is odd behavior.

--FileA_CC2019_WithDocumentsfontsfolder.png shows double listing of Trade Gothic LT Pro Roman.

--FileA_CC2019_WithoutDocumentfontsfolder.png (when I take away access to Document fonts folder, no other changes), one instance switches to "Regular" instead of "Roman"

--FileA_CC2017_WithDocumentfontsfolder.png shows what happens with I open this file in CC2017 (no double listing)

--FileA_CC2017_WithoutDocumentfontsfolder.png (Document fonts folder hidden) shows what happens with I open this file in CC2017 (no double listing)

I process large volumes of files; this is not an isolated incident nor a corrupted file. Packaging results in InDesign only grabbing the *single* correct font file, so that isn't broken. This behavior with Find Font is seemingly new to CC2019 (I'm working on 14.0.2). The multiple listing of same font, variation of font name when fonts enabled/disabled, and Find Font showing fonts missing that aren't because of what seems to be a name issue in Find Font. Has something changed in the way that InDesign reads fonts/accesses Document fonts folders?

I am using InDesign CC 2019 14.01 x64.

Once a stroke weight has been added, if you then change the stroke weight back to zero, then when you export to pdf the pdf will have a stroke weight added to the text, even though the indesign document looks correct. It may not have the original amount of weight that was added, but it will definitely have what looks to be around a .2 weight added.

However, if you were to start a new document, then add stroke weight, then click edit - undo stroke weight, then it would export to pdf just fine. However if you saved the document with the stroke weight added, and then re-opened and changed the weight to zero, then when you export to pdf it will have a stroke weight still added (around .2, same as above).

So once you have saved a document with the stroke weight added, then no matter what you do the document will not print without the added weight.

If ANYBODY has any idea how to fix this then PLEASE let me know :) I was on chat for 4 hours but no luck. I'm really not trying to redo this 600 page book.

The inclusion of ~F in a character class invalidates grep expressions in endnotes.

InDesign version: 14.0.2.324 (with the GREP fix installed)

Steps to reproduce:

1. Open the attached document. It contains a single page with text and an endnote.
2. In the GREP tab of the Find/What window, enter the following GREP expression:

\d[^.,;~F]+

And target the document. The expression matches from a digit up to the next period, comma, semicolon, or footnote marker.

Expected result: The expression should match some text in the main text and in the endnote.
Actual Result: The expression does not match anything in the endnote.

To show that it's ~F that's the problem, use this expression:

\d[^.,;]+

It matches in the main text and in the footnote, as expected.