[Bug 11162] New: This test case alerts 0 in all current released browsers: data:text/html,<!doctype html><script>var el = document.createElement("select"); el.multiple = true; alert(el.size);</script> As it stands, the spec says it should alert 1. While we're in the hab

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11162

           Summary: This test case alerts 0 in all current released
                    browsers: data:text/html,<!doctype html><script>var el
                    = document.createElement("select"); el.multiple =
                    true; alert(el.size);</script>  As it stands, the spec
                    says it should alert 1.  While we're in the hab
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#the
                    -select-element
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Section: http://www.whatwg.org/specs/web-apps/current-work/#the-select-element

Comment:
This test case alerts 0 in all current released browsers:
data:text/html,<!doctype html><script>var el =
document.createElement("select"); el.multiple = true; alert(el.size);</script>
 As it stands, the spec says it should alert 1.  While we're in the habit of
making the world making more sense, why not say that the default for the size
IDL attribute is the same as for the size content attribute, namely that it's
4 if multiple is set and 1 otherwise?  (What does it even mean for a content
attribute to have a default?)

Posted from: 68.175.61.233

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 28 October 2010 21:26:48 UTC