Skip to content

Commit 4afbd69

Browse files
Merge branch 'feature/7.7.0/DOC-3132' into feature/7.7.0/DOC-3132_TINY-11602
2 parents 3c56c9e + 5ea58d2 commit 4afbd69

File tree

4 files changed

+99
-1
lines changed

4 files changed

+99
-1
lines changed

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ tinymce.init({
1616
left: "1in",
1717
right: "1in"
1818
}
19-
}
19+
},
20+
watermark: {
21+
source: 'http://moxiecode.cachefly.net/tinymce/v9/images/logo.png',
22+
washout: true
23+
},
2024
}
2125
});

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

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,20 @@ include::partial$misc/admon-releasenotes-for-stable.adoc[]
2424

2525
The following premium plugin updates were released alongside {productname} {release-version}.
2626

27+
=== Export to Word
28+
29+
The {productname} {release-version} release includes an accompanying release of the **Export to Word** premium plugin.
30+
31+
**Export to Word** includes the following fix.
32+
33+
==== A document watermark can now be specified for the exported file
34+
35+
Previously, the **Export to Word** premium plugin did not support watermarks, preventing integrators from adding them to exported Word documents.
36+
37+
With the release of {productname} {release-version} watermark functionality has been introduced, enabling watermarks to be included in exported documents.
38+
39+
For information on the **Export to Word** plugin, see: xref:exportword.adoc[Export to Word].
40+
2741
=== Advanced Typography
2842

2943
The {productname} {release-version} release includes an accompanying release of the **Advanced Typography** premium plugin.
@@ -52,8 +66,56 @@ Previously, in the **Comments** premium plugin, an issue was identified where me
5266

5367
{productname} {release-version} resolves this issue by ensuring that newly added mentions to an existing comment are displayed correctly.
5468

69+
==== Pressing Keyboard shorctut `cmd+alt+m` when cursor is on annotated content now opens and focuses the reply textarea.
70+
// #TINY-11321
71+
72+
Previously, an issue was identified where pressing the keyboard shortcut `cmd-alt-m` on Mac and `ctrl-alt-m` on Windows while the cursor was on annotated content and the comments sidebar was open resulted in the focus shifting to the corresponding comment, which was not the desired behavior.
73+
74+
{productname} {release-version} fixes this by ensuring that the focus now moves to the reply text area instead of the corresponding comment.
75+
This matches the behavior when the "Add New Comment" button is clicked, resulting in more consistent functionality.
76+
77+
==== Improved visual separation of comments side panel header.
78+
// #TINY-11715
79+
80+
In previous versions of **Comments**, the side panel header blended into the body, resulting in a lack of visual separation. This made the UI appear less polished and dimensional.
81+
82+
{productname} {release-version} improves this by enhancing the side panel header’s visibility, creating a clearer distinction from the body, and refining the overall UI aesthetics.
83+
5584
For information on the **Comments** plugin, see: xref:introduction-to-tiny-comments.adoc[Comments].
5685

86+
=== Image Optimizer
87+
88+
The {productname} {release-version} release includes an accompanying release of the **Image Optimizer** premium plugin.
89+
90+
**Image Optimizer** includes the following fixes and improvements.
91+
92+
==== Some image file extensions would sometimes be incorrectly considered unsupported.
93+
// #TINY-11668
94+
95+
Previously, an issue was identified where `.jfi` and `.jif` file extensions were incorrectly considered unsupported due to the validation logic.
96+
97+
As a result, these extensions were blocked, and users encountered the error message: "Failed to upload: The image is not a supported file format."
98+
99+
{productname} {release-version} resolves this issue by fixing the validation logic to correctly detect the MIME type of uploaded images, ensuring that users can now successfully upload `.jfi` and `.jif` files.
100+
101+
==== Dropping files on the placeholder would sometimes insert the image in an incorrect location.
102+
// #TINY-11643
103+
104+
Previously, an issue was identified where the drag-and-drop functionality on an image placeholder in a table would insert the image outside of the table cell.
105+
This resulted in unpredictable behavior when users dragged and dropped an image into the image placeholder.
106+
107+
{productname} {release-version} resolves this issue by making it so that that the image placeholder handles the drop event instead of the editor content element. This improvement provides predictable and consistent drag-and-drop behavior for image placeholders in **Image Optimizer**.
108+
109+
==== Some error messages are now more descriptive.
110+
// #TINY-11613
111+
112+
Previously, error messages were unclear when the `uploadcare_public_key` was not configured with a valid API key.
113+
This caused confusion in identifying the problem during setup.
114+
115+
{productname} {release-version} addresses this by providing a more detailed error message when the `uploadcare_public_key` is not configured.
116+
117+
For information on the **Image Optimizer** plugin, see: xref:uploadcare.adoc[Image Optimizer].
118+
57119
[[improvements]]
58120
== Improvements
59121

@@ -107,6 +169,13 @@ the help dialog would not open if the plugin was disabled, leading to confusion.
107169

108170
{productname} {release-version} addresses this issue by ensuring that if the help plugin is disabled, the screen reader announces only "Rich Text Area." If the help plugin is enabled, the screen reader announces "Rich Text Area. Press `ALT-0` for help.".
109171

172+
=== Toolbar groups had both a `title` attribute and a custom tooltip, causing overlapping tooltips
173+
// #TINY-11768
174+
175+
In previous versions of {productname}, hovering over toolbar menu item would display both a custom tooltip and the default browser tooltip. This caused confusing behavior, as the custom tooltip was difficult to read due to the browser tooltip overlapping it.
176+
177+
{productname} {release-version} resolves this issue by replacing the `title` attribute with the `aria-label` attribute for toolbar groupings, preventing the default browser tooltip from appearing.
178+
110179
[[known-issues]]
111180
== Known issues
112181

modules/ROOT/pages/exportword.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,8 @@ include::partial$configuration/exportword_converter_options.adoc[leveloffset=+1]
7777

7878
include::partial$configuration/exportword_converter_style.adoc[leveloffset=+1]
7979

80+
include::partial$configuration/exportword_watermark.adoc[leveloffset=+1]
81+
8082
== Commands
8183

8284
The {pluginname} plugin provides the following {productname} commands.
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
[[watermark]]
2+
== `watermark`
3+
4+
The `watermark` option provides integrators with a way to include semi-transparent image watermarks on each page of the exported document, which can be useful for branding, copyright protection, or decorative purposes.
5+
6+
*Type:* `+Object+`
7+
8+
=== Example : using `watermark`
9+
10+
[source,js]
11+
----
12+
tinymce.init({
13+
selector: "textarea",
14+
plugins: ['exportword'],
15+
toolbar: 'exportword',
16+
exportword_converter_options: {
17+
watermark: {
18+
source: 'http://moxiecode.cachefly.net/tinymce/v9/images/logo.png',
19+
washout: true,
20+
}
21+
}
22+
});
23+
----

0 commit comments

Comments
 (0)