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 19986 - The spec says "If candidates is empty, return null and undefined and abort these steps.", but I can't return both null AND undefined? Should it just return and abort the algo?
Summary: The spec says "If candidates is empty, return null and undefined and abort th...
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: 2012-11-16 16:51 UTC by contributor
Modified: 2012-12-31 05:52 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-11-16 16:51:17 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#tinyhippos-injected
Complete: http://www.whatwg.org/c#tinyhippos-injected

Comment:
The spec says "If candidates is empty, return null and undefined and abort
these steps.", but I can't return both null AND undefined? Should it just
return and abort the algo? 

Posted from: 85.240.53.124 by marcos@marcosc.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.5 Safari/537.17
Comment 1 Marcos Caceres 2012-11-16 17:23:14 UTC 
ah, ok... got confused - the return types are at the top of the algorithm. To be a little more clear, it should say:

"return null as the URL and undefined as the pixel density"
Comment 2 contributor 2012-12-31 05:52:46 UTC 
Checked in as WHATWG revision r7632.
Check-in comment: Clarify
http://html5.org/tools/web-apps-tracker?from=7631&to=7632