Chore: Enable New Block Editor by Default#36257
Conversation
Remove feature flag for the new TipTap-v3 block editor.
🤖 Bedrock Review —
|
|
Claude finished @wezell's task in 2m 11s —— View job Rollback Safety Analysis
Result: ✅ Safe to Roll BackThe two changed files contain no rollback-unsafe operations:
Categories checked: C-1 through C-4, H-1 through H-8, M-1 through M-4 — none match. Note: The diff also reveals a duplicate |
The JSP loaded /dotcms-block-editor/{polyfills,generator-runtime,main}.js and
styles.css at fixed URLs, and the web-component app builds with outputHashing:none,
so after a dotCMS upgrade browsers kept serving the stale editor bundle from cache
until a manual hard-reload — the symptom where the new Block Editor "wouldn't load"
until a full reload. Append ?v=<build revision> (ReleaseInfo.getBuildNumber()) so the
URL changes per build and the cache busts automatically.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🤖 Bedrock Review —
|
|
Tick the box to add this pull request to the merge queue (same as
|
🤖 dotBot Review (Bedrock)Reviewed 2 file(s); 3 candidate(s) → 3 confirmed, 0 uncertain (unverified, kept for review). Confirmed findings
us.deepseek.r1-v1:0 · Run: #28272114940 · tokens: in: 11552 · out: 3490 · total: 15042 · calls: 7 · est. ~$0.034 |
|
|
||
| ## New TipTap-v3 Block Editor (rollback safety: legacy editor renders by default) | ||
| FEATURE_FLAG_NEW_BLOCK_EDITOR=false | ||
| ## Enhanced locale selector v2 in the edit-content sidebar |
There was a problem hiding this comment.
🟠 [High] Accidental removal of New Block Editor feature flag
The grep search found no instances of FEATURE_FLAG_NEW_BLOCK_EDITOR in the config file, and the read_file output shows the line was removed while a duplicate FEATURE_FLAG_LOCALE_SELECTOR_V2=true was added. This configuration change would disable the New Block Editor feature by default (since undefined flags default to false), directly contradicting the PR's stated purpose of enabling it. The duplicate LOCALE_SELECTOR_V2 line suggests a copy-paste error during modification.
| <%@ page import="com.liferay.portal.util.ReleaseInfo" %> | ||
| <!DOCTYPE html> | ||
| <script type='text/javascript' src='/dwr/interface/LanguageAjax.js'></script> | ||
|
|
There was a problem hiding this comment.
🟠 [High] Unescaped build number in HTML attribute risks XSS
The build number from ReleaseInfo.getBuildNumber() is directly output using <%= without HTML escaping in edit_contentlet.jsp line 82. This allows XSS if the build number contains special characters. The current PR does not modify this line, leaving the vulnerability present.
Turn of the New Block Editor by default
This PR fixes: #36254