Closed Bug 1263578 Opened 8 years ago Closed 8 years ago

Consider swappable carets on B2G

Categories

(Core :: DOM: Selection, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla48
Tracking Status
firefox48 --- fixed

People

(Reporter: TYLin, Assigned: TYLin)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

This is filed per bug 1168891 comment 16. After bug 1168891 is landed, Fennec will support swappable carets, which matches the convention of Android platform. And the swappable carets will become the default if user turn on "layout.accessiblecaret.enabled" on all the desktop platforms.

In the latest B2G text selection spec bug 921965, page 12, it explicitly says that the carets can't cross each other. Given the new capability of the swappable carets, is B2G still prefer the non-swappable caret? If yes, we can resolve this bug as won't fix. Otherwise we can make carets swappable on B2G as well.
NI for comment 0. This is a UX decision.
Flags: needinfo?(tchen)
I agree that swappable carets will provide better user experience. I've updated the spec(p12. dragging leftward & dragging upward part). Please check the attachment.
Flags: needinfo?(tchen) → needinfo?(tlin)
Tori, thank you for updating the spec. I'll update the code for B2G accordingly.
Assignee: nobody → tlin
Status: NEW → ASSIGNED
Flags: needinfo?(tlin)
According to the latest Firefox OS text selection spec 1.7, the carets
are now swappable.

Review commit: https://reviewboard.mozilla.org/r/46025/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/46025/
Attachment #8740795 - Flags: review?(mtseng)
Comment on attachment 8740795 [details]
MozReview Request: Bug 1263578 - Make AccessibleCaret swappable on B2G. r?mtseng

https://reviewboard.mozilla.org/r/46025/#review42525
Attachment #8740795 - Flags: review?(mtseng) → review+
https://hg.mozilla.org/mozilla-central/rev/9e62762fcc4a
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
You need to log in before you can comment on or make changes to this bug.