Bug 17193

Summary: Attributes of <input type=range> not accessable from javascript
Product: WebKit Reporter: Sascha <saschast>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ap, ddkilzer, ian, joepeck, phistuck, thorton, wenson_hsieh
Priority: P2 Keywords: HasReduction
Version: 523.x (Safari 3)   
Hardware: All   
OS: All   
See Also: https://bugs.webkit.org/show_bug.cgi?id=202859
Attachments:
Description Flags
test of min/max attributes of <input type=range> element none

Sascha
Reported 2008-02-06 04:50:35 PST
The min and max attributes of the <input type=range> element can not read from a javascript. Make somthing like this: a = input_el.min; it only return "undefined" I have this tested and confirmed on 10.4.11 Safari3, Win XP Safari3beta and Win XP Safari3beta +Nightly r29908 I think internaly it is used because if youset the element's value to a out-of-bound the value is set to the min/max boundary.
Attachments
test of min/max attributes of <input type=range> element (734 bytes, text/html)
2008-02-06 04:52 PST, Sascha 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Sascha
Comment 1 2008-02-06 04:52:35 PST
Created attachment 18959 [details] test of min/max attributes of <input type=range> element
Sascha
Comment 2 2008-02-06 05:12:43 PST
Additional Info: This problem also leads to a not functionality in Safaris RSS viewer. If you cklick the images on left/right of the scale slider result in no reaction. I have made a little patch on my own Safari (windows) and it works. I only add a test if the attribute is set or initalize it with it boundaries. File: Articles.js Location on Windows: Safari/PubSub.resources/Articles.js Patch: 1171,1172d1170 < if (slider.min == undefined) < slider.min = 0; 1177,1178d1174 < if (slider.max == undefined) < slider.max = 100;
Alexey Proskuryakov
Comment 3 2008-02-06 05:41:35 PST
Why is this a bug? HTMLInputElement interface definition does not specify that these attributes should be available as properties AFAICT. One can use getAttribute() and related DOM methods to manipulate element attributes.
Alexey Proskuryakov
Comment 4 2008-02-06 05:52:49 PST
(In reply to comment #2) > This problem also leads to a not functionality in Safaris RSS viewer. Thank you! Filed as <rdar://problem/5727306>.
David Kilzer (:ddkilzer)
Comment 5 2008-07-22 14:11:42 PDT
Web Forms 2.0 doesn't mention anything about including "min" and "max" as DOM attributes: http://www.whatwg.org/specs/web-forms/current-work/#ranges
Joseph Pecoraro
Comment 6 2010-03-17 17:54:09 PDT
This now works correctly if you have explicitly provided min/max attribute values. However, it doesn't seem to work with the defaults, which are 0 and 100 for an <input type=range>. I am going to leave this open for that reason.
PhistucK
Comment 7 2019-10-10 10:29:59 PDT
I think this can be closed. When not explicitly specifying the min and max, all of the browsers I tested (Firefox, Safari and Chrome) behave the same - min and max have empty strings as their values. On the other hand, a bit unrelated, you may want to port this patch perhaps - https://bugs.chromium.org/p/chromium/issues/detail?id=852938#c7
David Kilzer (:ddkilzer)
Comment 8 2019-10-11 10:48:33 PDT
(In reply to PhistucK from comment #7) > I think this can be closed. When not explicitly specifying the min and max, > all of the browsers I tested (Firefox, Safari and Chrome) behave the same - > min and max have empty strings as their values. > > On the other hand, a bit unrelated, you may want to port this patch perhaps - > https://bugs.chromium.org/p/chromium/issues/detail?id=852938#c7 Could you file a separate bug for the UI not updating when calling setAttribute()?
PhistucK
Comment 9 2019-10-11 11:55:46 PDT
Done. Bug 202859. This one can be closed.
Note You need to log in before you can comment on or make changes to this bug.