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 19560 - Should document.location be Unforgeable?
Summary: Should document.location be Unforgeable?
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-10-16 17:41 UTC by contributor
Modified: 2012-11-20 02:38 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-10-16 17:41:05 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html
Multipage: http://www.whatwg.org/C#the-document-object
Complete: http://www.whatwg.org/c#the-document-object

Comment:
Should document.location be Unforgeable?

Posted from: 193.190.253.146 by ms2ger@gmail.com
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0
Comment 1 Ms2ger 2012-10-16 17:42:08 UTC 
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1849 logs the Location object in IE/Gecko/Opera, the iframe in Chrome.
Comment 2 Ian 'Hixie' Hickson 2012-10-23 21:46:07 UTC 
see also input-for-whatwg-location-object
Comment 3 contributor 2012-11-19 18:47:33 UTC 
Checked in as WHATWG revision r7512.
Check-in comment: Make sure <iframe name=location> doesn't override Document.location
http://html5.org/tools/web-apps-tracker?from=7511&to=7512