Open Bug 981002 Opened 11 years ago Updated 3 years ago

cannot set background of the THUMB of <input type=range> to an image

Categories

(Core :: Layout: Form Controls, defect, P5)

x86_64
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: dima.tsurankou, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release) Build ID: 20140212131424 Steps to reproduce: set background of THUMB of <input type=range> to an image input[type=range]::-moz-range-thumb { height: 18px; width: 18px; background: url(thumb.svg) no-repeat; } Actual results: Looks like it uses the background I specify for the track Expected results: Should use proper background image
Component: DOM: Core & HTML → Layout: Form Controls
Why is ::-moz-range-thumb exposed to the web? Is this pseudo expected to become part of a standard?
Priority: -- → P5
(In reply to Mats Palmgren (:mats) from comment #1) > Why is ::-moz-range-thumb exposed to the web? To provide parity with Webkit/Blink, and because people asked for it at the time while nobody suggested we shouldn't expose it. > Is this pseudo expected to become part of a standard? That would sound like a good idea, but nobody's working on that as far as I know.
(In reply to Jonathan Watt [:jwatt] from comment #2) > To provide parity with Webkit/Blink, It's understandable that we want to keep up with the competition, but it's unfortunate since it undermines our arguments when we criticize other vendors for shipping prefixed features. Quote from our policy document: <em>Mozilla will no longer ship new "moz"-prefixed APIs</em> https://wiki.mozilla.org/WebAPI/ExposureGuidelines
Yes, that's since been pointed out before, which is (one of) the reasons the pseudo-elements for <input type=number> have not been exposed.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.