Skip to content

Commit 63d5496

Browse files
authored
Merge branch 'feature/7.8.0/DOC-3131' into feature/7.8.0/DOC-3131_TINY-11732
2 parents ef54236 + 5f43b72 commit 63d5496

File tree

2 files changed

+87
-38
lines changed

2 files changed

+87
-38
lines changed

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

Lines changed: 53 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -97,42 +97,6 @@ In {productname} {release-version}, a new `+tinycomments_fetch_author_info+` cal
9797

9898
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Introduction to {companyname} Comments].
9999

100-
=== Image Optimizer (Powered by Uploadcare)
101-
102-
{productname} {release-version} introduces the **Image Optimizer (Powered by Uploadcare)** plugin.
103-
104-
**Image Optimizers** includes the following fix and addition.
105-
106-
=== Added support for `+uploadcare_filters+` option in the Image Optimizer (Powered by Uploadcare) plugin
107-
// #EPIC-146
108-
109-
The **Image Optimizer (Powered by Uploadcare)** plugin now includes support for a new configuration option, `+uploadcare_filters+`, introduced in {release-version}. This option allows integrators to define a customizable list of image filters available within the **Image Optimizer (Powered by Uploadcare)** dialog. Each filter can be configured with an optional `amount` parameter, controlling the intensity of the effect, and an optional `label` to customize its display name in the UI.
110-
111-
.Example
112-
[source,js]
113-
----
114-
tinymce.init({
115-
selector: "textarea",
116-
plugins: 'uploadcare',
117-
toolbar: 'uploadcare',
118-
uploadcare_public_key: '<your-public-key>',
119-
uploadcare_filters: [
120-
{ name: 'none' },
121-
{ name: 'adaris', amount: -100, label: 'Vintage Fade' },
122-
{ name: 'adaris', amount: 0, label: 'Base' },
123-
{ name: 'adaris', amount: 100, label: 'Standard' },
124-
{ name: 'zevcen', amount: 200, label: 'Glow Boost' }
125-
]
126-
});
127-
----
128-
129-
==== Keyboard navigation between toolbars no longer loses focus.
130-
// #TINY-11880
131-
132-
In previous versions of **Image Optimizer**, navigating between toolbars and sub toolbars could cause the toolbar focus state to be lost. This issue required users to press `+Ctrl+F9+` to manually restore focus to the context toolbar, disrupting keyboard navigation workflows. {productname} {release-version} addresses this issue, by updating the focus handling using new sub toolbar APIs, ensuring that focus is now properly retained when moving between toolbars and sub toolbars. This improvement enhances accessibility and allows users to navigate the toolbar system more efficiently.
133-
134-
For information on the **Image Optimizer (Powered by Uploadcare)** plugin, see xref:uploadcare.adoc[Image Optimizer (Powered by Uploadcare)].
135-
136100
=== Math
137101

138102
The {productname} {release-version} release includes an accompanying release of the **Math** premium plugin.
@@ -205,15 +169,57 @@ For more information, see: xref:exportpdf.adoc[Export to PDF].
205169

206170
=== Image Optimizer (Powered by Uploadcare)
207171

208-
{productname} {release-version} introduces the **Image Optimizer (Powered by Uploadcare)** plugin.
172+
The {productname} {release-version} release includes an accompanying release of the **Image Optimizer (Powered by Uploadcare)** premium plugin.
173+
174+
**Image Optimizers** includes the following fixes and addition.
175+
176+
=== Added support for `+uploadcare_filters+` option in the Image Optimizer (Powered by Uploadcare) plugin
177+
// #EPIC-146
209178

210-
**Image Optimizer** includes the following fix.
179+
The **Image Optimizer (Powered by Uploadcare)** plugin now includes support for a new configuration option, `+uploadcare_filters+`, introduced in {release-version}. This option allows integrators to define a customizable list of image filters available within the **Image Optimizer (Powered by Uploadcare)** dialog. Each filter can be configured with an optional `amount` parameter, controlling the intensity of the effect, and an optional `label` to customize its display name in the UI.
180+
181+
.Example
182+
[source,js]
183+
----
184+
tinymce.init({
185+
selector: "textarea",
186+
plugins: 'uploadcare',
187+
toolbar: 'uploadcare',
188+
uploadcare_public_key: '<your-public-key>',
189+
uploadcare_filters: [
190+
{ name: 'none' },
191+
{ name: 'adaris', amount: -100, label: 'Vintage Fade' },
192+
{ name: 'adaris', amount: 0, label: 'Base' },
193+
{ name: 'adaris', amount: 100, label: 'Standard' },
194+
{ name: 'zevcen', amount: 200, label: 'Glow Boost' }
195+
]
196+
});
197+
----
198+
199+
==== Dragging and dropping image files onto the placeholder was not possible if the files had the correct extension but an incorrect MIME type.
200+
// #TINY-11842
201+
202+
In previous versions of the **Image Optimizer (Powered by Uploadcare)** plugin, dragging and dropping supported image files onto the placeholder could fail due to inconsistent file type detection. The issue occurred because only the MIME type or the file extension was checked, resulting in discrepancies when handling certain image files.
203+
204+
{productname} {release-version} resolves this issue by updating file type detection to consider both the MIME type and the file extension when verifying supported formats. This enhancement ensures more reliable and consistent behavior when dragging and dropping image files.
211205

