Drawing a box, moving it around etc is now a kind of laggy. Moves but slow and kind of stuttering.

The GUI overall, menus etc, behaves a bit slower as well. Not much but not as quick and responsive at it was in Sierra.

Have tried de-activating GPU but that has no difference at all.

I have the latest version, 14.0.2.
Updated to Mojave because the Adobe chat support suggested that would help out some other issues I have had.
One reason was that command + new shortcut stopped working. And now it stopped working again...

Same thing happens in Illustrator so it seems to be something of a Mojave comparability?

Other software (non-adobe) seems to be just fine though.

Using a Imac 2017, i7, 32 ram, 1 tb ssd.

I'm a big fan of technology but in Adobes case it seems as going back a few years actually was better having a lot fewer issues in the software.
(For me it all started with the bloody CC subscription thing.)

When you have a document with multiple languages and the main language isn't available in InDesign's presets, ie the document is mainly in Kirundi or Samoan and there are some English phrases, a user should be able to select 'No language' from the style's advanced options. Instead, 'No language' will export as EN and the tag in the PDF will have EN listed as the language in the tag's properties. This is problematic because the tag's language will override the document's language properties. This is a clear failure of WCAG SC 3.1.2 (language of parts).

A screen reader won't be able to read the document because the English language tag properties will override everything.

Fixing this will ensure PDFs can be accessible to people who use screen readers in languages other than InDesign's presets.

SITUATION
We migrated our old Active Directory "OldAD.ads" to a complete new one "NewAD.ads"
We use InDesign CC2019 (latest Version)

All out file-shares are mounted on client computers with Microsoft DFS-Links.
- Old DFS-Link: \\OldAD\DFS\OldShare - The DFS-Links points to a share on our old fileserver: \\OldFileServer.OldAD.ads\Share_OLD
All shares on the old fileserver are closed, so the DFS-Links have no destination but are still "available".

- New DFS-Link: \\NewAD\DFS\NewShare - The DFS-Links points to a share on our new fileserver: \\NewFileServer.NewAD.ads\Share_NEW

Both fileservers hold "their" (Active Directory based) DFS-structure.

Of course, all users open their files on the new fileserver, shares are mounted via the new DFS-structure.

THE REAL STRANGE ERROR
As long as the old fileserver and old Domaincontroller are up, InDesign acts as expected: We open an old document, the windows "missing links in document" comes up, we fix the broken links, the document opens, everything is fine.

BUT when I shut down the fileserver and the last domaincontroller, the following happens: We open an old document (containing links to documents, that were on shares mounted via the old DFS on our old fileserver), InDesign freezes and the mouse pointer circles. I waited up to 30 minutes, nothing happened. And now comes the really strange thing: When I unplug the network cable (no joke), the "missing links in document"-windows comes to front and I can fix the broken links after plugging in the cable again.
When I turn on the old fileserver and domaincontroller again, everything works fine again.

I can reproduce this error on all our 4 InDesign-workstations. The error only appears when the broken path contains a DFS-Link and the link is not available any more - no matter if the "real" share behind the link is available or not.
The InDesign option "Ignore missing links when opening a document" does not affect the error, it happens when the option is set or not.

1) Version of Adobe InDesign...

This bug has plagued InDesign from at least CS 6.2 all the way to the current CC2019 version. I filed a bug report in 2017, and @Abhinav Kaushik claimed the bug was solved, but this was straight-up NOT TRUE. The bug persists to the present software.

2) Follow these steps to replicate the bug:

Create a shape, let's say a circle, and then copy this circle and paste it in a separate layer directly over the top of the first. To better see the effects of the bug, make the fill of the top circle red, and the bottom blue. At this point, the bottom blue circle is completely hidden by the red circle above it. Now put a 4pt stroke with an outside alignment on the bottom blue circle. The blue circle is still hidden, and now it appears as if the red circle on top has a stroke. Before making any changes to the shapes, make sure the Dimensions Include Stroke Weight and Adjust Stroke Weight when Scaling are DESELECTED in the Transform panel options. Make sure to have the Info palette visible so you can read the starting and ending measurements. Using the Selection tool, select BOTH circles together, and then pull on any corner to enlarge the two shapes together.

3) EXPECTED RESULT

The two shapes should scale together. They start with the equal measurements in the Info palettes, and once scaled, the shapes and the measurements should still read as being equal (albeit larger) sizes.

4) THE ACTUAL RESULT

The two shapes are DIFFERENT sizes after scaling. Remember that Dimensions Include Stroke Weight was deselected, so the stroke shouldn’t have any effect on the shape size, and yet, the bottom shape is slightly bigger than the top. The blue circle is now clearly visible and peeking out from beneath the red circle. The Info palette confirms this - the final shape sizes are different. The following are images that illustrate the bug:

If you use an object style with unequal inset spacing and apply it to a text frame, the unequal spacing is ignore and made uniform.

Steps to recreate:
1. Create an Object Style
2. Go to 'Text Frame General Options' for that style
3. Set unequal values for 'Inset Spacing'
4. Go to 'Stroke & Corner Cptions'
5. In 'Corner Options' set 'Rounded'
6. Create a Text Frame
7. Fill Text Frame with placeholder text
8. Apply Object Style to Text Frame

Result: unequal inset spacing is ignored.

If you apply unequal inset spacing manually there are no problems — unless you apply a corner rounding greater than 6mm, at which point unequal spacing is ignored.

I've attached an InDesign file which demonstrates all of this.

As an addendum to this: object styles seem quite buggy generally. For example, if you set an initial paragraph style and select 'apply next' then later edit the paragraph style, the text frame doesn't always display the changes.

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.