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
Copy file name to clipboardExpand all lines: modules/ROOT/pages/7.6.1-release-notes.adoc
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,6 +101,22 @@ In {productname} {release-version}, this issue has been resolved by ensuring the
101
101
102
102
For information on the **Enhanced Table** plugin, see: xref:advtable.adoc[Enhanced Tables].
103
103
104
+
=== Image Optimizer
105
+
106
+
The {productname} {release-version} release includes an accompanying release of the **Image Optimizer** premium plugin.
107
+
108
+
**Image Optimizer** includes the following fixes.
109
+
110
+
==== Images with existing `srcset` were not handled correctly.
111
+
112
+
An issue was identified where images with an existing `srcset` attribute containing an Uploadcare URL were being processed incorrectly.
113
+
114
+
The problem occurred when attempting to update an `srcset` attribute that did not contain an Uploadcare URL. In such cases, no changes were applied, resulting in the image failing to update if the existing `srcset` had a different structure.
115
+
116
+
{productname} {release-version} resolves this issue by exclusively targeting `srcset` attributes with Uploadcare URLs. This ensures that all relevant images are updated correctly, with the `srcset` being regenerated from scratch to incorporate any modifications made.
117
+
118
+
For information on the **Image Optimizer** plugin, see: xref:uploadcare.adoc[Image Optimizer].
@@ -191,6 +207,15 @@ Previously, an issue was identified in Google Chrome and Microsoft Edge where te
191
207
192
208
{productname} {release-version} addresses this issue, by updating the logic for handling text input on non-editable elements to include support for form elements. As a result, text can now be successfully inserted into form elements in Google Chrome and Microsoft Edge.
193
209
210
+
=== Opening a notification when the toolbar is at the bottom threw an error.
211
+
// #TINY-11498
212
+
213
+
An issue was identified in the inline mode editor where, if the toolbar was positioned at the bottom of the screen, a UI error occurred that rendered notifications non-functional after being opened.
214
+
215
+
This issue significantly impacted the user experience, preventing users from interacting with the notification interface effectively.
216
+
217
+
{productname} {release-version} resolves this issue by enhancing the notification positioning logic to account for the toolbar's location. Notifications now function seamlessly, regardless of the toolbar's placement on the screen.
0 commit comments