Bug 273469 – REGRESSION (Safari 17): getRangeAt(0) returns the same JS object even after selection changes, differs from Chrome and Firefox

• Status: RESOLVED
• Resolution: FIXED
• Component: HTML Editing

Hi, a new change in selection and range API has broken my code for a custom find feature in the latest Safari v17.

When I use the window.getSelection().getRangeAt(0) on Safari v16, I get new range objects whenever the selection changes.

But in the latest Safari v17,  window.getSelection().getRangeAt(0) returns always the same range object (updated with new data).

This behavior differs from any other browser on windows, linux or mac.

Sharing an example snippet here: https://jsfiddle.net/zb85nhx6/1/.
Trying running this in different browsers and check the console.

This took of lot of debugging to figure out why my code was broken for only latest Safari on Mac.

Kindly either fix this behavior to make it seamless with other browsers, or provide an API to turn off live ranges.

[Alexey Proskuryakov]

Interestingly, Chrome has the same behavior with window.getSelection(), the returned object is always the same. But getRangeAt(0) is different when the selection changes.

[Radar WebKit Bug Importer]

<rdar://problem/127314280>

[Ryosuke Niwa]

Created attachment 473098 [details]
Reduction

[Ryosuke Niwa]

Pull request: https://github.com/WebKit/WebKit/pull/36032

[EWS]

Committed 285996@main (d187066ee9b0): <https://commits.webkit.org/285996@main>

Reviewed commits have been landed. Closing PR #36032 and removing active labels.

[EWS]

Committed 283286.581@safari-7620-branch (cddad120f97e): <https://commits.webkit.org/283286.581@safari-7620-branch>

Reviewed commits have been landed. Closing PR #2396 and removing active labels.