Skip to content

monokano

My feedback

220 results found

  1. 20 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
    monokano commented  · 

    @Egor
    Thank you for checking. I can reproduce this on the following macOS environments:

    macOS Ventura 13.7.5
    macOS Sequoia 15.7.4

    It appears to be macOS-specific.

    monokano shared this idea  · 
  2. 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
    monokano commented  · 

    2026 (30.3.0)
    I have confirmed that this bug has been fixed.. Thank you.

    An error occurred while saving the comment
    monokano commented  · 

    To reproduce this bug, follow these steps:

    - Save (or Save As) the file.
    - Open the saved file.
    - Save (or Save As) the file again.
    - Open the saved file.

    monokano shared this idea  · 
  3. 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)
    monokano supported this idea  · 
  4. 23 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
    monokano commented  · 

    @Nicole
    This is indeed a background save bug. However, it is not the Acrobat layers bug. It is a new bug introduced in 2026 (30.2.1), where linked images disappear in the PDF data of the PDF-compatible file. I have confirmed that it has been fixed in the beta.

    An error occurred while saving the comment
    monokano commented  · 

    @Camille
    Your issue is the malformed compatible PDF generation. This has been occurring for many years since the 2020 (v24), when background saving was introduced. It occurs randomly, so the triggering conditions cannot be identified. Some users have empirically found that disabling background saving can prevent this issue.

    An error occurred while saving the comment
    monokano commented  · 

    The bug posted here has been fixed in the following versions:
    2025 (29.8.4)
    2026 (30.1)

    If you experience issues with compatible PDFs in these or later versions, please uncheck "Save in Background" and "Export in Background" in Preferences.

    An error occurred while saving the comment
    monokano commented  · 

    AI files contain two different types of data: “native data” and “PDF data.”
    When PDF compatibility is enabled, the system generates PDF data that should have the same appearance as the native data.
    However, sometimes this PDF data does not match the appearance of the native data. This issue has become frequent since version 2020 (24) and later, when the background functionality was introduced.

    All applications except Illustrator only recognize the PDF data within AI files. InDesign also links AI files as PDF files. The abnormalities observed are likely due to failures in PDF data generation.

    An effective method to avoid this issue is to disable the background functionality.

    While Acrobat layer abnormalities occur in PDF data, PDF generation defects are a different bug from this.

    monokano shared this idea  · 
  5. 8 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)

    修正は最新の30.3一般リリースに反映されています。アップデート後、問題が解消されているか確認し、引き続き問題が発生する場合はご報告ください。

    The fix has been pushed into the latest 30.3 general release. Please update, check, and comment back if it still happens.

    An error occurred while saving the comment
    monokano commented  · 

    2026 (Beta) (30.4.0 #103)
    このバグが修正されたことを確認しました。完璧です。ありがとうございます。
    ---
    I have confirmed that this bug has been fixed. Perfect. Thank you.

    monokano supported this idea  · 
  6. 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)
    monokano supported this idea  · 
  7. 32 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)

    修正は最新の30.3一般リリースに反映されています。アップデート後、問題が解消されているか確認し、引き続き問題が発生する場合はご報告ください。

    The fix has been pushed into the latest 30.3 general release. Please update, check, and comment back if it still happens.

    An error occurred while saving the comment
    monokano commented  · 

    2026 Beta (30.4.0 #103)
    リンク配置、埋め込み、両方ともバグ修正されたのを確認しました。素晴らしい。

    ---
    I have confirmed that the bug has been fixed for both linked and embedded placements. Excellent work.

    An error occurred while saving the comment
    monokano commented  · 

    PDF書き出しでモノクロ2階調画像にグレースケールのダウンサンプルが適用されてしまうバグは、下記の経緯があります。

    1. このバグは10年以上前から「埋め込みのモノクロ2階調画像」ですでに発生していた(どの時点かは不明)
    2. 2025 (29.6) で、「埋め込みではないリンク配置のモノクロ2階調画像」にもこのバグが発生するようになった

    埋め込みの有無にかかわらずバグが発生しないようにする必要があります。

    ---
    これらのことはフォーラムの投稿から明らかになりました。
    https://community.adobe.com/t5/illustrator%E3%83%95%E3%82%A9%E3%83%BC%E3%83%A9%E3%83%A0-discussions/pdf%E3%81%8C%E5%8A%A3%E5%8C%96%E3%81%97%E3%81%A6%E3%81%97%E3%81%BE%E3%81%84%E3%81%BE%E3%81%99-cc2025/td-p/15391123?profile.language=ja

    monokano supported this idea  · 
  8. 20 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)

    Everyone - we want some more information about this issue.

    Is any export (PNG) done from Illustrator for any such (glitched preview) files showing the same thumbnail issue or not?

    Or, is the issue happening only with the thumbnail of the file as seen in the Mac / Win folder preview or while placing into another application?

    An error occurred while saving the comment
    monokano commented  · 

    2026 (30.2.1)
    In this version, a new bug has appeared in the new background save method. When image files such as PSD or JPG are placed as linked files (not embedded) and the .ai file is saved, the images very often disappear in the PDF data of the PDF compatible file.

    Note: I have confirmed that this bug does not occur in 2026 Beta (30.4.0 #87).

    For more information on the PDF compatible file, please refer to the following:
    What Does “Create PDF Compatible File” Mean in Adobe Illustrator?
    https://note.com/monokano/n/n9df9cfc584f4

    An error occurred while saving the comment
    monokano commented  · 

    The new background save method "Quick Save" in Illustrator 2026 (30.0) was causing malformed compatible PDF generation. The new method had actually been silently implemented in 2025 (29) as well, triggering the same bug.

    This issue was fixed in 2026 (30.1) and 2025 (29.8.4). However, the problems that background saving has had since 2020 (24) still appear to persist.

    An error occurred while saving the comment
    monokano commented  · 

    Illustrator files have two types of previews: "bitmap image" and "compatible PDF data." The issue being discussed here concerns the compatible PDF.

    Compatible PDF is not just used for previews — it serves as actual working data in many contexts, including linked placement in InDesign documents, import into After Effects, and more. It is a critically important component of the file.

    Compatible PDF must be generated with an appearance that is completely identical to the native data when saving an .ai file. However, ever since the background save feature was introduced, there has been a long-standing bug where the compatible PDF is generated with a different appearance. Moreover, because it occurs randomly, the exact conditions that trigger it cannot be determined.

    Some users have learned through experience that disabling the background save feature prevents this issue.

    monokano supported this idea  · 
  9. 35 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
    monokano commented  · 

    2026 (30.2.1)
    When a .psd image file is placed as a linked file, the image disappears from the compatibility PDF in the .ai file. Disabling “Save in Background” prevents the issue. This appears to be a new bug introduced by the new background save implementation.

    An error occurred while saving the comment
    monokano commented  · 

    The cause of this bug is the new feature called “Quick Save.” A reliable way to prevent this bug is to disable “Quick Save.” To do this, disable “Save in Background” in the preferences.

    An error occurred while saving the comment
    monokano commented  · 

    That bug appears to have been fixed in 2025 (29.8.3).

    An error occurred while saving the comment
    monokano commented  · 

    Bug Not Fixed
    2025 (29.8.2)
    2026 (30.0.0)
    2026 Beta (30.1.0 #65)
    2026 Beta (30.1.0 #89)

    Bug Fixed
    2025 (29.8.3)

    An error occurred while saving the comment
    monokano commented  · 

    2026 (30.0.0)
    This bug is also occurring in the official release version. It has not been fixed at all.

    ---
    このバグは正規リリース版でも発生しています。全く直っていません。

    An error occurred while saving the comment
    monokano commented  · 

    This bug is still occurring in the current latest version 2025 (29.8.2). Since this is a critical and serious bug, it should not be left unaddressed - a bug fix update should be released for 2025 (29) as well.

    ---
    この不具合は、現在の最新版である2025 (29.8.2) でも依然として発生しています。これは重大かつ深刻な不具合であるため、放置すべきではありません。2025 (29) 向けにも修正アップデートをリリースすべきです。

    An error occurred while saving the comment
    monokano commented  · 

    This bug appears to be avoidable by disabling ‘Save in Background’ in Preferences.

    ---
    このバグは環境設定の「バックグラウンドで保存」をOFFにすると回避できるようです。

    monokano supported this idea  · 
  10. 19 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)

    修正は最新の30.3一般リリースに反映されています。アップデート後、問題が解消されているか確認し、引き続き問題が発生する場合はご報告ください。

    The fix has been pushed into the latest 30.3 general release. Please update, check, and comment back if it still happens.

    An error occurred while saving the comment
    monokano commented  · 

    2026 Beta (30.4.0 #80)
    I’ve confirmed the bug has been fixed. Thank you.

    An error occurred while saving the comment
    monokano commented  · 

    In 2024 (v28), the em dash is correctly rotated sideways in vertical text layout (shown in blue). However, in 2025 (v29.8.2), the em dash incorrectly rotates upright like Japanese characters (shown in red).

    monokano shared this idea  · 
  11. 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)
    An error occurred while saving the comment
    monokano commented  · 

    As Egor mentioned, there seems to be an inconsistency in how gradients are handled in exported PDFs. Classic gradients are correctly clipped by their path objects, whereas perceptual gradients are not clipped, and the path objects themselves appear to be missing entirely. This difference in behavior between the two gradient types in PDF output should be straightforward to verify.

    Update: To reproduce this issue, please apply the gradient to a circular object rather than a rectangular one. In the exported PDF, perceptual gradients are output as rasterized images without being clipped by the path, resulting in blurry, anti-aliased edges. Classic gradients, by contrast, are properly clipped by the path in the exported PDF and therefore have clean edges.

    An error occurred while saving the comment
    monokano commented  · 

    Isn't what's being requested here that perceptual gradients should be clipped with a clipping mask in PDF output?
    In 2026 (30.2.1), the edges still appear jagged due to rasterization.

    monokano supported this idea  · 
  12. 8 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)

    The issue seems to visible at our end after closing the Illustrator and reopening the file. However, it is just the value does not get updated in the pop up panel. The transformation change on the object happens fine and is reflected properly in the properties panel as well. Let us know if you are experience similar behavior or not.

    monokano supported this idea  · 
  13. 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)

    最新の30.3一般リリースで修正されたとのことです。アップデート後、ご確認いただき、問題がまだ発生する場合はご報告ください。

    Claimed to be fixed in the latest 30.3 general release. Please update, check, and comment back if it still happens.

    An error occurred while saving the comment
    monokano commented  · 

    @Egor
    This is an extremely serious bug and should have been prioritized for a fix in 30.2. That's disappointing.

    An error occurred while saving the comment
    monokano commented  · 

    2026 (30.2.1)
    This bug has not been fixed.

    An error occurred while saving the comment
    monokano commented  · 

    I confirmed reproduction. This is a typical bug that occurs unknowingly during normal operations.
    This bug does not occur in version 30.0.0. It occurs in version 30.1.0.
    ----
    再現を確認しました。通常の操作で気づかずに発生する典型的なバグです。
    30.0.0でこのバグは発生しません。30.1.0で発生しています。

    monokano supported this idea  · 
  14. 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)
    monokano supported this idea  · 
  15. 28 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
    monokano commented  · 

    2026 Beta (30.1.0 #89)

    As Egor pointed out, the fact that perceptual gradients cause paths to disappear in PDF and outlines to be anti-aliased, making them independent of output device resolution, is not a desirable result.

    Addendum: In PDF/X-1a, there is no anti-aliasing and the jagged results have not been fixed.

    Further addendum: Perceptual gradients are subject to downsampling during PDF export. This is also a counterintuitive result.

    ---
    Egorさんが指摘している通り、知覚的グラデーションがPDFでパスが消失し輪郭がアンリエイリアス処理されるのは、出力デバイス解像度に非依存となるので望ましい結果ではありません。

    追記:PDF/X-1aではアンチエイリアスされず、結果がガタガタになるのは直っていません。

    さらに追記:知覚的グラデーションはPDF書き出し時のダウンサンプルの影響を受けます。これも直感に合わない結果です。

    An error occurred while saving the comment
    monokano commented  · 

    In PDF/X-1a, the perceptual gradation became a low-resolution image without anti-aliasing.

    ---
    PDF/X-1aでは知覚的グラデーションがアンチエイリアスがない低解像度画像になりました。

    monokano shared this idea  · 
  16. 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)
    monokano supported this idea  · 
  17. 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)
    An error occurred while saving the comment
    monokano commented  · 

    Since the background function was introduced in 2020 (24), PDF compatibility issues have started occurring. This is a bug that has persisted for 5 years now. The characteristic of this bug is that it occurs randomly and is impossible to reproduce.
    The only workaround is to disable the background function.

    ---
    バックグラウンド機能が搭載された2020 (24) 以降、互換PDF不良が発生するようになりました。5年も続いているバグです。このバグの特徴は、発生がランダムであり、再現が不可能なことです。
    唯一の回避策はバックグラウンド機能を無効にすることです。

  18. 14 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
    monokano commented  · 

    The workaround for this bug is to disable "Real-time drawing and editing" in the preferences. It's clear that this feature is the cause.

    ---
    このバグの回避方法は、環境設定の「リアルタイムの描画と編集」を無効にすることです。この機能が原因であることは明らかです。

    monokano supported this idea  · 
  19. 5 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
    monokano commented  · 

    This issue appears to be caused by having clipboard history software installed, rather than being a bug in Illustrator.

    ---
    この問題は、Illustratorのバグではなく、クリップボード履歴ソフトウェアがインストールされていることが原因であるようです。

  20. 26 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
    monokano commented  · 

    2026 (30.0)
    I have confirmed that this bug has been fixed. This is very good news.

    An error occurred while saving the comment
    monokano commented  · 

    Latest version at time of posting: 2025 (29.5)
    Since 2025 (29.3), a bug has been observed on the Mac version only.

    When typing in Japanese, it is common to change character types (e.g., full-width/half-width, hiragana/katakana) using the F-keys. However, starting with 29.3, pressing an F-key triggers Illustrator’s keyboard shortcuts (such as opening or closing panels) instead, making it impossible to switch character types as intended.

    This issue disrupts a fundamental aspect of Japanese input and significantly hinders workflow efficiency. We kindly request prompt investigation and resolution.

    ---

    Illustrator 2025(29.3)以降、Mac版でのみ次のような不具合が確認されています。

    日本語入力では、文字種(全角・半角、ひらがな・カタカナなど)をFキーで変換しながら入力することが一般的です。しかし、29.3 以降では、Fキーを押すとIllustratorのキーボードショートカット(パネルの開閉など)が優先して反応してしまい、文字種の変換ができなくなっています。

    この問題は、日本語入力の基本的な操作に支障をきたすものであり、作業効率にも深刻な影響を及ぼします。早急なご対応を希望します。

    monokano supported this idea  ·