commit | 73a5ae89bd4ec87b58eb0ef6d84e723a16dd01c4 | [log] [tgz] |
---|---|---|
author | sigbjornf@opera.com <sigbjornf@opera.com@bbb929c8-8fbe-4397-9dbb-9b2b20218538> | Thu Dec 05 21:21:29 2013 |
committer | sigbjornf@opera.com <sigbjornf@opera.com@bbb929c8-8fbe-4397-9dbb-9b2b20218538> | Thu Dec 05 21:21:29 2013 |
tree | fb355ddc9f4faf7f510c58722bad0c78eeabba81 | |
parent | c7a6100a4c6b32df10b0a55ec9783c6d87cfd169 [diff] |
Add 'exposed' objects and embeds to a document's named properties. The spec tells us that exposed <embed> and <object> are to be included in a document's "supported property names" http://www.whatwg.org/specs/web-apps/current-work/#dom-document-nameditem http://www.whatwg.org/specs/web-apps/current-work/#exposed (along with various other side conditions.) crbug.com/313292 retired a partial notion of "exposed"ness, this provides an implementation close to the spec's definition. R= BUG=316988 Review URL: https://codereview.chromium.org/75273004 git-svn-id: svn://svn.chromium.org/blink/trunk@163287 bbb929c8-8fbe-4397-9dbb-9b2b20218538