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.

InDesign sometimes, seemingly randomly, replaces pairs such as hn, il, io, sy, ek, etc. with completely wrong glyph, such as accented Y, U, etc., when regular Ligature setting is applied. This has been a problem since CS5 and we recently had it occur in CC2015, so it is still there. Affected fonts have been many over the years, including licensed Adobe fonts. Fonts can be Open Type or PostScript. Language setting can be English US, UK, or seemingly anything else. The only thing that works to avoid it is to turn off Ligatures which is generally unacceptable, so the only workaround is a targeted GREP style to apply ligatures to only the pairs that should have them for that file. This is a long-standing problem which has been reported in forums various times and needs to be addressed. There is no sure fire way to reproduce the bug. Only thing that sometimes works is to brute force load/unload fonts until the problem occurs. It seems that once the problem occurs the first time it may then become more frequent on that computer. I know someone who has even seen the effects of this problem in printed material (i.e., in a book they were reading).

File Created in Indesign CC 2017

I have created a test interactive document with links to product DG012 on our company website.

https://indd.adobe.com/view/da74b2d3-46b2-40cf-99e2-8201ddc6248a

When the link is clicked from publish online it opens the page but seems to disable all scripts that run on the website. e.g. search field and add to cart no longer functions on that page.

The website itself functions correctly if you navigate to the link manually ( http://www.lockhart.co.uk/Table-Service-and-Buffet/Buffet-Display/Display-Stands/Rafters-F usion-1-2-Board~p~DG012 ).

Interestingly in safari the add to cart button functions but the search field is still disabled.

On closer inspection it seems to be an iframe issue -
If I go into chrome developer tools i get the following errors:

The key "target-densitydpi" is not supported.

cast_sender.js:76 Uncaught DOMException: Failed to construct 'PresentationRequest': The document is sandboxed and lacks the 'allow-presentation' flag.
at V.P (chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/cast_sender.js:76:87)
at Object.chrome.cast.P (chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/cast_sender.js:91:165)
at g.VI.g.h.init (https://www.youtube.com/yts/jsbin/player-vflgfcuiz/en_US/base.js:5981:519)
at xAa (https://www.youtube.com/yts/jsbin/player-vflgfcuiz/en_US/remote.js:34:60)
at yAa (https://www.youtube.com/yts/jsbin/player-vflgfcuiz/en_US/remote.js:35:8)
at window.chrome.window.chrome.cast.window.chrome.cast.isAvailable.window.__onGCastApiAvaila ble (https://www.youtube.com/yts/jsbin/player-vflgfcuiz/en_US/remote.js:35:374)
at chrome.cast.ea (chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/cast_sender.js:94:152)

Rafters-Fusion-1-2-Board~p~DG012:1 Blocked form submission to '/cart/add' because the form's frame is sandboxed and the 'allow-forms' permission is not set.

Rafters-Fusion-1-2-Board~p~DG012:1 Blocked form submission to '/search' because the form's frame is sandboxed and the 'allow-forms' permission is not set.

When clicked the link opens in a new window so I am not sure how to go about editing the code behind the sandbox element.

Any advice would be greatly appreciated.

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 am working in Adobe InDesign CC 2019 14.0.1. When I have a manuscript already flowed into my document and try to adjust the margins on the master page with Adjust Layout enabled, when the new margins are applied to the document, all the existing text boxes "disappear." From what I can tell, they have been resized down to an infinitely small point in the middle of the spread. Obviously, this is not useful. I used to be able to adjust the margins across an entire book-length document in one go with layout adjustment, and the text on every page would be re-fit to the new margins. The attached screenshots show the before and after on a spread (you can see the tiny text box in the middle in the after).

Am I missing a step here, or is this a bug?

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.

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.

If I try to duplicate an object to another page, across the pasteboard border, by holding the Alt key and dragging with mouse, the object only moves there. If I want to duplicate an object to another page, I have to first duplicate it on the same page and then move it to another page.

However, as that is unintuitive, I still constantly try to duplicate an object across the page border, leading me to undo back after I find out the object didn't actually duplicate, but instead I have moved the original object (and oftentimes edited it a lot already).

As I find no particular reason why the duplicate shouldn't work across two pages, I believe this is a bug, or at least an oversight.

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.

VERSIONS
Windows 7, CC 2015.4 and CC 2017.0
Windows 10, CC 2015.4 and CC 2017.0
macOS 10.12, CC 2015.4
even CS6 versions are affected...

- - - - - - - - - - - - - - - - - - - - -

STEPS TO REPRODUCE
1. Create an InDesign document with several pages
2. Define the text frame options with two columns
3. Link all frames and fill with placeholder text
4. Create a new paragraph style with the option "span columns" (e.g. title)
5. Define several parts of the layout with the new paragraph style
6. Edit some text near the paragraph style
--> the performance while typing is very very bad!!!

- - - - - - - - - - - - - - - - - - - - -

EXPECTED RESULT
InDesign and InCopy should still be usable when a layout file was built using either "span column" or "split column" (e.g. using a paragraph style > "Span Columns").

- - - - - - - - - - - - - - - - - - - - -

ACTUAL RESULT
Very bad performance - working is NOT possible anymore

I have reported a variation of this—back with CS6—but it seems not to have been fixed. I assume it's a bug, but if someone can enlighten me about what I might be doing wrong and how I can fix this, I'd appreciate it.

I often work on books that include Arabic and Hebrew words and phrases in the middle of English text. They only way to get the Arabic ligatures to form is to use one of the World Ready composers. When I do that, though, the kerning around some English characters often—but not always—is affected. I have tried turning on and off various settings—justification settings, kashidas, etc.—and their effect seems to be random. Sometimes the changes fix the problem until the page redraws, sometimes the errant kerning is corrected in one location but shows up in another location, sometimes nothing happens at all. I'm attaching two screen captures of a book that I have in production now with the word "economics" selected in each. In the shot with the World-Ready Paragraph Composer active, you can see the extra kerning between the "e" and the "c." In the shot with the WRPC deactivated, the word looks as it should.

Is this a bug? If not, what am I doing wrong? If it is, when might we expect a fix. Unfortunately, I have a deadline on this project now and can't see any reasonable way to fix this. Thanks for considering this problem.