1867287 - m.hani.co.kr - Enabling accessibility apps triggers text select handle to jump unexpectedly when dragging across paragraphs

Status: RESOLVED DUPLICATE of bug 1849398

(Core :: DOM: Selection, defect)

Description

[Raul Bucata]

From github: https://github.com/webcompat/web-bugs/issues/129990.

<!-- @browser: Firefox Mobile 120.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 13; Mobile; rv:120.0) Gecko/120.0 Firefox/120.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @extra_labels: browser-fenix -->

URL: https://m.hani.co.kr/arti/economy/marketing/955723.html

Browser / Version: Firefox Mobile 120.0
Operating System: Android 13
Tested Another Browser: Yes Chrome

Problem type: Something else
Description: text select handle jumps unexpectedly when draging across paragraphs
Steps to Reproduce:

1. select any words in the news article with long click.
2. drag the text select handle across the paragraphs, i.e., to the next paragraph.
3. boom. text select handle jumps to the unexpected position. i.e., I draged it to the next paragraph but the handle goes to the beginning of the page.
   <details>
   <summary>View the screenshot</summary>
   <img alt="Screenshot" src="https://webcompat.com/uploads/2023/11/6f1d7dcc-93b6-49ad-8b57-5483b621fe06.jpeg">
   </details>

<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>buildID: 20231110091750</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

View console log messages

From webcompat.com with ❤️

Change performed by the Move to Bugzilla add-on.

Comment 1

[Raul Bucata]

The issue was reported via the webcompat.com reporter. Since the issue is related to the browser, we have moved the issue. Please feel free to move the issue to the correct Product and Component.

Comment 2

[Makoto Kato [:m_kato]]

This seems to be accessible caret issue.

Comment 3

[James Teh [:Jamie]]

Eitan, do you think this could possibly be related to bug 1849398? This one has been classified as a DOM selection issue, but it's interesting that it only occurs with an accessibility service running.

Maybe it's not related to scrolling, but do we ever mess with the caret or selection when we fire accessibility events?

Comment 4

[Eitan Isaacson [:eeejay]]

I just did some mozregression bisecting and I do believe bug 1849398 fixes this. Going to close as dup.