You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* DOC-2501: Add explanation for Export to Word service URL version appending
* DOC-2501: Add #TINY-11115 to "Colorpicker number input fields now show an error tooltip and error icon when invalid text has been entered." entry
* DOC-2501: Move "Unnecessary `nbsp` entities were inserted when typing at the edges of inline elements." to bug fixes
* DOC-2501: Add "Accompanying Enhanced Skins & Icon Packs changes" xref to nav.adoc and 7.3-release-notes.adoc Overview
* DOC-2501: Move "Fixed JavaScript error when inserting a table using the context menu by adjusting the event order in `renderInsertTableMenuItem`."
* DOC-2501: Move "Notifications didn't position and resize properly when resizing the editor or toggling views."
* DOC-2501: Move "The pattern commands would execute even if the command was not enabled."
* DOC-2501: Move "Split button popups were incorrectly positioned when switching to fullscreen mode if the editor was inside a scrollable container."
* DOC-2501: Move "The listbox component had a fixed width and was not a responsive ui element."
* DOC-2501: Change 7.3-release-notes.adoc entry titles to match changelog.adoc
* DOC-2501: Update productminorversion in antora.yml
* DOC-2501: Add 'format-code' icon to icon_list.adoc
* DOC-2501: Update Revision History demo editor content
<h2style="text-align: center;">Welcome to the TinyMCE Revision History demo!</h2>
3
+
<h2style="text-align: center;">Welcome to the TinyMCE Revision History demo!</h2>
4
4
5
-
<h5style="text-align: center;">This demo includes <em>enterprise</em>, also known as <em>Premium</em> features.</h5>
5
+
<pstyle="text-align: center;">Try out the Revision History feature by typing in the editor and then clicking the Revision History icon in the toolbar.</p>
6
6
7
-
<h5style="text-align: center;">Try out these features as provided in this full featured example.</h5>
7
+
<pstyle="text-align: center;">And visit the <ahref="https://www.tiny.cloud/pricing">pricing page</a> to learn more about our Premium plugins.</p>
8
8
9
-
<h5style="text-align: center;">And visit the <ahref="https://www.tiny.cloud/pricing">pricing page</a> to learn more about our Premium plugins.</h5>
10
-
11
-
<h2>Got questions or need help?</h2>
12
-
13
-
<ul>
14
-
<li>Our <aclass="mceNonEditable" href="https://www.tiny.cloud/docs/tinymce/7/">documentation</a> is a great resource for learning how to configure TinyMCE.</li>
15
-
<li>Have a specific question? Try the <ahref="https://stackoverflow.com/questions/tagged/tinymce" target="_blank" rel="noopener"><code>tinymce</code> tag at Stack Overflow</a>.</li>
16
-
<li>We also offer enterprise grade support as part of <ahref="https://www.tiny.cloud/pricing">TinyMCE premium subscriptions</a>.</li>
@@ -40,37 +30,23 @@ <h2>A simple table to play with</h2>
40
30
</tbody>
41
31
</table>
42
32
33
+
<h2>Got questions or need help?</h2>
43
34
44
-
<h2>Character strings to demonstrate some of the Advanced Typography plugin’s features</h2>
45
-
46
-
<p>Select the characters in the list below and choose <strong>Tools → Typography → Enhance</strong>.</p>
47
-
48
-
<ulstyle="list-style-type: none;">
49
-
<li>Not really an arrow glyph: -></li>
50
-
<li>"Double tear-drop quotation marks and apostrophes aren't typographically elegant."</li>
51
-
<li>But they should be honored in a <code>code-fragment: "true"</code>.</li>
52
-
<li>(c) symbol</li>
53
-
<li>(tm) symbol</li>
54
-
<li>30C is 86F</li>
55
-
</ul>
56
-
57
-
<h2>Note on the included Templates demonstration</h2>
58
-
59
-
<p>The included Templates demonstration uses the <aclass="mceNonEditable" href="https://www.tiny.cloud/docs/tinymce/7/advanced-templates/#advtemplate_list"><code>advtemplate_list</code></a> configuration option to return a local promise containing a basic Template structure with self-contained examples.</p>
60
-
61
-
<p>This example allows for the loading of and interacting with the Template user-interface but cannot be used to create, edit, or save Template items.</p>
62
-
63
-
<p>See the <aclass="mceNonEditable" href="https://www.tiny.cloud/docs/tinymce/7/advanced-templates/">Templates</a> documentation for details on how to setup Templates to interact with external data sources.</p>
35
+
<ul>
36
+
<li>Our <aclass="mceNonEditable" href="https://www.tiny.cloud/docs/tinymce/7/">documentation</a> is a great resource for learning how to configure TinyMCE.</li>
37
+
<li>Have a specific question? Try the <ahref="https://stackoverflow.com/questions/tagged/tinymce" target="_blank" rel="noopener"><code>tinymce</code> tag at Stack Overflow</a>.</li>
38
+
<li>We also offer enterprise grade support as part of <ahref="https://www.tiny.cloud/pricing">TinyMCE premium subscriptions</a>.</li>
39
+
</ul>
64
40
65
-
<h2>Found a bug?</h2>
41
+
<h2>Found a bug?</h2>
66
42
67
-
<p>If you think you have found a bug please create an issue on the <ahref="https://github.com/tinymce/tinymce/issues">GitHub repo</a> to report it to the developers.</p>
43
+
<p>If you think you have found a bug please create an issue on the <ahref="https://github.com/tinymce/tinymce/issues">GitHub repo</a> to report it to the developers.</p>
68
44
69
-
<h2>Finally…</h2>
45
+
<h2>Finally…</h2>
70
46
71
-
<p>Don’t forget to check out our other product <ahref="http://plupload.com" target="_blank">Plupload</a>, your ultimate upload solution featuring HTML5 upload support.</p>
47
+
<p>Don’t forget to check out our other product <ahref="http://plupload.com" target="_blank">Plupload</a>, your ultimate upload solution featuring HTML5 upload support.</p>
72
48
73
-
<p>Thanks for supporting TinyMCE! We hope it helps you and your users create great content.</p>
49
+
<p>Thanks for supporting TinyMCE! We hope it helps you and your users create great content.</p>
{productname} {release-version} was released for {enterpriseversion} and {cloudname} on Wednesday, August 7^th^, 2024. These release notes provide an overview of the changes for {productname} {release-version}, including:
@@ -227,25 +228,14 @@ As a consequence, this resulted in the unintended inclusion of head tag content
227
228
228
229
As a result, the editor now correctly handles full document content without misplacing head elements into the body, ensuring cleaner and more accurate content loading.
229
230
230
-
=== Unnecessary `nbsp` entities were inserted when typing at the edges of inline elements.
231
-
// #TINY-10854
232
-
233
-
Previously, the replacement mechanism for `+ +` did not account for nearby elements when converting non-breaking spaces to regular spaces.
234
-
235
-
As a consequence, when typing a sequence like "a space b," the output was correct. However, if the "b" was wrapped in an inline element (such as bold), the `+ +` remained instead of being replaced.
236
-
237
-
{productname} {release-version} addresses this issue. Now, the normalization process triggers when an inline format is applied, affecting the previous sibling element to ensure spaces are properly converted.
238
-
239
-
As a result, non-breaking spaces between different inline elements are now normalized, preventing unnecessary `+ +` entities.
240
-
241
231
242
232
[[additions]]
243
233
== Additions
244
234
245
235
{productname} {release-version} also includes the following addition:
246
236
247
237
=== Colorpicker number input fields now show an error tooltip and error icon when invalid text has been entered.
248
-
// #TINY-10799
238
+
// #TINY-10799 / #TINY-11115
249
239
250
240
Previously, the color picker HEX value input field only displayed a red outline and an aria label reading "invalid data" when users entered invalid values. This lacked sufficient detail to help users correct their input.
{productname} {release-version} also includes the following bug fixes:
275
265
276
-
=== Consecutive HTML comments would in some cases generate unwanted elements.
266
+
=== Unnecessary nbsp entities were inserted when typing at the edges of inline elements.
267
+
// #TINY-10854
268
+
269
+
Previously, the replacement mechanism for `+ +` did not account for nearby elements when converting non-breaking spaces to regular spaces.
270
+
271
+
As a consequence, when typing a sequence like "a space b," the output was correct. However, if the "b" was wrapped in an inline element (such as bold), the `+ +` remained instead of being replaced.
272
+
273
+
{productname} {release-version} addresses this issue. Now, the normalization process triggers when an inline format is applied, affecting the previous sibling element to ensure spaces are properly converted.
274
+
275
+
As a result, non-breaking spaces between different inline elements are now normalized, preventing unnecessary `+ +` entities.
276
+
277
+
=== Fixed JavaScript error when inserting a table using the context menu by adjusting the event order in `renderInsertTableMenuItem`.
278
+
// #TINY-6887
279
+
280
+
Previously in {productname}, a JavaScript warning would appear when attempting to insert a table from the context menu while using both the `table` and `autoresize` plugins. This warning was caused by the `onAction` event hiding the context menu, followed by an attempt to close the already hidden context menu, resulting in the warning message:
281
+
282
+
[quote]
283
+
"Uncaught Error: The component must be in a context to send: triggerEvent is not in context."
284
+
285
+
NOTE: This warning did not impact the functionality of table insertion, but it could be confusing for users.
286
+
287
+
In {productname} {release-version}, this issue has been resolved by adjusting the order of function calls in the code. Now, the context menu is closed before the `onAction` event is triggered when inserting a table from the context menu. As a result, the table is now inserted as expected without any JavaScript warnings.
288
+
289
+
=== Notifications didn't position and resize properly when resizing the editor or toggling views.
290
+
// #TINY-10894
291
+
292
+
Previously, the function responsible for recalculating the width of notifications only added a width if the notification's width exceeded the boundaries.
293
+
294
+
As a consequence, when notifications were constrained by boundaries, an additional width was added. However, if the boundaries were later increased, the added width was not adjusted accordingly.
295
+
296
+
{productname} {release-version} addresses this issue. Now, the function adds width when the notification's width exceeds the boundaries but also removes this width when necessary.
297
+
298
+
As a result, notifications now resize correctly when the boundaries increase, ensuring their width adjusts as expected.
299
+
300
+
=== The pattern commands would execute even if the command was not enabled.
301
+
// #TINY-10994
302
+
303
+
Previously in {productname}, the `text_patterns` commands would attempt to execute even if the functionality were not supported in the current editor context. As a consequence, the command would fail and the editor would display unexpected behavior. For example, typing "1. " without the `lists` plugin enabled would delete the text instead of converting it to a list.
304
+
305
+
This issue has been resolved in {productname} {release-version}. The editor now filters `text_patterns` to only the supported commands. For example, typing "1. " without the `lists` plugin enabled will no longer fire a text pattern and instead retain the text as plain text.
306
+
307
+
=== Split button popups were incorrectly positioned when switching to fullscreen mode if the editor was inside a scrollable container.
308
+
// #TINY-10973
309
+
310
+
Previously in {productname}, there was an issue where split button popups would be positioned incorrectly when opened within a scrollable container and the editor was in `fullscreen` mode. The behavior occurred because the box constraints for the split button popup did not take the `fullscreen` mode into account when calculating the position, resulting in an incorrect placement of the popup.
311
+
312
+
In {productname} {release-version}, this issue has been fixed. The box constraints for the split button popup are now correctly calculated when the editor is in a scrollable container and in `fullscreen` mode. As a result, the split button popup is now positioned correctly.
313
+
314
+
=== Sequential html comments would in some cases generate unwanted elements.
277
315
// #TINY-10955
278
316
279
317
Previously in {productname}, consecutive HTML comments would generate unwanted elements in the editor. For example, when inserting the following HTML into the editor:
@@ -308,62 +346,25 @@ In {productname} {release-version}, this issue has been resolved. The editor now
308
346
309
347
As a result, no extra paragraphs are generated.
310
348
311
-
=== `preventDefault` on mousedown on toolbar buttons was causing misplaced focus bugs.
312
-
// #TINY-10638
313
-
314
-
In previous versions of {productname}, the `preventDefault` on mousedown in the toolbar button component caused focus issues. As a consequence, when clicking on different toolbar buttons, the focus was not updated, leaving the initial button highlighted.
315
-
316
-
{productname} {release-version} addresses this issue by removing the `preventDefault`, allowing the focus to change as expected when users click on the image controls (ie. zoom in and out).
317
-
318
349
=== The listbox component had a fixed width and was not a responsive ui element.
319
350
// #TINY-10884
320
351
321
352
Previously, the listbox component was not responsive as a UI element, due to a fixed width being applied in the `CommonDropdown` component during dialog initialization.
322
353
323
354
This issue has been resolved in {productname} {release-version} by removing the fixed width setting, allowing the listbox component to function as a responsive UI element.
324
355
356
+
=== Prevent default mousedown on toolbar buttons was causing misplaced focus bugs.
357
+
// #TINY-10638
358
+
359
+
In previous versions of {productname}, the `preventDefault` on mousedown in the toolbar button component caused focus issues. As a consequence, when clicking on different toolbar buttons, the focus was not updated, leaving the initial button highlighted.
360
+
361
+
{productname} {release-version} addresses this issue by removing the `preventDefault`, allowing the focus to change as expected when users click on the image controls (ie. zoom in and out).
362
+
325
363
=== Attempting to use focus commands on an editor where the cursor had last been in certain `+contentEditable="true"+` elements would fail.
326
364
// #TINY-11085
327
365
328
366
Previously, when `+contentEditable="true"+` (CET) fields where not wrapped in `+contentEditable="false"+` (CEF) elements, the elements did not respond properly to focus commands. As a consequence, the focus was not given to the editor as expected, leading to disruptions in user interactions.
329
367
330
368
{productname} {release-version} addresses this issue. Now, when (CET) fields are **not wrapped** in (CEF) elements, the editor directs the focus to the body of the editor first.
331
369
332
-
As a result, the editor now correctly returns focus as expected, ensuring seamless user interactions.
333
-
334
-
=== Fixed JavaScript error when inserting a table using the context menu by adjusting the event order in `renderInsertTableMenuItem`.
335
-
// #TINY-6887
336
-
337
-
Previously in {productname}, a JavaScript warning would appear when attempting to insert a table from the context menu while using both the `table` and `autoresize` plugins. This warning was caused by the `onAction` event hiding the context menu, followed by an attempt to close the already hidden context menu, resulting in the warning message:
338
-
339
-
[quote]
340
-
"Uncaught Error: The component must be in a context to send: triggerEvent is not in context."
341
-
342
-
NOTE: This warning did not impact the functionality of table insertion, but it could be confusing for users.
343
-
344
-
In {productname} {release-version}, this issue has been resolved by adjusting the order of function calls in the code. Now, the context menu is closed before the `onAction` event is triggered when inserting a table from the context menu. As a result, the table is now inserted as expected without any JavaScript warnings.
345
-
346
-
=== Notifications didn't position and resize properly when resizing the editor or toggling views.
347
-
// #TINY-10894
348
-
349
-
Previously, the function responsible for recalculating the width of notifications only added a width if the notification's width exceeded the boundaries.
350
-
351
-
As a consequence, when notifications were constrained by boundaries, an additional width was added. However, if the boundaries were later increased, the added width was not adjusted accordingly.
352
-
353
-
{productname} {release-version} addresses this issue. Now, the function adds width when the notification's width exceeds the boundaries but also removes this width when necessary.
354
-
355
-
As a result, notifications now resize correctly when the boundaries increase, ensuring their width adjusts as expected.
356
-
357
-
=== Split button popups were incorrectly positioned when switching to fullscreen mode if the editor was inside a scrollable container.
358
-
// #TINY-10973
359
-
360
-
Previously in {productname}, there was an issue where split button popups would be positioned incorrectly when opened within a scrollable container and the editor was in `fullscreen` mode. The behavior occurred because the box constraints for the split button popup did not take the `fullscreen` mode into account when calculating the position, resulting in an incorrect placement of the popup.
361
-
362
-
In {productname} {release-version}, this issue has been fixed. The box constraints for the split button popup are now correctly calculated when the editor is in a scrollable container and in `fullscreen` mode. As a result, the split button popup is now positioned correctly.
363
-
364
-
=== The pattern commands would execute even if the command was not enabled.
365
-
// #TINY-10994
366
-
367
-
Previously in {productname}, the `text_patterns` commands would attempt to execute even if the functionality were not supported in the current editor context. As a consequence, the command would fail and the editor would display unexpected behavior. For example, typing "1. " without the `lists` plugin enabled would delete the text instead of converting it to a list.
368
-
369
-
This issue has been resolved in {productname} {release-version}. The editor now filters `text_patterns` to only the supported commands. For example, typing "1. " without the `lists` plugin enabled will no longer fire a text pattern and instead retain the text as plain text.
370
+
As a result, the editor now correctly returns focus as expected, ensuring seamless user interactions.
Copy file name to clipboardExpand all lines: modules/ROOT/pages/exportword.adoc
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,10 +40,13 @@ tinymce.init({
40
40
selector: 'textarea',
41
41
plugins: 'exportword',
42
42
toolbar: 'exportword',
43
-
exportword_service_url: '<service_URL>'
43
+
exportword_service_url: 'http://localhost:8080/' // update to your own self-hosted service URL
44
44
});
45
45
----
46
46
47
+
[IMPORTANT]
48
+
The `exportword_service_url` option automatically appends `/v2/convert/html-docx` to the URL provided, so only the base URL is required. For example, if the service is hosted at `http://localhost:8080/v2/convert/html-docx`, the `exportword_service_url` option should be set to `http://localhost:8080/`.
49
+
47
50
== Options
48
51
49
52
The following configuration options affect the behavior of the {pluginname} plugin.
0 commit comments