Mac running 10.14.4
InDesign 14.0.2 working color space is sRGB
Image placed has embedded profile of sRGB
Native InDesign content created with color numbers matching those in image
Exported to ePub

Result: RGB color numbers of native object correctly match those of original sRGB numbers BUT those of the placed image have changed. The numbers indicate they have been converted to the active display ICC profile!
Happens whether object export options on image are set to JPEG or PNG.

I confirmed this by changing the monitor profile in System Preferences and relaunching InDesign. the exported image's color numbers changed to the color numbers of the new monitor profile.

Expected result: all RGB content should be converted to sRGB or, less optimally, all RGB color numbers could remain the same.

InDesign 14.0.2 and Acrobat Continuous 2019.10.20099

This issue is about the behavior and appearance of interactive check boxes in documents that have been exported to Interactive PDFs.

There is a difference in the way that check boxes created in InDesign behave and appear versus those created in Acrobat Pro. The Acrobat Pro Forms preferences are involved in this difference.

When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is selected, check boxes created in InDesign behave and appear in the following manner.

When a check box is made active, it first appears the same as the check box that was created in InDesign. When you tab to or select another check box, or when you save the selection in the PDF, the appearance of the check box reverts to a default generic check mark.

When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is not selected, check boxes created in InDesign behave and appear in the following manner.

When a check box is made active, it first appears the same as the check box that was created in InDesign and remains as such.

This degrades the purpose of using the highlighted fields, which is to call attention to fields that need to be filled.

When the check boxes are created in Acrobat, it makes no difference in appearance or behavior if the “Show border hover color for fields” is selected or not. They always appear as the checkbox style you have chosen to use. They do not revert to a generic check mark.

This is the way that custom check boxes created in InDesign should behave. Thus, they would allow the use of a highlighted field without the appearance of the “selected” custom graphic changing to an unwanted generic graphic.

Please refer to the InDesign Forums message at this link for examples:

https://forums.adobe.com/message/11063952#11063952

InDesign 14.0.2 and Acrobat Continuous 2019.10.20099

This issue is about the behavior and appearance of interactive check boxes in documents that have been exported to Interactive PDFs.

There is a difference in the way that check boxes created in InDesign behave and appear versus those created in Acrobat Pro. The Acrobat Pro Forms preferences are involved in this difference.

When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is selected, check boxes created in InDesign behave and appear in the following manner.

When a check box is made active, it first appears the same as the check box that was created in InDesign. When you tab to or select another check box, or when you save the selection in the PDF, the appearance of the check box reverts to a default generic check mark.

When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is not selected, check boxes created in InDesign behave and appear in the following manner.

When a check box is made active, it first appears the same as the check box that was created in InDesign and remains as such.

This degrades the purpose of using the highlighted fields, which is to call attention to fields that need to be filled.

When the check boxes are created in Acrobat, it makes no difference in appearance or behavior if the “Show border hover color for fields” is selected or not. They always appear as the checkbox style you have chosen to use. They do not revert to a generic check mark.

This is the way that custom check boxes created in InDesign should behave. Thus, they would allow the use of a highlighted field without the appearance of the “selected” custom graphic changing to an unwanted generic graphic.

Please refer to the InDesign Forums message at this link for examples:

https://forums.adobe.com/message/11063952#11063952

Generic check mark reappears in PDF check box after exporting to Acrobat Pro

InDesign 14.0.2 and Acrobat Continuous 2019.10.20099

This issue is about the behavior and appearance of interactive check boxes in documents that have been exported to Interactive PDFs.

There is a difference in the way that check boxes created in InDesign behave and appear versus those created in Acrobat Pro. The Acrobat Pro Forms preferences are involved in this difference.

When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is selected, check boxes created in InDesign behave and appear in the following manner.

When a check box is made active, it first appears the same as the check box that was created in InDesign. When you tab to or select another check box, or when you save the selection in the PDF, the appearance of the check box reverts to a default generic check mark.

When, in Acrobat Pro Forms Preferences, under Highlight Color, the “Show border hover color for fields” option is not selected, check boxes created in InDesign behave and appear in the following manner.

When a check box is made active, it first appears the same as the check box that was created in InDesign and remains as such.

This degrades the purpose of using the highlighted fields, which is to call attention to fields that need to be filled.

When the check boxes are created in Acrobat, it makes no difference in appearance or behavior if the “Show border hover color for fields” is selected or not. They always appear as the checkbox style you have chosen to use. They do not revert to a generic check mark.

This is the way that custom check boxes created in InDesign should behave. Thus, they would allow the use of a highlighted field without the appearance of the “selected” custom graphic changing to an unwanted generic graphic.

Please refer to the InDesign Forums message at this link for examples:

https://forums.adobe.com/message/11063952#11063952

We are developping a plugin for inDesign and while testing a new feature on a Mac we noticed that sometimes InDesign was crashing. We managed to reproduce this bug in a very simple indesign script that make inDesign crash 100% of the time and I'm looking for a way to get around this inDesign bug.

The crash occurs when we programatically add an htmlItem to a pageItem then close the document too quicky, It's only on Mac, doing that on windows works perfectly. The crash error seems to be a memory usage problem on inDesign's side.

Here is the script code :

var document = app.activeDocument;

var sourcePageItem = document.allPageItems[0];

sourcePageItem.htmlItems.add(

document.activeLayer,

LocationOptions.AT_END,

sourcePageItem,

{

  geometricBounds: sourcePageItem.geometricBounds,  

  htmlContent: '<b>Hello</b>',  

}

);

document.close(SaveOptions.NO);

other observations :

-Doing a sourcePageItem.htmlItems[0].remove(); to remove the htmlItem after adding it doesn't change anything, so the problem comes from using the function htmlItems.add() and not having an htmlItem in the document.
-Delaying the close by using $.sleep(5000) before fix the crash, but we can't rely on it as the delay needed increase with the number of htmlItems added and it might be different from a computer to another due to performances.
-Saving the document or not doesn't change anything

I've added my clean document with just a rectangle frame, the script and the crash report on this url : https://we.tl/t-uFpX658s0o since we can't add an indeed file to the post

If there is no way to fix it, do you have an idea to get around this inDesign bug ?

In advance:
- Our external writers send us InDesign CC files (idml and indd)
- We open and save them in InDesign CS6
- Our customers use InDesign CS6

1. Version:
   InDesign CS6 8.0
   InDesign CC from 12.0 to 14.0.2 (others not tested)




2. Steps:
   Since when: between 10 and 17. April 2019 (last time it worked on 10. April 2019)

2.a Open InDesign CC (any version, i tested 12.0, 13.1, 14.0.1 and 14.0.2)
2.b Save a file with activated hypenation (either indd or idml, both tested)
2.c Open either one of 2.b. in CS6

1. Expected result:
   Hypenation works as usual in CS6. Text fits frames.




2. Actual result:




3. Hypenation doesn't work in CS6 which resluts in text frames having overflow




4. Test files and information:
   Already tested:



5. de- and reactivating hypenation in CS6


6. checking for "no break" option


7. checking every used paragraph- and character-format


8. checking user dictionary options


9. checking language options


10. checking autocorrection options


11. saved the file as idml and indd in CC 12.0, 13.1, 14.0.1, 14.0.2 and then opened it in CS6


12. contacted support