Adobe InDesign: Bugs
When filing a new bug, please provide:
- Version of Adobe InDesign, InCopy or InDesign Server
- Steps to reproduce the issues
- Expected result
- Actual result
- Test file, screenshot, video or GIF capturing the issue (optional)
219 results found
-
WorldReady settings go missing in [Basic Paragraph] style
Adobe InDesign (ME) 2021, 2020, CC 2019, ..., CS6
macOS and WindowsInDesign's WorldReady settings (Paragraph Direction, Kashidas, etc.) are being stripped from a document's [No Paragraph Style] style when opened on a machine with a missing 3rd-party plug-in (like Em Software's InCatalog). This appears to happen with any 3rd-party plug-in that adds a text attribute with a prefix that's lower than the WorldReady plug-in's prefix. While the following steps use the Middle Eastern app (English Arabic), where there's a UI to see the style's empty/blank WorldReady entries, we've confirmed that this problem affects all app variants (including English (Roman)).
…
15 votesThanks for reporting this issue.
We’ll review this shortly.—
Adobe InDesign team -
[ID-4219714]CEPHtmlEngine maxes out CPU to 100%
macOS Catalina 10.15.5. and InDesign. 15.1.1.
Massive problem with CEPHtmlEngine Helper. After a while, my MacBook Pro fan is running high and in the activity window, CEPHtmlEngine Helper is running between 90 and 100%. It is no fun to work with a system that runs crazy.
Why? Solution needed.41 votesThis issue is being reviewed again.
—
Adobe InDesign team -
object style override plus-sign when multiple elements selected
Object style made. Works fine.
Multiple items on page need same style. When applied to ONE item, styles menu looks "normal." When applied to multiple items, with items selected, the styles menu shows plus-sign after style name.
All of "clear overrides" options tried. Does not fix. Cannot verify that use of style is correct if styles panel gives false feedback.
In the past, earlier versions, I don't remember ever seeing this apparent conflict.
MacOS 11.5.2
InDesign 17.0.11 voteThanks for reporting this issue.
We are going to review this shortly.
--
InDesign team
-
[ID-4261011] In Find/Change, search for font style (eg "Book") incorrectly selects "Regular" style text, even if "Book" style isn't present
In InDesign 2021 (the latest version both on Mac and Windows), I add a text frame and fill it with placeholder text which is set, by default, to Minion Pro - Regular.
Then I go to the find-change dialog box and set 'find format > basic character format > font style' to Book.
And guess what happens when I hit the ‘find next’ button? It selects all the ‘regular text. (The document has no text with the 'book' font style applied!)
Selecting another style — e.g. Bold, Italic, etc. — results, as expected, in the 'cannot find match' alert.
Looks…13 votesHi,
Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation.
—
Adobe InDesign Team
-
Text formatting can break backlinking endnote texts to endnote refs when exported to PDF (Print)
Hi together,
to explain the issue:Sometimes backling from endnote text to endnote reference number will not work.
To make it work at all I found the following minimum requirements for PDF export:
PDF Export (Print)
Compatibility: Acrobat 5 (PDF 1.4)
[x] Create Tagged PDF
[x] Hyperlinks enabled
Even with that sometimes only linking from the endnote reference number to the endnote text will work, but not backlinking from the endnote number in the endnote text to the reference in the main text.
What I found:
If you want linking back from the endnote number at the start of the…
13 votesThanks for reporting the issue of backlinking not working for Endnotes with WR Composers.
We’re going to review this shortly.—
Adobe InDesign team -
[ID-4222229]Exporting to ePub (reflowable) when document has endnotes containing hyperlinks causes InDesign to hang
Version of Adobe InDesign: 15.1.2 / macOS 10.15.6
Steps to reproduce the issues: When exporting a document with endnotes containing hyperlinks to ePub (reflowable), InDesign hangs and needs to be force quit. Have tested removing all hyperlinks to tests, and document exports correctly. Have tested putting hyperlinks outside of endnotes and document exports correctly. The bug is specific to hyperlinks which are part of the endnote text.
Expected result: Successful export with endnotes reciprocally linked to text, and hyperlinks in endnote text active to respective URLs.
Actual result: InDesign hangs and needs to be force quit.
21 votesHi,
We have been able to reproduce the issue and it is currently under investigation.—
Adobe InDesign Team -
GREP search failed to match all text in a story
We use to be able to search all text in a story by using this (?s).+ code. It’s working fine in CS6. But in CC2019, 2020, and 2021 on both Mac and Windows it will fail to select all text in the story if there is more than ~ 50000 character. Only the first ~ 50000 will be selected.
This might be related to an old bug that was introduced in 14.0.2 that was fixed in 14.0.3.
Steps to Reproduce:
1. Create a document with one story containing more than 50000 characters
2. Do a GREP Find using (?s).+A…
17 votesThanks for reporting. We will review the issue
-InDesign Team
-
[ID-4261147] Hyperlinks with alt text added in the accessibility section, the alt text disappears when you save the file as an .idml
Hyperlinks with alt text added in the accessibility section get lost when saving to .idml.
16 votesHi,
Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation.
—
Adobe InDesign Team
-
[ID-4260994]The filter in the review panel is automatically changing to "resolved"
This happens very frequently.
I will be going through user comments given online in the Indesign Review tab. As I do them I resolve them. This works fine.
But then suddenly and randomly it will just decide to change my filter to show all resolved! Then all the old issues magically appear in the tab again until I go back to filter and unselect the Resolved button.
Then it happens again. And again. It happens only when I go to change something in the document but it doesn't seem to matter what type of issue i'm doing. Replacing text. Deleting,…
12 votesHi,
Thank you for reporting the issue. We have been able to reproduce the issue and it is currently under investigation.
—
Adobe InDesign Team
-
Shortcuts for view at 200% 400% & 50% not working correctly
Windows 10 - Indesign CC 16.4 (only just updated today 8/10)
Issues - shortcuts
Ctrl+5 (view @ 50%)
Ctrl+2 (view @200%)
Ctrl+4 (view @400%) not working properly.Ctrl+5 is now view @ 33.33%
Ctrl+4 is now view @ 266.67%
Ctrl+2 is now view @ 133.33%The issue doesn't seem to be a thing for Mac, they work fine.
1 voteThanks for reporting this issue.
We are going to review this shortly.—
Adobe InDesign team -
GREP position marker "^" = Beginning of Paragraph (not beginning of a new line after a forced line break)
Dear Support,
with the GREP position marker "^" for "Beginning of Paragraph", the GREP-search should consider the position of the beginning of a paragraph.
But this marker does not only recognize the beginning of a paragraph, but also the beginning of a new line after a forced line break (SHIFT-RETURN).This is not correct: A forced new line is not the beginning of a paragraph.
The only correct way would be to consider the beginning of a paragraph (RETURN).Sometimes you can use "(?=\r)\w+" to look for a word behind a Return instead of "^\w+" to find only the hits…
18 votesThanks for reporting the issue. We will review it shortly
-InDesign Team
-
[ID-4224416]PDF comments: Delete <FEFF> marker after removal of all comments
After choosing »Delete all comments« from the fly-out menu of the PDF comments panel at every position, where a comment was before the removal, a <FEFF> char is left behind, which shows up as a zero-width colon (:), when special characters are turned on.
Since this is a useless char after deleting the comments, the <FEFF> should also be removed, when selecting the removal in the fly-out.
<FEFF> shows up with XML tags, notes and index markers, so we can’t simply do a TEXT search for <FEFF> to remove it.
BTW:
\x{feff} doesn’t work in GREP search, which is kind…46 votesThanks for reporting. We will review the issue shortly.
-InDesign Team
-
InDesign freezes while working with "Scale Tool"
When using the "Scale Tool", every 4 or 5 times or so the app freezes at the dialog box and there's no way to exit. You have to force quit the app and hope that your work is autosaved. Unacceptable and only started happening recently.
InDesign 15.1.1 on macOS Mojave 10.14.6
HELP!
16 votesWe’re reviewing this issue.
—
Adobe InDesign team -
Serious GREP style bug: ampersands
Hi, InDesign team.
I've run into a serious bug with GREP styles. Any GREP expression containing an ampersand character that is entered as a GREP style in a paragraph style will suddenly acquire additional ampersands whenever I scroll through the list of GREP styles.
STEPS TO REPRODUCE:
Create a simple GREP style as part of a paragraph style.
The entire GREP expression should consist of the single character &. (Though this also happens when the & is part of longer expressions.)
Make enough other GREP styles that you need to scroll in the window to see them all.
Close the…5 votesThanks for reporting. We’ll review this shortly.
—
Adobe InDesign team -
BUG (since CS6!): Nonbreaking Space (^S) Issue with World-Ready-Composer
Issue:
When using the ›World-Ready Composer‹, the character ›Nonbreaking Space‹ (^S) behaves exactly like the character ›Nonbreaking Space (Fixed Width)‹ (^s); i.e.: in justified paragraphs, its width does not adjust (like regular spaces do), but it is fixed and unchanging.
This only occurs with the ›Adobe World-Ready Composer‹ (both ›Paragraph‹ and ›Single-line‹) and not with the regular ›Adobe Composer‹ (neither ›Paragraph‹ nor ›Single-line‹).
It is not related to the font used, it has been tested with many different fonts.Versions with this bug, tested and confirmed by myself or colleagues:
InDesign (Standard Version) CS6, CC2015.0
InDesign (Middle Eastern Version) CC2020…
12 votesThanks for reporting. We will review the issue
-InDesign Team
-
Drop shadow in exported PDF is a different size
Certain drop shadows have a different size when they appear in an exported PDF.
In the attached example, the black shapes each have a drop shadow effect in yellow. When exported, the shadows appear shorter and narrower. The difference is approximately 20 pt narrower and 1 pt shorter. (Note the difference in proportion of the yellow drop shadow and black shape in the screenshots.) I've also included the drop shadow effect attributes.
This occurs with multiple PDF export settings including the default [High Quality Print]. I am able to reproduce this behavior in both InDesign versions 15.1.2 and 16.0.
12 votesThanks for reporting. We will review the issue shortly.
-InDesign Team
-
Translation bug : Spread -> Grossi instead of Planche (in french)
- Click on publish online button Single Page is well translated as "Un(e) seul(e)" (page) Spread is wrongly translated as "Grossi" Grossi means bigger (or what we had with trapping : spreading inks, so making ink marks bigger) Planche which has been the accepted term in inDesign for ages.
(also known as 09/01/2017 #ID-4199114)
11 votesThanks for reporting this issue. We will review it
-InDesign Team
-
Endnotes are tagged incorrectly when exporting to Accessible PDF from InDesign 2021
In InDesign 2021, endnotes are not nested inside of a <Note> tag like they should be. Now only the Endnote number is in a <Note> tag and everything else is in a <P> tag. Normal behavior is to put each Endnote in its entirety within a <Note> tag. In addition, for several versions Endnotes and Footnotes are in a <Note> tag but then there's a <P> tag within the <Note> tag. The <P> tag is unnecessary and causes an error when trying to validate Accessible PDF. Please remove the <P> tag within <Note> tags when exporting to tagged PDF.
6 votesThanks for reporting this issue.
We’ll review this shortly.—
InDesign team -
Exporting accessible PDF – wrong BoundingBox
InDesign Version: All
Background:
An accessible PDF needs for all graphics and pictures a bounding box.
This is used by AT e.g. to set a focus to a visual impaired user.
Using the PDF export a bounding box is defined for all linked images.Problem:
Often the bounding box does not fit to the visible area.
AT user get wrong information, in fact the file is not accessible.Steps to reproduce the issues:
Place an asset, where only a part of the linked asset is visibily placed in InDesign, the rest is cropped.Expected result:
Bounding box fits to visible…18 votesThanks for reporting the issue. We will review the bug shortly
-InDesign Team
-
Crash while export to JPG
indesign 16.2 (mac version) crashes every time exports jpg and it tries to overwrite existent jpg
2 votesHi,
We have been able to reproduce the issue and it is currently under investigation.—
Adobe InDesign Team
- Don't see your idea?