Open Bug 1545812 Opened 6 years ago Updated 2 months ago

AccessibleCaret jumps when dragging over ::marker

Categories

(Core :: DOM: Selection, defect, P3)

68 Branch
Unspecified
Android
defect

Tracking

()

Tracking Status
firefox68 --- affected

People

(Reporter: csheany, Unassigned)

References

(Blocks 1 open bug)

Details

+++ This bug was initially created as a clone of Bug #1540545 +++

User Agent: Mozilla/5.0 (Android 7.1.1; Tablet; rv:68.0) Gecko/68.0 Firefox/68.0

Steps to reproduce:

  1. Open this bug
  2. Long press Open
  3. Drag the caret to the left

Actual results:

The top half is selected

Expected results:

To be determined

It doesn't require zooming in

Summary: Text in subframes isn't properly selected after zooming in: the sequel → Text in subframes isn't properly selected: the sequel

Does "2. Long press Open" mean "Long press on any word (such as "Open" in step 1) to make the blue caret appearing"?

Yes.

I think the key is the numbered list.

It might not be about subframes either

Component: Panning and Zooming → Selection
Summary: Text in subframes isn't properly selected: the sequel → Text isn't properly selected...

Thanks! I think this is a selection bug, and can be reproduce on desktop browser with
layout.accessiblecaret.enabled=true and layout.accessiblecaret.hide_carets_for_mouse_input=false.

By selecting the word "Open" in step 1 in comment 0, and dragging the right caret toward the auto-generated <li> ::marker "1.", the selection range jumps to somewhere unexpected.

This is likely to be an existing bug before ::marker was introduced.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P2 → P3
Summary: Text isn't properly selected... → AccessibleCaret jumps when dragging over ::marker

Additional STR...

  1. Open https://en.m.wikipedia.org/wiki/Bullet_(typography)
  2. Long press Item
    3 Drag the caret to the left

Actual results:

The bottom half is selected

Expected results:

To be determined

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.