Consider hand-rolling radios and checkboxes for resizability

UNCONFIRMED
Unassigned

Status

()

enhancement
P3
normal
UNCONFIRMED
4 years ago
3 years ago

People

(Reporter: robin, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: tpi:+)

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
In bug 394892 Markus Stange fixed radios and checkboxes to use native Cocoa widgets and made them resizable, which puts Firefox a step up from where Chrome and Safari currently are. It’s a shame though that they look pixellated at large sizes (see attached image).

In the intervening time an @2x set of image states for checkboxes and radios has been introduced (try setting transform:scale(2); against an input in Chrome or Safari) which would be a stop-gap, but it would be very nice if this could be resolution independent.

Other browsers (for example Chrome on Windows) have their own set of vector widgets including checkboxes and radios. Is this something Mozilla would be interested in doing? It would obviously be better if OS X introduced resolution independent controls and I’d imagine it can’t be far off, so that might be the better path.
(Reporter)

Comment 1

4 years ago

Updated

3 years ago
Component: Widget: Cocoa → Theme
Product: Core → Firefox

Comment 2

3 years ago
Firefox :: Theme doesn't control web checkboxes / radio buttons. We potentially could use hardcoded images on the widget side. I don't know that we want to. Markus, thoughts?
Component: Theme → Widget: Cocoa
Flags: needinfo?(mstange)
Product: Firefox → Core
Yeah, it's a long standing problem, and I don't know what we should do about it. I was hoping somebody would just come along with a solution and tell us what to do. :-)
We can handroll drawing, sure, but that means we lose the native look on every platform/theme combination that we didn't handroll drawing for. I don't know whether that trade-off is worth it.
Flags: needinfo?(mstange)

Updated

3 years ago
Priority: -- → P3
Whiteboard: tpi:+
You need to log in before you can comment on or make changes to this bug.