Skip to content

Matthew Williams

My feedback

19 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    In ID 2025, I can extend my palettes from the top of the screen to the bottom. In ID 2026, I'm limited to the height shown in the screen shot. Try dragging the bottom handle of the palette down on a display with a resolution of 1440 pixels high. If your machine behaves like mine, you won't be able to drag all the way to the bottom of the display. See the attached video.

    Matthew Williams shared this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    Thanks for the quick reply.

    I have a document that I created in ID 2025. I opened it in ID 2026, but my client is still working in ID 2025, so I wanted to supply them with a Print PDF for a stable reference document and an IDML file so that they could open it in ID 2025.

    In ID 2026, save to IDML takes 93. In ID 2025, it takes 2 seconds.
    The PDF export issue seems to have resolved itself. I may have missed that it was exporting as an interactive PDF, so I'll keep an eye on that and report back if it starts misbehaving.

    I've attached the 2026 INDD file and the 2025 INDD file that I generated from the 2026 IDML file. You will notice when comparing the hyperlinks in the 2026 INDD file and the 2025 INDD file that the hyperlinks on the JL parent page are almost all broken in the 2025 file.

    Matthew Williams shared this idea  · 
  3. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello All,

    Thank you for your support. The issue is now fixed in the latest update of InDesign.
    Please upgrade to the new InDesign 14.0 from your Creative Cloud Application.

    If you are unable to see the update yet, click on the menu (three dots) on the top right corner of Creative cloud app and click on “Check for App Updates”.

    Let us know your feedback in the comment section.

    Thanks,
    Abhinav Kaushik
    InDesign Team

    Matthew Williams supported this idea  · 
  4. 31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    Hi. In ID 2025, I could open a document when I already had a document open, and the new document window would fit the existing window. In 2026, the new document forces the window to expand to fill the screen. This is a problem because I often have a PDF and InDesign file open side by side to do corrections. Now, every time I open a new InDesign file to make edits, it fills the screen over my PDF, and I have to resize the window over and over. It's not a huge ordeal, but it is an inconvenience that has popped up in 2026. It'd be great if it can be returned to the behavior in 2025. Thanks!

    Matthew Williams supported this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  6. 600 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams supported this idea  · 
  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  8. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    Thanks for finding this, Rivkah. I'll check it out.

    Matthew Williams supported this idea  · 
    Matthew Williams shared this idea  · 
  9. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    This seems to have gotten worse in 20.0. I'm now losing either the left-most or right-most Arabic character on export to PDF in multiple situations.

    This is a huge problem!

    The only workaround I've been able to find is to print the file to postscript and then convert it using Distiller, but that creates complications with finicky printers and is a huge waste of time.

    C'mon, Adobe. There are bugs reported on this forum that are DECADES old and not fixed. If I can no longer rely on InDesign to accurately output what it's showing me on screen—the most basic function!—why am I even using this program. I'd be better off going back to QuarkXPress.

  10. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    The fix of the issue is now available in the latest InDesign 2025(v20.0.1.032). We recommend you upgrade to the latest version for the fix.

    If you are unable to see the update, go to the Creative Cloud application click on the context menu on the top right, and click on Check for App Updates.

    Adobe InDesign Team

    Matthew Williams shared this idea  · 
  11. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    This is critical!

    I have been using the same template for years without this happening, and I can confirm that it now DOES happen even though the only change was the version of InDesign. I can send a file if that helps. In the meantime, here's a screenshot. The "7" should be a proportional lining numeral like the "3" is, but instead, it's being set as a proportional old style numeral.

    Thanks!

    Matthew Williams supported this idea  · 
  12. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

    An error occurred while saving the comment
    Matthew Williams commented  · 

    If it's any help locating the problem, it seems to be related to the recomposition engine. I've had fussy tables in I design for as long as I've been able to make tables in InDesign, but the file I'm fighting with now has all kinds of weirdness happening. Sometimes when I force recompose a page with a table on it, the page is blank after the table and the remaining text flows onto the next page. Sometimes I can get a table that spans two pages to behave if I make the text frame extra wide, but as soon as I resize the frame to the correct size, InDesign locks up. It seems like it's unable to decide whether or not to repeat the column heads on the second page. It could also be having trouble calculating whether or not the footnotes in the table will fit on the page.

    The recomposition engine has a number of problems that I've reported on; this seems to be just another.

  13. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Hi,
    Thanks for reporting the issue
    We are looking into it

    -InDesign Team

    Matthew Williams supported this idea  · 
    An error occurred while saving the comment
    Matthew Williams commented  · 

    Looks like this is still open, so hoping my case sheds some light. When I run a GREP search for any character between two tags, text between the tags that includes a footnote reference is missed by the find. I've attached a PDF showing what I mean and an InDesign file that you can test.

    I have tried adding ~F to the GREP find (i.e., "[.~F]+"), but that seems to corrupt the find entirely. Just searching for "<u>[.+]</u>" finds the string as long as it doesn't include a footnote reference. If I add ~F ("<u>[.~F]+</u>"), the find fails to locate any occurrences, even those without footnote references. If I then delete the ~F, the resulting find—which matches the original—continues to fail to find any occurrences. Retyping the original find (rather than just deleting ~F) allows the find to work again.

    I'm working on a Mac, OS 12.6.3, InDesign version 18.1 (reported as up to date in CC on 2/13/2023).

  14. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  15. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  16. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  17. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  18. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  19. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 

Feedback and Knowledge Base