Skip to content

Commit 54c483d

Browse files
authored
Merge branch 'feature/8.0.0/DOC-3147' into feature/8.0.0/DOC-3147_TINY-12045
2 parents c7720ea + c9d4fa2 commit 54c483d

38 files changed

+1447
-662
lines changed

modules/ROOT/examples/live-demos/a11ychecker/index.js

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,11 @@ tinymce.init({
22
selector: 'textarea#a11ychecker',
33
plugins: 'a11ychecker advcode table advlist lists image media anchor link autoresize',
44
toolbar: 'a11ycheck | blocks bold forecolor backcolor | bullist numlist | link image media anchor | table | code',
5+
max_height: 500,
56
a11y_advanced_options: true,
67
a11ychecker_html_version: 'html5',
78
a11ychecker_level: 'aaa',
9+
a11ychecker_allow_decorative_images: true,
10+
a11ychecker_alt_text_max_length: 150,
811
content_style: 'body { font-family:Helvetica,Arial,sans-serif; font-size:16px }'
912
});

modules/ROOT/nav.adoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,8 +140,6 @@
140140
**** xref:configure-imageproxy-service.adoc[Image Proxy service settings]
141141
**** xref:configure-spelling-service.adoc[Spelling service settings]
142142
**** xref:self-hosting-hunspell.adoc[Spelling service - Using Hunspell dictionaries]
143-
**** xref:configure-logging-services.adoc[Activity logging]
144-
*** xref:introduction-to-premium-selfhosted-services.adoc[Server-side component installation without Docker]
145143
*** xref:troubleshoot-server.adoc[Troubleshoot server-side components]
146144
** Customizing the editor appearance
147145
*** xref:customize-ui.adoc[Customizing the UI]

modules/ROOT/pages/8.0-release-notes.adoc

