RESOLVED FIXED 257410
AX: AXTextMarkerRangeForTextMarkersAttribute needs to support unordered TextMarkers.
https://bugs.webkit.org/show_bug.cgi?id=257410
Summary AX: AXTextMarkerRangeForTextMarkersAttribute needs to support unordered TextM...
Andres Gonzalez
Reported 2023-05-26 18:48:10 PDT
It only works when the passed TextMarkers are ordered, i.e., start < end.
Attachments
Patch (10.04 KB, patch)
2023-05-26 19:41 PDT, Andres Gonzalez
no flags
Patch (10.15 KB, patch)
2023-05-30 09:10 PDT, Andres Gonzalez
no flags
Patch (10.09 KB, patch)
2023-05-30 11:37 PDT, Andres Gonzalez
no flags
Radar WebKit Bug Importer
Comment 1 2023-05-26 18:48:23 PDT
Andres Gonzalez
Comment 2 2023-05-26 18:48:54 PDT
Radar WebKit Bug Importer
Comment 3 2023-05-26 18:49:07 PDT
Andres Gonzalez
Comment 4 2023-05-26 19:41:48 PDT
Andres Gonzalez
Comment 5 2023-05-26 19:52:38 PDT
Andres Gonzalez
Comment 6 2023-05-30 09:10:37 PDT
Andres Gonzalez
Comment 7 2023-05-30 11:37:00 PDT
chris fleizach
Comment 8 2023-05-31 07:40:33 PDT
Comment on attachment 466536 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=466536&action=review > Source/WebCore/accessibility/AXTextMarker.cpp:290 > + auto startBoundaryPoint = marker1.boundaryPoint(); are these pointers? should they be auto*
Andres Gonzalez
Comment 9 2023-05-31 08:39:56 PDT
(In reply to chris fleizach from comment #8) > Comment on attachment 466536 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=466536&action=review > > > Source/WebCore/accessibility/AXTextMarker.cpp:290 > > + auto startBoundaryPoint = marker1.boundaryPoint(); > > are these pointers? should they be auto* No, std::optional.
EWS
Comment 10 2023-05-31 11:03:42 PDT
Committed 264742@main (b37f820dae2a): <https://commits.webkit.org/264742@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 466536 [details].
Note You need to log in before you can comment on or make changes to this bug.