Bug 2062388 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

STR:
1. View a chat conversation on X/Twitter in Firefox for Android, as described in 1990445 comment 0.  Or, view youtube comments as described in bug 2011231 comment 0.
2. Long-press a word in a chat-message (or youtube comment) to select that word. (Note, this can only be done in builds after bug 1998331 landed.)
3. Click-and-drag the end-of-selection accessible-caret to try to broaden the selection to include some later word/words.

ACTUAL RESULTS:
As you drag the caret, the selection oscillates between...
- the "correct" selection (from the start to the point-where-you've dragged it)
- a sort of inverse selection (not quite the inverse), from the start of the document up to the "start" selection marker.

It seems like the caret that you're dragging gets intermittently snapped to the start of the document, creating a giant selection that causes the whole page to get highlighted and flicker.  And if you drop the caret at the "wrong time", then this is literally the selection that you end up with.

EXPECTED RESULTS:
No such weird oscillation/jumping.

This means bug 1990445 and bug 2011231 are still not-quite-fixed -- they work better now, but the selection has this weird bad-effect instead of previously being impossible.
STR:
1. View a chat conversation on X/Twitter in Firefox for Android, as described in 1990445 comment 0.  Or, view youtube comments as described in bug 2011231 comment 0.
2. Long-press a word in a chat-message (or youtube comment) to select that word. (Note, this can only be done in builds after bug 1998331 landed.)
3. Click-and-drag the end-of-selection accessible-caret to try to broaden the selection to include some later word/words.

ACTUAL RESULTS:
As you drag the caret, the selection oscillates between...
- the "correct" selection (from the start to the point-where-you've dragged it)
- a sort of inverse selection (not quite the inverse), from the start of the document up to the "start" selection marker.

It seems like the caret that you're dragging gets intermittently snapped to the start of the document, creating a giant selection that causes the whole page to get highlighted and flicker.  And if you drop the caret at the "wrong time", then this is literally the selection that you end up with.

EXPECTED RESULTS:
No such weird oscillation/jumping.

This means bug 1990445 and bug 2011231 are still not-quite-fixed -- it's at least possible to select text now, but the selection behavior is pretty weird and might not get the region that you're intending.
STR:
1. View a chat conversation on X/Twitter in Firefox for Android, as described in bug 1990445 comment 0.  Or, view youtube comments as described in bug 2011231 comment 0.
2. Long-press a word in a chat-message (or youtube comment) to select that word. (Note, this can only be done in builds after bug 1998331 landed.)
3. Click-and-drag the end-of-selection accessible-caret to try to broaden the selection to include some later word/words.

ACTUAL RESULTS:
As you drag the caret, the selection oscillates between...
- the "correct" selection (from the start to the point-where-you've dragged it)
- a sort of inverse selection (not quite the inverse), from the start of the document up to the "start" selection marker.

It seems like the caret that you're dragging gets intermittently snapped to the start of the document, creating a giant selection that causes the whole page to get highlighted and flicker.  And if you drop the caret at the "wrong time", then this is literally the selection that you end up with.

EXPECTED RESULTS:
No such weird oscillation/jumping.

This means bug 1990445 and bug 2011231 are still not-quite-fixed -- it's at least possible to select text now, but the selection behavior is pretty weird and might not get the region that you're intending.

Back to Bug 2062388 Comment 0