212206
=== Non-uploadcare image URLs would be altered by color adjustments even when they failed to upload.
213207
// #TINY-11761
214208

215209
Previously, applying color filters to images that had not yet been successfully uploaded to Uploadcare could result in broken image links if the server returned an error. This occurred because the original image was modified before confirming a successful upload. With this update, {productname} now preserves the original image until a successful upload is completed, ensuring that image functionality remains intact even if an upload fails. This change improves the reliability of the image upload and editing workflow in {release-version}.
216210

211+
==== Keyboard navigation between toolbars no longer loses focus.
212+
// #TINY-11880
213+
214+
In previous versions of **Image Optimizer (Powered by Uploadcare)** plugin, navigating between toolbars and sub toolbars could cause the toolbar focus state to be lost. This issue required users to press `+Ctrl+F9+` to manually restore focus to the context toolbar, disrupting keyboard navigation workflows. {productname} {release-version} addresses this issue, by updating the focus handling using new sub toolbar APIs, ensuring that focus is now properly retained when moving between toolbars and sub toolbars. This improvement enhances accessibility and allows users to navigate the toolbar system more efficiently.
215+
216+
==== Placeholder element is now responsive and adjusts to the container's width.
217+
// #TINY-11958
218+
219+
Previously, in **Image Optimizer**, the image placeholder had a fixed width, which prevented it from being responsive to different screen or container sizes. This limitation caused visual issues when the placeholder was placed inside small containers (e.g. table cells, small editors), resulting in layout inconsistencies.
220+
221+
With the release of {productname} {release-version}, this issue has been resolved. The image placeholder styles have been updated to ensure full responsiveness, allowing it to adapt seamlessly to small containers without any visual issues.
222+
217223
For information on the **Image Optimizer (Powered by Uploadcare)** plugin, see xref:uploadcare.adoc[Image Optimizer (Powered by Uploadcare)].
218224

219225
[[accompanying-premium-plugin-end-of-life-announcement]]
@@ -364,6 +370,15 @@ Previously, when the editor height was set using relative units such as `pt` or
364370

365371
Previously, the tooltip for the `blockquote` button was not translated in Hebrew. {productname} {release-version} addresses this by adding a new Hebrew translation to the tooltip for the `blockquote` button.
366372

373+
=== It wasn't possible to add comments to selected footnotes elements.
374+
// #TINY-11842
375+
376+
In previous versions of {productname}, it was not possible to add comments to footnotes (created by the xref:footnotes.adoc[Footnotes] plugin) when selecting the footnote element.
377+
378+
As a result, attempting to add a comment would result in the comment being attached to a word outside the footnote as they were not considered valid block elements.
379+
380+
{productname} {release-version} addresses this issue. Comments can now be added directly to the entire footnote element, similar to how comments are handled for figures and other comparable elements.
381+
367382

368383
[[security-fixes]]
369384
== Security fixes

modules/ROOT/pages/changelog.adoc

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,40 @@
44

55
NOTE: This is the {productname} Community version changelog. For information about the latest {cloudname} or {enterpriseversion} Release, see: xref:release-notes.adoc[{productname} Release Notes].
66

7+
== xref:7.8.0-release-notes.adoc[7.8.0 - 2025-04-9]
8+
9+
=== Added
10+
* New subtoolbar support for context toolbars.
11+
// #TINY-11748
12+
* New `extended_mathml_attributes` and `extended_mathml_elements` options.
13+
// #TINY-11756
14+
* New `onboarding` option.
15+
// #TINY-11931
16+
17+
=== Improved
18+
* Dialog menu dropdowns now close when a dialog is moved.
19+
// #TINY-11368
20+
* Focus outline was misaligned with comment card border on saving an edit.
21+
// #TINY-11329
22+
* The `editor.selection.scrollIntoView()` method now pads the target scroll area with a small margin, ensuring content doesn't sit at the very edge of the viewport.
23+
// #TINY-11786
24+
25+
=== Changed
26+
* Changed promotional text and link.
27+
// #TINY-11905
28+
29+
=== Fixed
30+
* Setting editor height to a `pt` or `em` value was ignoring min/max height settings.
31+
// #TINY-11108
32+
* Exception when pressing tab in the last cell of a non-editable table.
33+
// #TINY-11797
34+
* Exception was thrown when trying to use context form API after component was detached.
35+
// #TINY-11781
36+
* Deleting an empty block within <li> would move cursor at the end of the <li>.
37+
// #TINY-11763
38+
* Deleting an empty block that is between two lists would throw an error when all of the elements were nested inside the same <li>.
39+
// #TINY-11763
40+
741
== xref:7.7.2-release-notes.adoc[7.7.2 - 2025-03-19]
842

943
=== Fixed

0 commit comments

Comments
 (0)