If I place an image and then try to move it within the bounding box, the opacity appears to change to around 50%. However, the opacity is still set to 100%. I can correct it by hitting Undo which reverts the image back to normal. From what I can tell, it is only a visual bug. Exporting the image doesn't show the change in opacity.

I haven't been able to reproduce this issue consistently but would say it happens around 80% of the time I try to move an image. Another interesting thing is that if the issue happens and I duplicate the image and change it's opacity, the original image reverts to normal again.

The Fonts folder in the InDesign 2019 application folder no longer follows symlinks, as previous versions did.

I prefer to keep my InDesign fonts separate from my system fonts, and in previous versions placed a symlink to my font folder in the InDesign application folder, titled "Fonts." InDesign would follow that link, and I would have access to all of my fonts within InDesign, without needing to install them user- or system-wide.

In InDesign 2019, no symlinks are followed - not on the top level, and not inside the folder either. (Tested by symlinking one font or one folder inside a new Fonts folder.)

One description of the method: https://glyphsapp.com/tutorials/testing-your-fonts-in-adobe-apps
Thread where others comment on this: https://forum.glyphsapp.com/t/adobe-fonts-folder-for-indesign-cc-2019/9971

Embedded Publish Online pages do not behave properly (i.e., go to full screen mode) in the latest release of Firefox 62.0.3 on Mac.

Please go to these two websites and click on the embedded document. It will attempt to go to full screen, but the cover only is jammed in the upper left corner of the screen. You can't navigate or do anything to fix that I've found. This is a serious problem, as many people have embedded Publish Online pages in their websites.

http://www.andreanienhaus.de/
http://www.atlasdergisi.com/dijital/yaban-karacadag.html

Could someone else check this with Firefox and let me know the result?

And also please advise with any workaround.

Thank you.

InDesign Version: Adobe InDesign CC 13.0.1
Operating System: macOS High Sierra version 10.13.2
Computer: MacBook Pro (Retina, 15-inch, Mid 2015)

Steps to reproduce the issue:
1. Create a new document in InDesign with at least 3 pages.
2. Make a textbox on one of the pages (e.g. page 1) and fill it with some text.
3. Resize the textbox so that some text overset and preflight shows 1 error - overflowing text.
4. Save and close the document
5. Create a new InDesign document
6. Place the InDesign file with the overflowing textbox in the new InDesign document (NOTE: You need to place the page which actually has the overflowing text). You should get an error message that the document you want to place is containing overflowing text. Click OK.
7. Alt+Double Click / Opt+Double Click on the placed document in order to edit it.
8. Do some edits in the document, e.g. duplicate the textbox with the overflowing text by holding ALT while moving it. Make sure that you still have overset text in the document.
9. Save the document, and close it by clicking CMD+W or File->Close. This should automatically lead you back to the document where you placed the document, and InDesign should try to automatically update the placed document with the new content.

Expected result:
InDesign should update the contents of the placed InDesign document, and not crash, regardless of whether the placed InDesign document contains overset text or not.

Actual result:
In my case, InDesign crashes at the end of step 9 when trying to update the placed document containing overset text. I have attached a screenshot, in addition to the crash reports generated by Apple/Adobe at this time. InDesign shows the following error message (translated from Norwegian to English): "Error: Adobe InDesign is exiting. A serious error occured. Restart InDesign to restore work in any InDesign-documents that isn't archived." It also shows a dialog box which warns you about overset text on pages in the placed document.

Extra notes and comments:
If InDesign didn't crash in step 9, you can try to go to the "Links" panel and update the link to the placed document, if it didn't update automatically. In general you should also try placing and updating InDesign documents containing overset text into another InDesign document, and this error should occur eventually.

In my experience InDesign crashes very often due to this error when using a workflow which requires mounting other InDesign documents, which might contain overset text accidentally. In the workflow that we use, this error is very devastating leading to InDesign crashing up to several times per day (or per hour) in certain periods.

The error most consistently occurs when doing some changes in a document containing overset text, and then updating it in InDesign, as described in the steps to reproduce the error. However, the error has also occured when placing the document, not just while updating it.

I have also experienced that this error occurs even when there just are some extra lines at the end of the textbox, so that text technically overflows, but no preflight error appears because the overflowing text is just empty lines/paragraphs. This makes the bug extra difficult to avoid, because the overflowing text could be in any textbox in the document, even though no error is showed.

This error has occured consistently over several InDesign and OS versions, at least for several years, probably since the feature to place another InDesign document was introduced.

InDesign cuts off effects on PDF Exports if they get too large. (Also to mention... menues look different fot Font or Object Effects... someone realigned one of them and forgot the others.)

Version of Adobe InDesign, InCopy or InDesign Server: CC 2017.1 with Tablefix
Steps to reproduce the issues: Create a new Document that's wide enough e.g. 5000mm (happend to us on a big Banner) – Write Text - Use Effect "Bevel" - Export to PDF and watch it fail.

Expected result: A Text with the applied effect

Actual result: The Effect gets cut off (we almost printed a job like this...)

Test file, screenshot, video or GIF capturing the issue (optional): see Attachments