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 13045 - Figure out what to do about Document.documentURI
Summary: Figure out what to do about Document.documentURI
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-24 12:31 UTC by Ms2ger
Modified: 2011-08-28 09:56 UTC (History)
3 users (show)

See Also:


Attachments

Description Ms2ger 2011-06-24 12:31:21 UTC

    
Comment 1 Anne 2011-06-24 17:02:59 UTC
Options:

1. Remove
2. Make it readonly
3. Move it HTML5
4. Combination of 2 and 3
5. Deal with it
Comment 2 Anne 2011-07-29 19:11:40 UTC
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-June/032255.html
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-June/032267.html

I think we should do it like Gecko does with the exception that documentURI becomes readonly. I think we should define documentURI and URL as a "document URL" concept for other specifications to set and read with initially the value "about:blank".
Comment 4 Anne 2011-07-30 14:22:40 UTC
Implemented comment 2.