CEP 11 Now in Prereleases

Test your plugins against our new releases

CEP (the Common Extensibility Platform) version 11 contains a major CEF update (Chromium Embedded Framework), from v74 to v88 and a major Node.js update, from v9 to v15.9.0.

CEP 11.1 has the CEF upgrade to v88 and CEPHTMLEngine runs as a native ARM processors on macOS M1 Apple silicon devices.

The CEP team is interested in your feedback!

Updates and Bug Fixes

✅ CEP-2221: Native Mac ARM Support for all CEP components
✅ CEP-2349: CEF Update to v88
🐛 CEP-2291: CEPHtmlEngine Helper crash
🐛 CEP-2208: Crash in: node::NodePlatform::Shutdown reported from After Effects.
🐛 CEP-2337: Windows only: IME is disabled in certain cases when entering text in textfields.
🐛 CEP-2382: Crash in CEPHTMLEngine Helper (renderer).
🐛 CEP-2251: CEP Extension with Video causes Crash/hang when moved between monitors.
🐛 CEP-2215: [GitHub Issue:320] Capture Panel layout issues when panel moved between primary and secondary screen.

How to Migrate from CEP 10 to CEP 11 and Known Issues

1. Update the Node Modules: CEP 11 works with NodeJS 15.9.0 and Node-WebKit 0.50.1 version. If your extension(s) were built on older versions of NodeJS there can be cases where these extensions may not load in CEP 11 due to incompatible node modules. In such cases, the node modules need to be updated using NodeJS version 15.9.0 or higher.
2. Content-Security-Policy Changes: With CEP 11.1 that integrates CEF #88, content-security-policy checks are strictly enforced. Extensions that embed third-party websites may not be able to do so anymore if the embedded site has a content-security-policy directive that doesn’t allow sites to frame them.
3. Cookies: With CEF v88, we have seen that when no SameSite attribute is set in a cookie, it defaults to SameSite=Lax. This will cause the cookie to be blocked in cross-site contexts. If your application needs cookies to be used in a cross-site context, we suggest you set SameSite=None.If a component is not sending the SameSite attribute in the cookie it will default to SameSite=Lax to prevent setting the cookie in a cross-site context. Refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie and https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite for more information.
4. CORS checks: With CEP 11 security updates, we are seeing many more requests blocked by CORS checks. Your extension may encounter this if it is trying to access an endpoint that does not have the Access-Control-Allow-Origin header. Please ensure that your endpoints have Access-Control-Allow-Origin headers set appropriately.

Where to Try CEP 11

Be sure to check out the CEP Cookbook for the most up-to-date information. The following list is current at the time of this writing:

• After Effects 18.4 — prerelease or public beta
• Animate TBD
• Audition 14.4 — prerelease or public beta
• Bridge TBD
• Dreamweaver 22.0 — October, no prereleases are planned
• Illustrator 25.3 — prerelease
• InCopy 16.3 — via InDesign prerelease
• InDesign 16.3 — prerelease, or SDK developer prerelease
• Photoshop 23.0 — CEP 11 will only be available on Intel Macs and Windows (not on ARM or M1 devices, unless you run Photoshop in Rosetta 2 mode)
• Premiere Pro 15.4 — currently in public beta

Where to Report Issues

Generally speaking, if you find a bug or want to report an issue, please post about it in the relevant forum for the Creative Cloud app you found it in. However, if you have a feature that worked in CEP 10 that is broken by CEP 11, please report it in the CEP GitHub issues here.

For more stories like this, subscribe to our Creative Cloud Developer Newsletter.