NEW 242861
REGRESSION (Safari 15.4): SVG Text Selection not usable due to selection rect not positioned properly, affects Internet Archive books
https://bugs.webkit.org/show_bug.cgi?id=242861
Summary REGRESSION (Safari 15.4): SVG Text Selection not usable due to selection rect...
Drini Cami
Reported 2022-07-18 08:58:55 PDT
Created attachment 460975 [details] Sample HTML with SVG for reproducing the error To Repro: 1. Go on an iPhone with Safari 15.4 or 15.5 2. Visit the attached file 3. Long press on "selecting" Expected: A blue rectangle with handles appears over the word "selecting" (This is what happens in Safari 15.3) Actual: A blue rectangle appears at the top of the SVG (Safari 15.4, 15.5) Note this is similar to https://bugs.webkit.org/show_bug.cgi?id=108837 , but not the same. This is happening for *all* SVGs, not just certain viewports/scalings of SVGs.
Attachments
Sample HTML with SVG for reproducing the error (173 bytes, text/html)
2022-07-18 08:58 PDT, Drini Cami
no flags
Photos showing behaviour in Safari 15.3, 15.4, and 15.5 (150.87 KB, image/png)
2022-07-18 09:06 PDT, Drini Cami
no flags
Drini Cami
Comment 1 2022-07-18 09:06:33 PDT
Created attachment 460976 [details] Photos showing behaviour in Safari 15.3, 15.4, and 15.5
Drini Cami
Comment 2 2022-07-18 09:10:35 PDT
This has currently broken our text selection mechanism on Internet Archive books. We're getting user complaints about being unable to select text after users updated their iOS devices. Eg In other browsers and Safari 15.3, you can long press on a word to select it here: https://archive.org/details/goodytwoshoes00newyiala/page/n1/mode/1up .
Alexey Proskuryakov
Comment 3 2022-07-18 17:48:21 PDT
This reproduces on macOS too, including with STP 149.
Radar WebKit Bug Importer
Comment 4 2022-07-19 08:38:26 PDT
Ahmad Saleem
Comment 5 2023-05-21 17:19:01 PDT
I think this seems to work fine now in Safari 16.5. @ap - can you reconfirm my testing, I checked on iPhone 13 Pro Max as well with this test case and long press on 'Selecting' works.
Note You need to log in before you can comment on or make changes to this bug.