|
| 1 | += {productname} 6.8.2 |
| 2 | +:navtitle: {productname} 6.8.2 |
| 3 | +:description: Release notes for {productname} 6.8.2 |
| 4 | +:keywords: releasenotes, new, changes, bugfixes |
| 5 | +:page-toclevels: 1 |
| 6 | + |
| 7 | +include::partial$misc/admon-releasenotes-for-stable.adoc[] |
| 8 | + |
| 9 | +[[overview]] |
| 10 | +== Overview |
| 11 | + |
| 12 | +{productname} 6.8.2 was released for {enterpriseversion} and {cloudname} on Wednesday, December 13^th^, 2023. These release notes provide an overview of the changes for {productname} 6.8.2, including: |
| 13 | + |
| 14 | +* xref:accompanying-premium-plugin-changes[Accompanying Premium plugin changes] |
| 15 | +* xref:bug-fixes[Bug fixes] |
| 16 | + |
| 17 | + |
| 18 | +[[accompanying-premium-plugin-changes]] |
| 19 | +== Accompanying Premium plugin changes |
| 20 | + |
| 21 | +The following premium plugin updates were released alongside {productname} 6.8.2. |
| 22 | + |
| 23 | +=== PowerPaste 6.2.4 |
| 24 | + |
| 25 | +The {productname} 6.8.2 release includes an accompanying release of the **PowerPaste** premium plugin. |
| 26 | + |
| 27 | +**PowerPaste** 6.2.4 includes the following fix. |
| 28 | + |
| 29 | +==== `white-space-collapse` CSS property was not correctly supported when pasting from Google Docs. |
| 30 | +// #TINY-9967 |
| 31 | +From major version 114, Google Chrome and Microsoft Edge added support for the CSS4 shorthand `white-space` property. The shorthand `white-space` property would be expanded into the `white-space-collapse` and `text-wrap` properties. This resulted in PowerPaste not being able to remove the `white-space-collapse` and `text-wrap` properties from the emitted content even after `white-space: pre` is removed. This issue was particularly noticeable when copying content from Google Docs. |
| 32 | + |
| 33 | +As of {productname} 6.8.2, PowerPaste now supports working with the shorthand `white-space` property by removing the expanded `white-space-collapse` and `text-wrap` properties when present from Google Docs content. |
| 34 | + |
| 35 | +For information on the **PowerPaste** plugin, see: xref:introduction-to-powerpaste.adoc[PowerPaste]. |
| 36 | + |
| 37 | + |
| 38 | +[[bug-fixes]] |
| 39 | +== Bug fixes |
| 40 | + |
| 41 | +{productname} 6.8.2 also includes the following bug fixes: |
| 42 | + |
| 43 | +=== Bespoke select toolbar buttons including `fontfamily`, `fontsize`, `blocks`, and `styles` incorrectly used plural words in their accessible names. |
| 44 | +// #TINY-10426 |
| 45 | + |
| 46 | +As of {productname} 6.8.1, the accessible labels of bespoke select toolbar buttons announced both the name of the button and the current value of the visible selected option. However, some bespoke button names, including `fontfamily`, `fontsize`, `blocks`, and `styles` have plural names, such as “Fonts”. This resulted in incorrect grammar when combined with the current value, an example being "Fonts Arial". |
| 47 | + |
| 48 | +As of {productname} 6.8.2, the accessible labels of `fontfamily`, `fontsize`, `blocks`, and `styles` bespoke buttons use singular words for the names. This results in grammatically correct labels such as “Font Arial”. |
| 49 | + |
| 50 | +=== The `align` bespoke select toolbar button had an accessible name that was misleading and grammatically incorrect in certain cases. |
| 51 | +// #TINY-10435 |
| 52 | + |
| 53 | +As of {productname} 6.8.1, the accessible label of the `align` bespoke select toolbar button announced both the name of the button, “Align”, and the currently selected value. This would result in the accessible label of the select button to be “Align left”, “Align right”, “Align center”, or “Align justify” depending on the value selected. However, the problem with the first three labels is that they are the same as the normal align toolbar buttons. This is misleading as unlike the normal align buttons, the bespoke button does not result in the aligning action, and instead opens a dropdown. The problem with “Align justify” is that the two verbs do not make grammatical sense in terms of describing the text alignment. |
| 54 | + |
| 55 | +As of {productname} 6.8.2, the name of the `align` bespoke select button is changed to “Alignment”, followed by the currently selected value. This results in the accessible labels being “Alignment left”, “Alignment right”, “Alignment center”, or “Alignment justify” depending on the value selected, which more clearly indicates the currently selected text alignment. |
| 56 | + |
| 57 | +=== Accessible names of bespoke select toolbar buttons including `align`, `fontfamily`, `fontsize`, `blocks`, and `styles` were incorrectly translated. |
| 58 | +// #TINY-10426 #TINY-10435 |
| 59 | + |
| 60 | +As of {productname} 6.8.1, the accessible labels of the bespoke select toolbar buttons announced both the name of the button and the currently selected value, for example “Block Paragraph”. However, corresponding translation strings with placeholders were not added. This resulted in the current value being translated as expected, but not the name of the button. |
| 61 | + |
| 62 | +In {productname} 6.8.2, new translation strings were added to ensure names of the bespoke select toolbar buttons are translated as well, making their accessible labels appropriately internationalized. |
| 63 | + |
| 64 | +=== Clicking inside table cells with heavily nested content could cause the browser to hang. |
| 65 | +// #TINY-10380 |
| 66 | +Previously when clicking below content that is heavily nested inside a block such as a table cell, would cause the browser to hang. |
| 67 | + |
| 68 | +{productname} 6.8.2 addresses this, by optimizing algorithm that was causing the browser to hang. |
| 69 | + |
| 70 | +As a result, the browser no longer hangs, when clicking inside table cells with heavily nested content. |
| 71 | + |
| 72 | +=== Toggling a list that contains an LI element having another list as its first child would remove the remaining content within that LI element. |
| 73 | +// #TINY-10414 |
| 74 | +In a previous xref:6.7.2-release-notes.adoc#toggling-a-list-that-contained-a-list-item-element-li-which-in-turn-contained-another-list-item-element-as-its-first-child-removed-other-content-within-the-first-list-item-element[bugfix] for lists, some element structures would not recreate the `<li>` tags when a list element was toggled using the `bullist` button in the toolbar. |
| 75 | + |
| 76 | +.Example structure |
| 77 | +[source, html] |
| 78 | +---- |
| 79 | +<li> |
| 80 | + <ul>...</ul> |
| 81 | + <something-else/> |
| 82 | +</li> |
| 83 | +---- |
| 84 | + |
| 85 | +As a consequence, any tags nested within the `<li>` would be deleted from the {productname} document, resulting in content loss for the user. |
| 86 | + |
| 87 | +{productname} 6.8.2 addresses this by improving the representation of the list to manage this case. |
| 88 | + |
| 89 | +As a result, now, when toggling `<li>` elements using the `bullist` button, content within a list is now correctly recreated the content is retained as expected. |
0 commit comments