Dreamweaver 21.7.0.15757 Crashes when editing text on Mac macOS 26.4 (Tahoe)

I am filing this as a new bug report with full technical details from my crash logs, as I believe this is a distinct and unresolved issue affecting Mac users on macOS 26 Tahoe.

**My Setup:**
- MacBook Pro (Mac14,9 — M2 Pro, Apple Silicon)
- macOS 26.4 Tahoe (build 25E246)
- Dreamweaver 21.7.0.15757
- ARM-64 Native (not running under Rosetta)

**The Problem:**
Dreamweaver crashes randomly during normal editing sessions — cutting and pasting code, typing text, or sometimes spontaneously, with no specific user action. There is no consistent trigger, which makes it impossible to reproduce on demand. I have submitted multiple crash reports to Adobe through the macOS crash dialog.

**What the Crash Reports Show:**
Both crash reports I have studied in detail show an identical failure pattern. The exception type is EXC_BREAKPOINT (SIGTRAP) — this is not a simple application error but a hard assertion failure inside Dreamweaver's Chromium Embedded Framework (CEF), meaning the CEF code itself is hitting a condition it cannot recover from.

Thread 0 (CrBrowserMain) crashes at the top of the stack inside the Chromium Embedded Framework, specifically within the font rendering engine — the symbol fontations_ffi$cxxbridge1$font_ref_is_valid. This is CEF's Rust-based font rendering bridge failing on macOS 26 Tahoe.

In the first crash report (March 26), the failure is triggered during a mouse click event being processed by AppKit's -[NSView _recursiveLostHiddenAncestorBySwitchingWindow:], which then calls into AdobeOwl (the panel/UI framework), which in turn calls into CEF's font renderer — which crashes.

In the second crash report (March 30 — today), the failure is triggered differently: by a timer callback (NSFireTimer → CFRunLoopDoTimer) calling Dreamweaver's CEF message loop handler (DW_CEF_IPC::DWCEFMessageHandler::DoCefMessageLoopWork), which again enters CEF's Blink rendering engine (blink$cxxbridge1$crash_in_rust_with_overflow) and crashes with an overflow condition.

The fact that two different triggers (a mouse click and a timer callback) both end up crashing in the same CEF font/rendering layer strongly indicates the root cause is CEF's font rendering and Blink engine being incompatible with macOS 26 Tahoe's updated AppKit and rendering APIs — not anything in my user configuration.

The Chromium Embedded Framework version bundled in Dreamweaver 21.7 is 132.3.3.0 (org.cef.framework). This version predates macOS 26 Tahoe and has not been updated to handle Tahoe's changes to the font rendering stack.

**What I Have Already Tried (none resolved the issue):**
- Restoring Dreamweaver preferences (Cmd+Option+Shift at launch)
- Installing Rosetta
- Verifying Verdana and Tahoma fonts are enabled in Font Book
- Granting Dreamweaver Full Disk Access in System Settings > Privacy & Security
- Checking for any newer DW version (21.7 is the latest)

**What Needs to Happen:**
This requires Adobe to update the Chromium Embedded Framework bundled inside Dreamweaver to a version that is compatible with macOS 26 Tahoe's rendering APIs. No user-side workaround can fix a crash that originates inside CEF's own font rendering bridge.

I am continuing to send crash reports via the macOS dialog. I am happy to provide the full crash report files directly to Adobe engineering if that would help.

Is Adobe actively investigating CEF compatibility with macOS 26 Tahoe for Dreamweaver? Is there any timeline for a fix?