This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21735 - select: item/namedItem return values should be nullable
Summary: select: item/namedItem return values should be nullable
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-17 17:37 UTC by contributor
Modified: 2013-06-04 20:26 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2013-04-17 17:37:40 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html
Multipage: http://www.whatwg.org/C#the-select-element
Complete: http://www.whatwg.org/c#the-select-element
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
select: item/namedItem return values should be nullable

Posted from: 87.64.200.53 by ms2ger@gmail.com
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20130415 Firefox/23.0
Comment 1 contributor 2013-06-04 20:12:31 UTC 
Checked in as WHATWG revision r7893.
Check-in comment: Fix HTMLSelectElement's collection-related IDL and non-normative prose.
http://html5.org/tools/web-apps-tracker?from=7892&to=7893
Comment 2 Boris Zbarsky 2013-06-04 20:15:19 UTC 
>  (HTMLOptionElement or HTMLOptGroupElement)? namedItem(DOMString name);

Why?  It can only return HTMLOptionElement or null...
Comment 3 Ms2ger 2013-06-04 20:26:26 UTC 
(In reply to comment #2)
> >  (HTMLOptionElement or HTMLOptGroupElement)? namedItem(DOMString name);
> 
> Why?  It can only return HTMLOptionElement or null...

That's bug 22225 already :)