3 results found

1. PreflightScope not working

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’ and ‘1,2’)

   We would very much like to speed our preflight process and get rid of the tedious parsing of preflight results only to discard pages not set in the scope.

   One additional note on its behavior that could be fixed, too: if you define a scope that includes page numbers not in the document, either as
   - a range e.g. "1-5" when document has pages numbers 1,4,5,6,... or
   - e.g. "14" when the document has only 12 pages
   ––> InDesign throws an error "Error 30477: Invalid value for set property 'preflightScope'. Expected PreflightScopeOptions enumerator or String, but received "1-5".", which is quite misleading.

   PreflightOptions.preflightScope in InDesign has not worked since at least CS 5.5. No matter what value is used, preflight checks the whole document. Here is a sample script (error for color image <250 ppi) that the issue can be tested:

   var currDoc = app.documents[0];
   if (app.preflightProfiles.itemByName("export").isValid){
           app.preflightProfiles.itemByName("export").remove();
   }
   var pfProfile = app.preflightProfiles.add({name: "export"});
   var pfResRule = pfProfile.preflightProfileRules.add("ADBE_ImageResolution", {flag: PreflightRuleFlag.returnAsError});
   pfResRule.ruleDataObjects.add("color_min_res", RuleDataType.realDataType, 250);
   currDoc.preflightOptions.preflightScope = '1-2';
   var pfProcess = app.preflightProcesses.add(currDoc, pfProfile);
   pfProcess.waitForProcess();
   pfResults = pfProcess.aggregatedResults[2];
   $.writeln(pfResults);
   

   ––> with a 3-page document with problems on pages 2 and 3, InDesign reports both problems despite the scope been set to ‘1-2’ (same with ‘1’… more

   9 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  CEP  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  amaarora responded

   Thanks for reporting
   We are reviewing the issue

   -InDesign Team

2. Any open CEP panel keeps InDesign at 30–70% CPU while idle (macOS)

   Summary
   On macOS, as soon as one CEP panel is visible in InDesign, InDesign's main thread starts spending about half of its time in PlugPlugOwl → -[MTKView draw], even when nothing is happening (no user input, panel content not changing). CPU usage of the InDesign process goes from a few percent to 50–85% and stays there until the last CEP panel is closed.

   This happens with Adobe's own CC Libraries panel (com.adobe.DesignLibraries.angular), so it does not depend on third-party panel code. The same CC Libraries panel in Illustrator 2026 does not cause this.

   Environment
   macOS 14.8.9 (23J631), MacBook Pro (Apple M1 Max)
   Displays: built-in Liquid Retina XDR + external 4K display (3840×2160, used in a scaled HiDPI mode; macOS reports a 6720×3780 backing resolution)
   InDesign 2026 21.6.0.57 / InDesign 2025 20.5.5.119 (both affected)
   Illustrator 2026 30.8.2 (not affected)
   CEP 12.1 (Chrome/99 in the panel user agent)

   Steps to reproduce
   1. Launch InDesign 2026. Make sure no CEP panel is open (UXP panels and the built-in panels are fine).
   2. Leave InDesign idle and watch the CPU usage of the InDesign process in Activity Monitor (or ps -o %cpu -p <pid>).
   3. Open Window > CC Libraries.
   4. Do not touch anything. Watch the CPU usage again.
   5. Close the CC Libraries panel. CPU usage drops back.

   Results (idle, average of 2-second samples)
   App No CEP panel open CC Libraries panel open
   InDesign 2026 (21.6) ~16.5% ~75–87%
   Illustrator 2026 (30.8.2) ~0–3% ~1.7%

   The display setup does not matter: with the external display disconnected (built-in Retina display only, 3024×1964), InDesign 2026 measured ~16% without the panel and ~74% with the CC Libraries panel open — the same as with the external 4K display connected.

   Additional measurements in InDesign 2025 (20.5.5) with our own CEP panels:

   No CEP panel: ~3–4%
   One CEP panel visible: ~48–70%
   Six CEP panels visible: ~60–67% (it does not add up; it jumps with the first panel and stays there)
   Closing the last CEP panel: ~2.7%
   Replacing the panel's page with about:blank, hiding the body, or stopping all timers in the panel: no change
   The panel's renderer process (CEPHtmlEngine Helper) stays at ~0% CPU the whole time
   Lowering "User Interface Scaling" to the minimum (devicePixelRatio 2.5 → 2.0): no meaningful change
   Turning "GPU Performance" off (and restarting InDesign): no change
   A UXP panel, and a UXP panel with a <webview>, in the same InDesign: ~3–4% (not affected)

   What the profiler shows
   sample of the InDesign process while idle with one CEP panel visible (3 seconds):

   Main thread: ~1,750–1,930 samples
   Of these, ~50–58% are under: dispatchsourceinvoke → _23-[MTKView _initCommon]block_invoke → -[MTKView draw] → PlugPlugOwl (several internal frames)

   With no CEP panel visible, MTKView draw does not appear at all.

   It looks like the MTKView that hosts CEP panel content is driven continuously by its display-link timer, instead of drawing only when the panel content changes (e.g. enableSetNeedsDisplay / paused not set). Illustrator hosts the same CEP panel without this cost.

   Impact
   Any InDesign user who keeps a CEP panel open (including Adobe's own CC Libraries) pays a constant 30–70% CPU cost on the main thread while idle. On laptops this means heat, fan noise and battery drain, and it makes InDesign feel slower. Panel developers cannot work around it from inside the panel.

   The following is in Japanese:------------------------------------------------------------------------------------
   表題
   CEPパネルを開いているだけで、InDesignのCPU使用率が30〜70%になる（macOS）

   概要
   macOSのInDesignでCEPパネルが1枚でも表示されると、何も操作しておらず、パネルの中身も変わっていないのに、InDesignのメインスレッドが処理時間の約半分をPlugPlugOwl → -[MTKView draw] に使い始めます。InDesignのCPU使用率は数%から50〜85%に上がり、最後のCEPパネルを閉じるまでその状態が続きます。

   Adobe純正のCCライブラリパネル（com.adobe.DesignLibraries.angular）でも起きるので、サードパーティのパネルの作りとは関係ありません。同じCCライブラリパネルをIllustrator 2026で開いても、この現象は起きません。

   環境
   ・macOS 14.8.9（23J631）、MacBook Pro（Apple M1 Max）
   ・ディスプレイ：内蔵Liquid Retina XDR ＋ 外付け4K（3840×2160。拡大表示で使用し、macOS 上の内部の描画解像度は6720×3780）
   ・InDesign 2026 21.6.0.57／InDesign 2025 20.5.5.119（どちらも発生）
   ・Illustrator 2026 30.8.2（発生しない）
   ・CEP 12.1（パネルのユーザーエージェントはChrome/99）

   再現手順
   1. InDesign 2026を起動し、CEPパネルが1枚も開いていない状態にする（UXPパネルと標準のパネルは開いていてかまいません）。
   2. 何も操作せず、アクティビティモニタでInDesignのCPU使用率を見る。
   3. ［ウィンドウ］→［CCライブラリ］を開く。
   4. 何も操作せず、もう一度CPU使用率を見る。
   5. CCライブラリパネルを閉じると、CPU使用率は元に戻る。

   結果（何も操作していないとき・2秒おきの計測の平均）
   アプリ CEPパネルなし CCライブラリパネルを開く
   InDesign 2026（21.6） 約16.5% 約75〜87%
   Illustrator 2026（30.8.2） 約0〜3% 約1.7%

   ディスプレイの条件は関係ありません。外付けディスプレイを外して内蔵画面（3024×1964）だけにしても、InDesign 2026はパネルなしで約16%、CCライブラリパネルを開くと約74%で、外付け4Kをつないでいるときと同じでした。

   InDesign 2025（20.5.5）で、自作のCEPパネルを使って計った結果：

   ・CEPパネルなし：約3〜4%
   ・CEPパネル1枚を表示：約48〜70%
   ・CEPパネル6枚を表示：約60〜67%（足し算にはならず、1枚目で跳ね上がってそのまま）
   ・最後のCEPパネルを閉じる：約2.7%
   ・パネルのページをabout:blankに差し替える、bodyを非表示にする、パネル内のタイマーをすべて止める：変化なし
   ・パネル側の描画プロセス（CEPHtmlEngine Helper）は、ずっと約0%
   ・環境設定の［UIの拡大・縮小］を最小にする（devicePixelRatio 2.5 → 2.0）：ほとんど変化なし
   ・環境設定の［GPUパフォーマンス］をオフにする（InDesignを再起動）：変化なし
   ・同じInDesignでUXPパネル、および<webview>入りのUXPパネルを開く：約3〜4%（影響なし）

   プロファイラの結果
   CEPパネルを1枚表示し、何も操作していないときのInDesignをsampleで3秒間記録：

   ・メインスレッド：約1,750〜1,930サンプル
   ・そのうち約50〜58%が次の経路：dispatchsourceinvoke → _23-[MTKView _initCommon]block_invoke → -[MTKView draw] → PlugPlugOwl（内部の関数がいくつか続く）

   CEPパネルが表示されていないときは、MTKView drawはまったく現れません。

   CEPパネルの中身を表示するMTKViewが、中身が変わったときだけ描くのではなく、画面の更新のたびに描き続けているように見えます（たとえばenableSetNeedsDisplayやpausedが設定されていない）。Illustratorは同じCEPパネルを、この負担なしで表示しています。

   影響
   CEPパネル（Adobe純正のCCライブラリを含む）を開いたまま作業しているInDesignの利用者は全員、何もしていないあいだもメインスレッドで30〜70%のCPUを使い続けることになります。ノートパソコンでは発熱、ファンの音、電池の減りにつながり、InDesignの動作も重く感じられます。パネルを作る側では、パネルの中から回避する手段がありません。

   Summary
   On macOS, as soon as one CEP panel is visible in InDesign, InDesign's main thread starts spending about half of its time in PlugPlugOwl → -[MTKView draw], even when nothing is happening (no user input, panel content not changing). CPU usage of the InDesign process goes from a few percent to 50–85% and stays there until the last CEP panel is closed.

   This happens with Adobe's own CC Libraries panel (com.adobe.DesignLibraries.angular), so it does not depend on third-party panel code. The same CC Libraries panel in Illustrator 2026 does not cause this.

   Environment
   macOS 14.8.9 (23J631), MacBook Pro (Apple… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  CEP  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. getSystemPath using CSInterface throws URI Malformed error

   I was trying to get the my documents folder path of the system using CSInterface getSystemPath function. It works in most of the cases. But it throws URI malformed error (refer the screenshot below), if the path of the documents folder contain characters from languages other than English.

   I debugged the CSInterface.js file at line 521. And I found that the below piece of code returns the path of the folder without encoding the characters from languages other than English.

   window.adobe_cep.getSystemPath(pathType)

   IN MY CASE:

   Path of documents folder: "C:\Users\sanjay\OneDrive - Élégante\Documents".

   window.adobe_cep.getSystemPath(pathType)
   // Returned value - "file:///C:/Users/sanjay/OneDrive%20-%20Ã%89lÃ%a9gante/Documents"
   // É is encoded as Ã%89

   encodeURI("C:/Users/sanjay/OneDrive - Élégante/Documents")
   // Expected value - "file:///C:/Users/sanjay/OneDrive%20-%20%C3%89l%C3%A9gante/Documents"
   // É is encoded as %C3%89

   decodeURI("Ã%89") throws URI malformed error.
   decodeURI("%C3%89") returns É.

   ISSUE:

   So, I guess it is the problem with the encoding of window.adobe_cep.getSystemPath(pathType). Is there any work around for this issue?

   SAME ISSUE WITH OTHER FUNCTION:

   I'm also facing the same issue with other scripting functions like "documentAfterActivate" CS Event which returns the path of active document if a document is opened. The path received is not encoded properly for characters other than English.

   VERSION INFO:

   CEP: 9
   InDesign: 2022
   OS: Windows 10

   I was trying to get the my documents folder path of the system using CSInterface getSystemPath function. It works in most of the cases. But it throws URI malformed error (refer the screenshot below), if the path of the documents folder contain characters from languages other than English.

   I debugged the CSInterface.js file at line 521. And I found that the below piece of code returns the path of the folder without encoding the characters from languages other than English.

   window.adobe_cep.getSystemPath(pathType)

   IN MY CASE:

   Path of documents folder: "C:\Users\sanjay\OneDrive - Élégante\Documents".

   window.adobe_cep.getSystemPath(pathType)
   // Returned value -… more

   •  

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  CEP  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating