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 25608 - 'parent' vs. 'parentID' for addHitRegion()
Summary: 'parent' vs. 'parentID' for addHitRegion()
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: 2014-05-08 15:52 UTC by contributor
Modified: 2014-05-08 17:50 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-05-08 15:52:39 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html
Multipage: http://www.whatwg.org/C#hitregionoptions
Complete: http://www.whatwg.org/c#hitregionoptions
Referrer: 

Comment:
'parent' vs. 'parentID' for addHitRegion()

The algorithm description for say:

"If the arguments object's _parent_ member is the empty string, let it be null
instead."

but the HitRegionOptions dictionary has

"DOMString? parentID = null;"

Posted from: 2a00:801:e0:30:72f3:95ff:fe00:4501
User agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16
Comment 1 Fredrik S 2014-05-08 15:53:30 UTC 
s/for say/for addHitRegion say/
Comment 2 contributor 2014-05-08 17:50:26 UTC 
Checked in as WHATWG revision r8619.
Check-in comment: Somehow I had typos and copypasta in the name of the addHitRegion parentID attribute here
http://html5.org/tools/web-apps-tracker?from=8618&to=8619