Lines changed: 148 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
21
= {productname} {release-version}
32
:release-version: 8.0.0
43
:navtitle: {productname} {release-version}
@@ -59,6 +58,50 @@ The following premium plugin updates were released alongside {productname} {rele
5958

6059
// For information on the **<Premium plugin name 1>** plugin, see: xref:<plugincode>.adoc[<Premium plugin name 1>].
6160

61+
=== Accessibility Checker
62+
63+
The {productname} {release-version} release includes an accompanying release of the **Accessibility Checker** premium plugin.
64+
65+
**Accessibility Checker** Premium plugin includes the following improvements.
66+
67+
=== Accessibility: Enhanced image accessibility checks in a11ychecker plugin
68+
// #TINY-10903
69+
70+
The {productname} {release-version} introduces four new image accessibility rules (xref:a11ychecker.adoc##image-rules[Image rules]) in the xref:a11ychecker.adoc[a11ychecker] plugin to improve compliance and authoring guidance. These rules help identify common accessibility issues related to image use and provide actionable recommendations:
71+
72+
* *xref:a11ychecker.adoc#I1[I1: Mixed Signals & Decorative Policy]*: Flags images with conflicting accessibility indicators (e.g., `alt` with `role="presentation"`) and ensures decorative images comply with best practices.
73+
* *xref:a11ychecker.adoc#I2[I2: Alt Attribute Requirement]*: Enforces the presence of the `alt` attribute on all `<img>` elements, regardless of other labeling mechanisms like `aria-label`, `aria-labelledby`, or `title`.
74+
* *xref:a11ychecker.adoc#I3[I3: Filename Detection]*: Warns when `alt` text appears to be a filename (e.g., `image123.jpg`), including cases with URL encoding.
75+
* *xref:a11ychecker.adoc#I4[I4: Alt Text Length]*: Detects `alt` text that exceeds a configurable maximum length, promoting concise descriptions. The default limit is 100 characters and can be adjusted using the new xref:a11ychecker.adoc#a11ychecker_alt_text_max_length[`a11ychecker_alt_text_max_length`] setting.
76+
77+
Additional improvements include a rule precedence system to avoid duplicate violations, centralized image intent detection (e.g., decorative, informative, mixed signals, incomplete), and more readable user-facing messages. Technical terminology such as "alternative text" has been replaced with "text description," and repair instructions are now more contextual and user-friendly.
78+
79+
=== New `a11ychecker_alt_text_max_length` configuration option for Accessibility Checker alt text length
80+
// #TINY-10903
81+
82+
A new configuration option, xref:a11ychecker.adoc#a11ychecker_alt_text_max_length[`a11ychecker_alt_text_max_length`], has been added to the Accessibility Checker plugin. This option allows users to configure the maximum allowed length for image alt text descriptions. The default value is 150 characters. For example:
83+
84+
[source,js]
85+
----
86+
tinymce.init({
87+
selector: 'textarea',
88+
plugins: 'a11ychecker',
89+
a11ychecker_alt_text_max_length: 150 // Set maximum length to 150 characters
90+
});
91+
----
92+
93+
For more information on the Accessibility Checker plugin, see: xref:a11ychecker.adoc[Accessibility Checker].
94+
95+
=== PowerPaste
96+
97+
The {productname} {release-version} release includes an accompanying release of the **PowerPaste** premium plugin.
98+
99+
==== Word import of lists with a "lighter" level failed parsing.
100+
101+
When users pasted content from Microsoft Word documents containing lists styled with Word’s "No List" setting into the editor with PowerPaste enabled, the operation failed due to a parsing error. As a result, the content was not inserted into the editor, causing disruption to content workflows. {productname} {release-version} addresses this issue by updating the **PowerPaste** parser to correctly handle lists with the "No List" style. As a result, users can now successfully paste such content into the editor without encountering errors.
102+
103+
For information on the **PowerPaste** plugin, see: xref:introduction-to-powerpaste.adoc[PowerPaste].
104+
62105

63106
[[accompanying-premium-plugin-end-of-life-announcement]]
64107
== Accompanying Premium plugin end-of-life announcement
@@ -99,11 +142,24 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
99142

100143
{productname} {release-version} also includes the following improvement<s>:
101144

102-
// === <TINY-vwxyz 1 changelog entry>
103-
// #TINY-vwxyz1
145+
=== Instructions on how to navigate the color swatch, image select and insert table widget are now announced by screen readers.
146+
// #TINY-12189
104147

105-
// CCFR here.
148+
Previously, interactive elements such as the color swatch, create table grid, and image select were missing an `aria-label`. This resulted in a lack of instructions for keyboard users and hindered overall accessibility.
149+
150+
{productname} {release-version} now includes `aria-labels` for these elements, providing clear keyboard navigation instructions. This improvement ensures a more accessible experience for all users.
151+
152+
=== Resize handles are more accessible with `role` and `aria-valuetext` attributes.
153+
// #TINY-11421
154+
155+
In previous versions of {productname}, the editor's resize handle lacked a `role` attribute, raising accessibility concerns.
156+
157+
In {productname} {release-version}, the resize handle now includes a `role` seperator and an `aria-valuetext` attribute that dynamically reflects the current dimensions of the editor. These improvements enhance accessibility and ensure more accurate announcements by screen readers.
106158

159+
=== The translate API now automatically replaces three dots in a row with an ellipsis character.
160+
// #TINY-12155
161+
162+
Previously, menu items and tooltips containing three consecutive periods (`...`) were read aloud by the JAWS screen reader as "dot dot dot," which could confuse users relying on assistive technologies. To enhance accessibility, the `translate` API in {productname} {release-version} now automatically replaces three dots with the typographic ellipsis character (`…`) across all translations. This update ensures a consistent visual appearance while improving screen reader behavior, as the ellipsis character is not read aloud. The change is implemented directly in the translation function, ensuring comprehensive coverage across all languages.
107163

108164
[[additions]]
109165
== Additions
@@ -121,10 +177,17 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
121177

122178
{productname} {release-version} also includes the following change<s>:
123179

124-
// === <TINY-vwxyz 1 changelog entry>
125-
// #TINY-vwxyz1
180+
=== Changed the default value for the `pagebreak_separator` option.
181+
// #TINY-12013
126182

127-
// CCFR here.
183+
In previous versions of {productname}, inserting a page break in the editor did not translate correctly when exporting using the xref:exportpdf.adoc[Export to PDF] plugin. Similarly, the xref:exportword.adoc[Export to Word] plugin also failed to preserve page breaks in the exported documents. As a result, exported files lacked the intended page breaks, leading to confusing output for users.
184+
185+
With the release of {productname} {release-version}, this issue has been resolved by updating the default HTML value of the `pagebreak_separator` option:
186+
187+
* **Old value** – `'<!-- pagebreak -->'`
188+
* **New value** – `'<div style="break-after: page"></div>'`
189+
190+
This change aligns better with modern standards and ensures that page breaks are now accurately rendered in exported documents.
128191

129192

130193
[[removed]]
@@ -137,6 +200,12 @@ For information on using Enhanced Skins & Icon Packs, see: xref:enhanced-skins-a
137200

138201
// CCFR here.
139202

203+
=== Removed undocumented `documentBaseUrl` property from Editor instances. `documentBaseURI` is the supported property now.
204+
// #TINY-12182
205+
206+
An undocumented `documentBaseUrl` property was previously accessible on `Editor` instances. This property was not part of the supported public API and could lead to confusion or inconsistent usage across implementations.
207+
208+
To improve API clarity and maintain a well-defined interface, the `documentBaseUrl` property has been removed. Integrators should use the officially supported `documentBaseURI` property to access the base URI of the document.
140209

141210
[[bug-fixes]]
142211
== Bug fixes
@@ -150,6 +219,62 @@ In previous versions of {productname}, the content selection logic incorrectly a
150219

151220
This issue has been resolved in {productname} {release-version}. The selection logic has been updated to correctly identify and handle content within `<div>` elements such that it does not try to insert content within itself. As a result, pressing `Enter` after an image inside a `<div>` element no longer triggers errors or causes unintended behavior.
152221

222+
=== In inline mode, pressing the back button dismissed the context toolbar and moved focus from the selected image to the editor.
223+
// #TINY-12118
224+
225+
In inline mode, the context form toolbar incorrectly shifted focus from the selected image to the editor container. As a result, the plugin which relies on the current selection to apply changes was unable to apply attributes like `alt` text to the correct image.
226+
227+
{productname} {release-version} resolves this by ensuring that the focus is preserved properly, ensuring that the plugin now applies changes such as `alt` text to the correct image in inline mode.
228+
229+
=== Toolbar drawer now closes when the editor loses focus.
230+
// #TINY-12125
231+
232+
In previous versions of {productname}, the floating toolbar remained visible even when the editor lost focus. This behavior introduced potential accessibility concerns, as the toolbar was not properly associated with the editor it controlled, potentially causing confusion for users.
233+
234+
In {productname} {release-version}, the toolbar now automatically closes when the editor loses focus. This ensures it is only displayed within the appropriate context, enhancing accessibility and improving the overall user experience.
235+
236+
=== Arrow key navigation between buttons was blocked when a button is hovered by the mouse.
237+
// #TINY-12163
238+
239+
In previous versions of {productname}, if a button was hovered by the mouse while using arrow keys for navigation, focus would return to the previously focused element. This caused the selection to become stuck on the button with the `mouseover` event.
240+
241+
{productname} {release-version} resolves this issue by preventing the `mouseover` event from being triggered again during arrow key navigation, ensuring a seamless user experience when navigating with arrow keys.
242+
243+
=== It was not possible to navigate out of a `figcaption` using the left and right arrow keys in Firefox.
244+
// #TINY-11982
245+
246+
Prior to {productname} {release-version}, Firefox exhibited an issue where pressing the left or right arrow keys would not allow users to exit the image `figcaption` element. This behavior was inconsistent with other major browsers such as Google Chrome and Safari, where the arrow keys functioned as expected and allowed seamless navigation out of the `figcaption`.
247+
248+
With {productname} {release-version}, this issue has been resolved. Users can now exit the `figcaption` using the left/right arrow keys in Firefox, aligning its behavior with that of other browsers. This update ensures a more consistent user experience.
249+
250+
=== Decorative images would lose their decorative status when the `alt` subtoolbar was closed when using the apply button.
251+
// #TINY-11912
252+
253+
Previously, an issue was identified where closing the `alt` subtoolbar using the `Apply` button would inadvertently remove the decorative status from an image that was already marked as decorative. This occurred because the `onSetup` API disabled the input group, leading the `Apply` logic to incorrectly interpret the image as non-decorative.
254+
255+
This issue has been resolved in {productname} {release-version}. The `onSetup` and `Apply` behavior has been aligned to consistently evaluate the input group, ensuring the decorative status is preserved as expected.
256+
257+
=== The HTML schema did not treat `colgroup` or `col` elements as block elements.
258+
// #TINY-12092
259+
260+
In previous versions of {productname}, whitespace between `<colgroup>` and `<col>` tags was not removed by {productname}'s HTML schema. This behavior caused the editor to preserve unnecessary whitespace characters in the table markup.
261+
262+
This issue has been resolved in `{release-version}`. Both `colgroup` and `col` elements are now treated as block-level elements, ensuring that extraneous whitespace is stripped from these areas. As a result, the editor now produces cleaner and more concise table markup.
263+
264+
=== Deleting a whole element would sometimes modify nearby content
265+
// #TINY-11868
266+
267+
Previously, deleting a complete HTML element using the "Source Code" editor either by cutting `+Ctrl+X+` or `+Cmd+X+`, backspacing, or pressing delete could inadvertently modify surrounding content. For example, removing a `<div>` element that precedes a `<p>` tag could cause the `<p>` to be transformed into a `<div>`, resulting in unintended structural changes.
268+
269+
This issue has been resolved in {productname} {release-version} by improving how element deletions are handled within the editor's DOM logic. Cutting or deleting a selected element now preserves the integrity and tag type of adjacent elements. Users can expect consistent and predictable editing behavior when modifying HTML source content.
270+
271+
=== Strikethrough format could be added outside font size format, which renders incorrectly in some browsers.
272+
// #TINY-12004
273+
274+
Previously, there was an issue where combining strikethrough (`s` element) and font size formatting could lead to incorrect rendering in some browsers, particularly Chrome. This occurred when the `s` (strikethrough) element was placed outside a font size `span`, causing the strikethrough line to render incorrectly.
275+
276+
The fix ensures that the `s` element is now properly nested inside the font size element, improving visual consistency across browsers.
277+
153278

154279
[[security-fixes]]
155280
== Security fixes
@@ -165,7 +290,22 @@ This issue has been resolved in {productname} {release-version}. The selection l
165290
[[deprecated]]
166291
== Deprecated
167292

168-
{productname} {release-version} includes the following deprecation<s>:
293+
{productname} {release-version} includes the following deprecations:
294+
295+
=== Java application server-based server components have been deprecated
296+
// #DOC-3231
297+
298+
{productname} {release-version} deprecates the Java application server-based deployment method for self-hosted services. Docker containers are now the **only** supported deployment method for self-hosted services. The Java `.war` files (`ephox-spelling.war`, `ephox-image-proxy.war`, `ephox-hyperlinking.war`) will be removed in a future release.
299+
300+
For information about setting up containerized server-side components using Docker containers, see: xref:bundle-intro-setup.adoc[Introduction and initial setup for containerized server-side services from the premium self-hosted bundles]
301+
302+
=== Docker container services
303+
304+
* Enhanced Media Embed and Link Checker service, see: xref:individual-hyperlinking-container.adoc[Deploy the {productname} hyperlinking server-side component using Docker].
305+
* Image Editing and Export image proxy service, see: xref:individual-image-proxy-container.adoc[Deploy the {productname} image proxy server-side component using Docker].
306+
* Spell Checker service, see: xref:individual-spelling-container.adoc[Deploy the {productname} spelling service server-side component using Docker].
307+
* Export to PDF service, see: xref:individual-export-to-pdf-on-premises.adoc[Deploy the {productname} Export to PDF service server-side component using Docker].
308+
* Import from Word and Export to Word services, see: xref:individual-import-from-word-and-export-to-word-on-premises.adoc[Deploy the {productname} Import from Word and Export to Word service server-side component using Docker].
169309

170310
// === The `<plugin>` configuration property, `<name>`, has been deprecated
171311
// #TINY-vwxyz1

0 commit comments

Comments
 (0)