Bug 69193

Summary:

Disabled sliders are rendered incorrectly

Product:

WebKit

Reporter:

Jon Lee <jonlee>

Component:

Forms

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

ahmad.saleem792, akeerthi, ap, tkent, webkit-bug-importer

Priority:

Keywords:

HTML5, InRadar

Version:

528+ (Nightly build)

Hardware:

Mac

OS:

OS X 10.7

Attachments:

Description	Flags
Screenshot on Lion	none

Jon Lee

Reported 2011-09-30 17:15:25 PDT

They should render grayed out. Instead they look like active sliders. <rdar://problem/10081254>

Attachments
Screenshot on Lion (42.73 KB, image/png) 2011-10-01 22:52 PDT, Jon Lee	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Alexey Proskuryakov

Comment 1 2011-09-30 23:02:27 PDT

Could you please attach a screenshot? I cannot reproduce this bug on <http://www.webkit.org/projects/forms/survey.html#section-slider> with r94878 on Snow Leopard.

Jon Lee

Comment 2 2011-10-01 22:52:34 PDT

Created attachment 109417 [details] Screenshot on Lion

Jon Lee

Comment 3 2011-10-01 22:53:56 PDT

Attached screenshot. This is on Lion, r96162.

Alexey Proskuryakov

Comment 4 2011-10-04 12:40:34 PDT

I can reproduce on Snow Leopard with a newer revision now - so sounds like a recent regression.

Kent Tamura

Comment 5 2011-10-04 19:20:43 PDT

I couldn't reproduce on Snow Leopard with today's WebKit. The thumb of a disabled slider is gray, and the thumb of a enabled slider is blue. It's the expectation, right?

Jon Lee

Comment 6 2011-10-05 15:19:45 PDT

I think that's right for Snow Leopard. On Lion the track should be a lighter gray, but the button remains the same.

Ahmad Saleem

Comment 7 2024-04-10 08:29:08 PDT

I am unable to reproduce this bug: 1) https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_range_disabled or JSFiddle - https://jsfiddle.net/z9tdxou1/show Click 'Try it' and it is 'greyed out' on Safari (both macOS and iPhone). Marking this as 'RESOLVED CONFIGURATION CHANGED'.

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