311553 2026-04-06 01:13:18 -0700 SVG getStartPositionOfChar/getEndPositionOfChar should not include dominant-baseline shift in returned position 2026-04-17 08:08:18 -0700 1 1 1 Unclassified WebKit SVG WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=311597 https://github.com/web-platform-tests/wpt/pull/59318 InRadar P2 Normal --- 297455 1 karlcow karlcow sabouhallawa webkit-bug-importer zimmermann oldest_to_newest 2197183 0 karlcow 2026-04-06 01:13:18 -0700 getStartPositionOfChar() and getEndPositionOfChar() return positions that include the dominant-baseline shift baked into the SVG text fragment y-coordinate. Chrome and Firefox return positions without the baseline shift, reflecting the y attribute value rather than the visual rendering position. The issue is in SVGTextLayoutEngine.cpp where the baseline shift from dominant-baseline is applied to the fragment y-position (line 603: y -= baselineShift) and stored in the fragment (line 635: fragment.y = y). The SVGTextQuery API reads directly from fragment.y, so it returns the shifted position. The fix is to store the baseline shift separately in SVGTextFragment and apply it only during painting, not in the stored position. This makes the query APIs return the correct unshifted position matching Chrome/Firefox behavior. Related: Bug 297455 (dominant-baseline inheritance fix exposes this issue more broadly) 2197184 1 webkit-bug-importer 2026-04-06 01:13:34 -0700 <rdar://problem/174145885> 2197194 2 karlcow 2026-04-06 02:11:27 -0700 Pull request: https://github.com/WebKit/WebKit/pull/62106 2201484 3 ews-feeder 2026-04-17 07:01:45 -0700 Committed 311450@main (48ca57667b1e): <https://commits.webkit.org/311450@main> Reviewed commits have been landed. Closing PR #62106 and removing active labels. 2201511 4 karlcow 2026-04-17 08:08:18 -0700 Submitted web-platform-tests pull request: https://github.com/web-platform-tests/wpt/pull/59318