InDesign 15.0.1, Mac
After placing item from libary inline into the text, tab and return keys have no effect until the mouse is clicked somewhere in the text.

A placed graphic will show onscreen and in graphic exports like PNG and JPG outside the stroke when the stroke is aligned to the inside of the frame. InDesign 2020 and earlier. To reproduce: place a graphic, add a stroke to the frame, align stroke to inside, export the page to jpg or png. A thin portion of the image is visible outside the stroke. Obviously, this is most noticeable when the stroke is thick and white.

A placed graphic will show onscreen and in graphic exports like PNG and JPG outside the stroke when the stroke is aligned to the inside of the frame. InDesign 2020 and earlier. To reproduce: place a graphic, add a stroke to the frame, align stroke to inside, export the page to jpg or png. A thin portion of the image is visible outside the stroke. Obviously, this is most noticeable when the stroke is thick and white.

Back to how it was.

ID Version 15.0.1 (Windows)
IL Version 24.0.2 (Windows)

I placed an Illustrator document in my indd file. When I change something in the Illustrator file, ID recognizes this with the yellow sign. If I click on this ID should refreshes the link, but instead nothing happened. Also if I try to relink the file in the Links menu nothing happened despite the yellow sign disappears.

I've been selecting objects and exporting them as 72 / 96ppi jpegs. Whenever I inspect these files, there's a small white border added to the top and bottom. It's bizarre and i'm at a loss for why this would happen.

Indesign won't 'reveal in Bridge' if the file is in a business shared Dropbox folder

When selecting an image inside a frame using the A shortcut, or the white arrow, the rotating arrows (that should appear when hovering over the corners of that image) don't show up. It works fine when using the Content Grabber and the black arrow.

InDesign 15.0.1

The Place command now fails in Applescript, following an upgrade to Catalina.
The "Image Catalog" sample script also fails to place the images in the same manner. Image placement fails with an error 1708, <<the file string>> doesn't understand the "place" message.

I've placed a bitmap on my page. When scaling it with the scaling tool and the proportion lock engaged, proportions aren't maintained.

Ever since I updated to the latest InDesign (InDesign 15.0.1), the bounding box is always on the outside of the stroke so instead of objects snapping to the box they are snapping to the outside of the stroke.

InDesign 2020 v 15.0.1, Mac OS Catalina. When opening legacy versions of indd or idml documents within packaged folders, images flash/display briefly, then most if not all, disappear. The only solution seems t be to re-link each graphic individually.

Since the most recent update, I can no longer export ID file to jpg or png. The files just shows as zero bytes. I am able to save as pdf and then save as image. But need to be able to export to jpg and png. Please fix. Thanks

InDesign does not keep masks that are embedded in the SVG. It ungroups them, causing hidden parts of the SVG to display.

Example: I have a vector logo placed on a specifically sized artboard within Illustrator that has designated safety space around. the artwork, however InDesign adjusts the frame to fit the content within that dartboard instead of the artboard itself.

When placing an image from Illustrator (like an .ai or .eps) and rotating it 270 degrees will turn round corners into sharp corners. this only happens with 270 degrees rotation not with 269 or 271. Not even with 270,1 or 269,9. This was on InDesign CC 2020 version 15.0.

Although all my images and graphics are linked correctly and there are no errors, when opening a file, they are appearing as grey boxes. Some images are working but most of them are not. Also PDF export is therefore not working (error message attached). It doesn't matter which file type my links are as it's happening to all kinds of them (mostly TIFF and AI). Perhaps worth mentioning that this problem didn't occur in ID2019.