<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>19073</bug_id>
          
          <creation_ts>2012-09-25 22:25:49 +0000</creation_ts>
          <short_desc>WF3: Allow two handles on input type=&quot;range&quot;, like this: http://jqueryui.com/demos/slider/#range</short_desc>
          <delta_ts>2013-01-30 07:51:08 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>HTML WG</product>
          <component>HTML5 spec</component>
          <version>unspecified</version>
          <rep_platform>Other</rep_platform>
          <op_sys>other</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>REMIND</resolution>
          
          <see_also>https://www.w3.org/Bugs/Public/show_bug.cgi?id=13154</see_also>
          <bug_file_loc>http://www.whatwg.org/specs/web-apps/current-work/#top</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P5</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>contributor</reporter>
          <assigned_to name="This bug has no owner yet - up for the taking">dave.null</assigned_to>
          <cc>ayg</cc>
    
    <cc>cmhjones</cc>
    
    <cc>ian</cc>
    
    <cc>jackalmage</cc>
    
    <cc>jonas</cc>
    
    <cc>mike</cc>
    
    <cc>public-html-admin</cc>
    
    <cc>public-html-wg-issue-tracking</cc>
          
          <qa_contact name="HTML WG Bugzilla archive list">public-html-bugzilla</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>74527</commentid>
    <comment_count>0</comment_count>
    <who name="">contributor</who>
    <bug_when>2012-09-25 22:25:49 +0000</bug_when>
    <thetext>This was was cloned from bug 13154 as part of operation REMIND convergence.
Originally filed: 2011-07-06 01:10:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2011-07-06 01:10:15 +0000 
--------------------------------------------------------------------------------
Specification: http://www.w3.org/TR/html5/spec.html
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
Please give developers the ability to use two handles on input type=&quot;range&quot;,
like this: http://jqueryui.com/demos/slider/#range

This feature is very important when the user must enter two boundary values
​​of the interval.

Posted from: 95.31.9.93
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
================================================================================
 #1   Tab Atkins Jr.                                  2011-07-06 18:15:51 +0000 
--------------------------------------------------------------------------------
I agree that a two-handle range is a useful and reasonably common widget.  This can probably wait until the current form stuff is well-supported, though.
================================================================================
 #2   Aryeh Gregor                                    2011-07-06 20:54:21 +0000 
--------------------------------------------------------------------------------
This is probably something we want to add, but not until browsers have more solid WF2 support.
================================================================================
 #3   Jonas Sicking                                   2011-07-07 23:54:57 +0000 
--------------------------------------------------------------------------------
For what it&apos;s worth, I believe type=&quot;range&quot; support is coming along in most browsers main-stream browsers. There are other controls which is seeing much slower adoption, such as type=&quot;date&quot;, however I don&apos;t see a reason to hold off working on range-like controls until the problems surrounding date pickers have been solved.
================================================================================
 #5   Ian &apos;Hixie&apos; Hickson                             2011-08-13 02:52:34 +0000 
--------------------------------------------------------------------------------
Yeah, we probably need to address this soon. Marking REMIND for now but I&apos;ll get back to that once the feedback is down to more manageable levels in a month or so. Please don&apos;t hesitate to reopen this in mid September or so if I forget (I do check REMIND bugs regularly, but might not be prompt).

Meanwhile, anyone got any good ideas of how to fix this? New type (type=actually-a-range)? Attribute for type=range (&lt;input type=range foobar&gt;)? Reuse multiple=&quot;&quot; somehow? How about submission; have the value be a comma or space separated list? Do type=image-like name.min=foo&amp;name.max=bar?
================================================================================
 #6   Jonas Sicking                                   2011-08-22 20:59:04 +0000 
--------------------------------------------------------------------------------
First thing I could think of was

&lt;input type=range highlow&gt;

And yes, I think type=image-like is a good way to go.
================================================================================
 #7   Cameron Jones                                   2011-08-29 16:39:20 +0000 
--------------------------------------------------------------------------------
it might be possible to alter the specification of &apos;multiple&apos; attribute to be dynamically typed and have a numeric value for the declaration of the quantity of multiplicity, eg:

&lt;input type=&quot;range&quot; multiple=&quot;2&quot;/&gt;

This indicates that the range should have 2 values, and the agent should interpret and provide the corresponding interface. 

The extrapolation of this example illustrates greater potential for this extension and could also extend to the &apos;required&apos; attribute for declaration of the number of values required.

This will work well with the other constraint declarations to provide rich interface elements:

&lt;input type=&quot;range&quot; multiple=&quot;4&quot; required=&quot;2&quot; min=&quot;-1&quot; max=&quot;1&quot; step=&quot;0.1&quot;/&gt;
================================================================================
 #8   Simon Pieters                                   2011-08-30 09:28:07 +0000 
--------------------------------------------------------------------------------
Why would we ever want more than two values?
================================================================================
 #9   Cameron Jones                                   2011-08-30 12:09:05 +0000 
--------------------------------------------------------------------------------
there&apos;s no reason why a representation of a &apos;range&apos; can&apos;t select multiple values within that range. this is what the control represents in single-valued mode - &quot;select a value within this range&quot; where the range (or scale) is bound by the min\max values. for dual-value mode there is more of an assumption that the user is selecting the &apos;range&apos;, however they are really still selecting 2 values within the overall range\scale. 

nothing is lost by allowing a &apos;range&apos; input to select multiple values yet this opens the element for greater use.

implementing slider\scale controls in other languages i considered this to be relatively standard, however it would seem to be a less used configuration than i expected. there is no difficulty in representing this control to a user with multiple handles, and the implementation of encoding the values assigned to the control will require the same considerations.

for a specific use case, i&apos;ll just continue in abstract and just say that someone will want to collect 3, 4, etc values within a pre-defined range\scale. when combined with datalist, and especially when exhibiting pre-defined\natural ordering, the ability to graphically represent the choice of multiple values with a visual representation of their natural characteristics and relativity is not possible through other controls.
================================================================================</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>