Open Bug 978320 Opened 6 years ago Updated Last year

Enable styling of input[type=number] pseudo elements (spin buttons) for content

Categories

(Core :: Layout: Form Controls, enhancement)

30 Branch
enhancement
Not set

Tracking

()

REOPENED

People

(Reporter: ntim, Unassigned)

References

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

Details

Now that the number input implementation is stable, we should consider enabling the pseudo elements for content.

A good place to start : bug 930010
Blocks: number-input
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Flags: needinfo?(jwatt)
The reason that they're disabled is because Simon Sapin thought we might be able to do things a better way, perhaps using Web Components. Since Web Components aren't complete enough to play with for this use case yet it's hard to know if that will work or not.
Flags: needinfo?(jwatt)
I don’t know if Web Components are the right approach or not, but was there any discussions of this in a standards body? Please consider https://wiki.mozilla.org/WebAPI/ExposureGuidelines before exposing new features to the Web.
Severity: normal → enhancement
Component: Layout: Form Controls → CSS Parsing and Computation
Is there a spec for this? Should we make one?
Flags: needinfo?(dbaron)
I don't know of a spec for this, but it seems like if we want to expose them to content, there ought to be a spec.  (Do other browsers implement them?)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(dbaron)
Depends on: 926412
Duplicate of this bug: 1175824
Summary: Enable input[type=number] pseudo elements for content → Enable styling of input[type=number] pseudo elements (spin buttons) for content
See Also: → 947365
Component: CSS Parsing and Computation → Layout: Form Controls
This'd be a great feature since native buttons look terribly on "transform:scale(3);", at least on Win7
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Is Firefox the only major browser that doesn't support `::-webkit-inner-spin-button` today?
(In reply to James B from comment #8)
> Is Firefox the only major browser that doesn't support
> `::-webkit-inner-spin-button` today?

::-webkit-inner-spin-button is a propriatary pseudo-class only supported by Chrome, Opera, and Safari due to their common engine history.

(In reply to David Baron :dbaron: 🇫🇷 ⌚UTC+2 from comment #4)
> I don't know of a spec for this, but it seems like if we want to expose them
> to content, there ought to be a spec.  (Do other browsers implement them?)

Webkit and Blink support the pseudo-class mentioned above as well as ::-webkit-outer-spin-button[1] and ::-webkit-textfield-decoration-container, respectively.

As far as I know, only CSS UI 4 specifies[3] some styling for form elements, but explicitly doesn't define any input specific styling like special pseudo-elements.

Sebastian

[1] https://developer.mozilla.org/en-US/docs/Web/CSS/::-webkit-inner-spin-button
[2] https://developer.mozilla.org/en-US/docs/Web/CSS/::-webkit-outer-spin-button
> only supported by Chrome, Opera, and Safari

Ah, but I just checked and IE / Edge don't support spinner controls (arrows) at all, so that means FF is the only major browser that a) has spinners and b) doesn't let you style them explicitly.  Combine that with bug 1158435 and you have number field controls that are worse than nothing for some users.

I've seen other feature requests kept open because Firefox wants parity with the competition.  Does that apply here?
(In reply to James B from comment #10)
> > only supported by Chrome, Opera, and Safari
> 
> I've seen other feature requests kept open because Firefox wants parity with
> the competition.  Does that apply here?

I'm not a Mozilla employee, so I can't speak for them, though I guess this bug is kept open simply because of the need for styling this form field, not necessarily to catch up with other browsers.

Sebastian
You need to log in before you can comment on or make changes to this bug.