Open Bug 1271728 Opened 9 years ago Updated 3 years ago

Show a circle cursor when touch simulation is enabled in RDM

Categories

(DevTools :: Responsive Design Mode, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: hholmes, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

(Whiteboard: [multiviewport] [reserve-rdm])

Attachments

(1 file)

Chrome currently uses a circle cursor when you have a device selected. I think this is to drive home the idea that on a phone someone would be using touch events and to reiterate that the tap space needs to be > 45px as thumbs are larger than mice cursors. Should we use this same cursor in our responsive design mode?
Whiteboard: [multiviewport] [mvp-rdm]
Switching to triage first so we figure what to remove from MVP if needed.
Whiteboard: [multiviewport] [mvp-rdm] → [multiviewport][triage]
Flags: qe-verify+
Priority: -- → P3
Whiteboard: [multiviewport][triage] → [multiviewport] [reserve-rdm]
QA Contact: mihai.boldan
Assignee: nobody → bchabod
Status: NEW → ASSIGNED
Priority: P3 → P2
Okay, just an update on this bug: Chrome doesn't just use a circle cursor to remind designers that thumbs are less precise than mice cursors, they also enable what used to be called "event fluffing" in B2G. Basically, any element inside the radius of the circle can be clicked, even if it's not exactly where the mouse is. This is controlled by touch-radius and mouse-radius preferences in Firefox, and I think it would be reasonable to turn this on along with the circle cursor for RDM, at least when touch simulation is enabled. Using the preferences correctly, it can target click events synthesised by touch events only, so it wouldn't be harmful to turn it on for the whole browser. Helen, what is your opinion on this? Does it fit in RDM's UX?
Flags: needinfo?(hholmes)
(In reply to Benoit Chabod [:bigben] from comment #2) > Okay, just an update on this bug: Chrome doesn't just use a circle cursor to > remind designers that thumbs are less precise than mice cursors, they also > enable what used to be called "event fluffing" in B2G. > > Basically, any element inside the radius of the circle can be clicked, even > if it's not exactly where the mouse is. This is controlled by touch-radius > and mouse-radius preferences in Firefox, and I think it would be reasonable > to turn this on along with the circle cursor for RDM, at least when touch > simulation is enabled. Using the preferences correctly, it can target click > events synthesised by touch events only, so it wouldn't be harmful to turn > it on for the whole browser. > > Helen, what is your opinion on this? Does it fit in RDM's UX? I think it does. Makes a lot of sense, and I think it's what users are expecting when they have the circle cursor enabled.
Flags: needinfo?(hholmes)
(In reply to Helen V. Holmes (:helenvholmes) (:✨)(pls ni?) from comment #3) > I think it does. Makes a lot of sense, and I think it's what users are > expecting when they have the circle cursor enabled. Alright! I'll move forward with this as soon as bug 1285566 has landed, since the touch simulator is being refactored over there.
Depends on: 1285566
Priority: P2 → P3
Since Benoit's internship has ended, I am going to assume he may not be working on this anymore. If that's incorrect, feel free to pick it up again!
Assignee: be.chabod → nobody
Status: ASSIGNED → NEW
I assume this only makes sense when bug 1282089 is fixed. Sebastian
Severity: normal → enhancement
Depends on: 1282089
Summary: Should we use a circle cursor when a device is selected? → Show a circle cursor when on RDM
Attached image touchCircle.svg
I've created a circle cursor, which can be used for this purpose. Sebastian
Product: Firefox → DevTools
Summary: Show a circle cursor when on RDM → Show a circle cursor when touch simulation is enabled in RDM
Assignee: nobody → mtigley
Status: NEW → ASSIGNED

I appreciate you assigned this bug to yourself, Micah! But as I wrote in comment 7, I think a circular cursor just makes sense together with a mobile behavior. And bug 1282089 comment 6 sounded like the patch there was already in a good shape. So, maybe you could finish that up first?

Sebastian

Thank you for pointing out the work already done, Sebastian! I agree this would make sense to have with bug1282089, so I'll unassign myself from this for now and investigate what needs to be done for that other patch.

Status: ASSIGNED → NEW
Assignee: mtigley → nobody
Depends on: 128556, 1501939, 1565529, 1556962, 1625925
No longer depends on: 1285566
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: