monokano
My feedback
199 results found
-
31 votes
This issue was fixed with Beta Build 30.3.0.104 — please update and see if it solves the behavior for you.
However, the Eyedropper still doesn’t work as expected. Here, a report about Eyedropper + Shift changing text and adding stroke when applied — please upvote it.
An error occurred while saving the comment 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
·
-
20 votes
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
·
-
Acrobat layers duplicate excessively in AI file’s compatible PDF
-
Screenshot%202025-11-18%20at%204.26.18%E2%80%AFPM.png 63 KB -
Screenshot%202025-11-18%20at%204.16.59%E2%80%AFPM.png 44 KB -
Screenshot%202025-11-18%20at%204.10.01%E2%80%AFPM.png 74 KB -
Screenshot%202025-10-30%20094255.png 125 KB -
Screenshot%202025-10-30%20094325.png 40 KB -
Illustrator%20corrupted%20file%20event.jpg 51 KB
22 votesThe issue mentioned in this thread has been fixed in Illustrator v30.1 and v29.8.4
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
·
-
-
47 votes
An error occurred while saving the comment monokano
commented
The attached file shows how the ‘Scale’ display in Illustrator’s Links panel has evolved when placing linked images at 100%.
It seems to me that the major change in 2025 was the result of an attempt to make Illustrator more specialized for web use.An error occurred while saving the comment monokano
commented
In 2025 (29.7.1), this bug has started occurring even in flattened PSD files with only background layers. It has gotten worse and worse.
2025 (29.7.1) で、背景レイヤーのみのフラット化されたPSDファイルでもこのバグが発生するようになりました。状況は悪化の一途を辿っています。
monokano
supported this idea
·
-
31 votes10 comments · Illustrator (Desktop) Feature Requests » Effects, Appearance, Graphic Styles · Admin →monokano
supported this idea
·
-
35 votes
Seems to work fine in 30.2.1
Please comment back if it misbehaves at your side still.
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
·
-
28 votes
Perceptual Gradient now honors the Document Raster Effect settings in latest Beta build 30.1.89
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
·
-
8 votesmonokano
supported this idea
·
-
"Kinsoku" / Punctuation Squeeze doesn't work
-
28.7.1%E5%8F%AF%E4%BB%A5%E6%AD%A3%E5%B8%B8%E5%B7%A5%E4%BD%9C.png 599 KB -
30.0%E4%B8%8D%E8%83%BD%E6%AD%A3%E5%B8%B8%E5%B7%A5%E4%BD%9C%EF%BC%8C%E5%8D%A0%E4%BD%8D%E8%BE%83%E5%AE%BD%EF%BC%8C%E6%B2%A1%E6%9C%89%E6%8C%A4%E5%8E%8B.png 463 KB -
1732157743612.jpg 84 KB -
Video_2024-11-21_112918.mp4 1619 KB -
"Punctuation squeeze" does not work.png 128 KB
9 votesmonokano
supported this idea
·
-
-
3 votes
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年も続いているバグです。このバグの特徴は、発生がランダムであり、再現が不可能なことです。
唯一の回避策はバックグラウンド機能を無効にすることです。 -
13 votes
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
·
-
5 votes
This issue is reportedly fixed in the latest Beta 30.3.126 build.
Kindly update (or install) to verify the fix making it behave as expected, to allow the team to safely push it into the next general build.
If it still works wrongly — please comment back.
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のバグではなく、クリップボード履歴ソフトウェアがインストールされていることが原因であるようです。 -
25 votes
Reported as fixed in version 30.
If this is still a problem for you with the latest build — please comment.
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
·
-
3 votes
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, PDF data that matches the appearance of the native data is supposed to be generated.
However, sometimes this PDF data does not match the appearance of the native data. This issue has been occurring frequently since version 2020 (24) and later, when the background function was introduced.What Photoshop displays is the PDF data. The abnormality there is likely because the PDF data generation is failing.
An effective method to work around this issue is to disable the background function.
-
20 votes
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
·
-
22 votes
An error occurred while saving the comment monokano
commented
When I checked going back to version 10, I found that the Effect preview specifications have remained completely unchanged from that time until now.
This is speculation, but in the past, Effect processing was slow, so "Preview OFF" probably existed to avoid real-time rendering.
I speculate that the intended workflow for Effect preview was something like this:
1. Change settings with Preview OFF
2. Turn Preview ON to check the results
3. Turn Preview OFF again to modify numerical values
4. Turn Preview ON to confirm the settingsI believe this kind of repetitive toggle operation was the expected workflow to accommodate the technical limitations of that era.
An error occurred while saving the comment monokano
commented
*Illustrator 2025 (Beta) (29.9.0 #36)*
When accessing any effect from the Effect menu, unchecking the "Preview" option in the effect dialog box fails to disable the preview. The preview continues to be displayed even when the Preview checkbox is unchecked.
---
効果でプレビューのOFFが機能しない
メニューバー「効果」直下の全てで、設定ウィンドウで設定を変更して「プレビュー」をチェックOFFにしても表示が設定変更前に戻りません。チェックOFFの機能が働いていない状態です。
monokano
supported this idea
·
-
63 votes
An error occurred while saving the comment monokano
commented
Due to the current specifications, a large number of users are misunderstanding HEX color codes as "a color setting method that can be used universally regardless of color mode." This is a serious problem, especially because beginners fall into this misconception.
As a leading professional tool in the industry, Illustrator has a significant impact on users' learning experience. The current inconsistent implementation hinders proper conceptual understanding and increases learning costs, so improvement would be greatly appreciated.
---
現在の仕様により、多くのユーザーが16進数カラーコードを「カラーモードに関係なく汎用的に使用できるカラー設定方法」と誤解しています。特に初心者がこの誤解に陥るため、これは深刻な問題です。業界をリードするプロフェッショナルツールとして、Illustratorはユーザーの学習体験に大きな影響を与えます。現在の一貫性のない実装は正しい概念理解を妨げ、学習コストを増加させています。改善が強く望まれます。
An error occurred while saving the comment monokano
commented
Displaying a HEX value input field when the color panel is in CMYK mode is completely incorrect.
HEX values represent the RGB color model itself and cannot substitute for the CMYK color. Therefore, the current specification causes serious misunderstanding for users.----
カラーパネルがCMYKモードのときにHEX値の入力フィールドを表示するのは完全に間違っています。
HEX値はRGBカラーモデルそのものであり、CMYKカラーの代替にはできません。そのため、現在の仕様はユーザーに深刻な誤解を与えています。monokano
supported this idea
·
-
32 votes
Hi everyone,
In the latest BETA 30.0.21, we’ve improved the ‘Save As’ workflow.
Now, instead of remembering the last used format, the default will always be .AI.
We made this change to ensure that your files are consistently saved in the native Illustrator format, which is the most reliable option for preserving full editability.
Please try out he changes by downloading the latest BETA from the Creative Cloud and let us know if it helps you or not.
An error occurred while saving the comment monokano
commented
Illustrator 2026 (Beta) (30.0.0 #21)
It had been improved to meet the ideal specifications. Excellent.
---
理想的な仕様に改善されていました。素晴らしい。monokano
supported this idea
·
An error occurred while saving the comment monokano
commented
The native format for Adobe Illustrator is exclusively the Adobe Illustrator (.ai) format. When users create new documents and save them for the first time, they rightfully expect the native .ai format to be the default.
This is absolutely fundamental and non-negotiable: Setting any non-native file format as the default for new save operations would be a critical design error that violates core software principles. For an application with its own proprietary file format, defaulting to anything other than that native format for new saves is simply unacceptable.
Why this matters: Users trust that when they save their work in Illustrator, they are preserving it in the application's full-fidelity native format unless they explicitly choose otherwise. Breaking this expectation would compromise data integrity, user trust, and the fundamental purpose of having a native file format.
Recommended Approach:
- New Save: Must always default to .ai format without exception
- Export: Can remember the last selected export format for user convenienceThe Export function exists specifically for outputting to non-native formats. That is where format memory belongs, not in the core save functionality.
This is not a preference or suggestion - it is a fundamental requirement for maintaining Illustrator's integrity as a professional application.
---
Adobe Illustratorのネイティブ形式は、Adobe Illustrator（.ai）形式のみです。ユーザーが新規ドキュメントを作成し、初回保存を行う際、ネイティブ.ai形式がデフォルトになることを当然のこととして期待しています。
これは絶対に基本的かつ譲れない原則です：新規保存操作で非ネイティブファイル形式をデフォルトに設定することは、ソフトウェアの基本原則に違反する重大な設計ミスとなります。独自のプロプライエタリファイル形式を持つアプリケーションにとって、新規保存でそのネイティブ形式以外をデフォルトにすることは、単純に受け入れられません。
なぜこれが重要なのか：ユーザーは、Illustratorで作業を保存する際、明示的に他の形式を選択しない限り、アプリケーションの完全な忠実度を持つネイティブ形式で保存されることを信頼しています。この期待を裏切ることは、データの整合性、ユーザーの信頼、そしてネイティブファイル形式を持つ根本的な目的を損なうことになります。
推奨されるアプローチ：
- 新規保存：例外なく常に.ai形式をデフォルトにしなければならない
- 書き出し：ユーザーの利便性のため、最後に選択した書き出し形式を記憶することができる書き出し機能は、非ネイティブ形式への出力を目的として特別に存在しています。形式記憶機能が属すべき場所はそこであり、コアとなる保存機能ではありません。
これは好みや提案ではありません。プロフェッショナルアプリケーションとしてのIllustratorの整合性を維持するための基本的な要件です。
-
4 votesmonokano
supported this idea
·
-
8 votes
An error occurred while saving the comment monokano
commented
2024では発生せず、2025で発生するということは、「2025のバックグラウンド機能に新たなバグがある」と考えられるところです。
バックグラウンド機能のバグは、通常は不規則に発生するので、再現手順を確定できず、修正も困難というかなり厄介な問題を抱えています。
その中でも、再現手順を確定できたものは修正されました。
https://illustrator.uservoice.com/forums/601447-illustrator-desktop-bugs/suggestions/47176633今回のバグも再現手順を確定できたものなので、修正されることを期待するところです。
---
Since this doesn’t occur in 2024 but does occur in 2025, it suggests that ‘there’s a new bug in the 2025 background function.’
Background function bugs typically occur irregularly, making it impossible to establish reproduction steps and difficult to fix - this presents quite a troublesome problem.
Among these, the ones where reproduction steps could be established have been fixed.
https://illustrator.uservoice.com/forums/601447-illustrator-desktop-bugs/suggestions/47176633Since reproduction steps have been established for this current bug as well, I expect it to be fixed.
monokano
supported this idea
·
An error occurred while saving the comment monokano
commented
macOS Ventura 13.7.5
Illustrator 2025 (29.8.1)「環境設定 > ファイル管理」の「バックグラウンドで○○」をチェックONにしていると再現しました。チェックOFFにすると防げると思います。
aiファイルの互換PDFに異常が発生するのは、総じてバックグラウンド機能が原因であることが経験則として判明しています。バックグラウンド機能が搭載された2020 (24) 以降からずっと問題になっています。
---
This bug occurred when the background setting in 'Preferences > File Handling' was checked ON. I think it can be prevented by unchecking it (turning it OFF).The abnormalities occurring in compatible PDFs of AI files are generally caused by using the background function. This has been an ongoing problem ever since the background function was implemented in 2020 (version 24) and onwards.
@Egor
This is an extremely serious bug and should have been prioritized for a fix in 30.2. That's disappointing.