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 8915 - "the active document of the script's browsing context" -- is there more author-friendly terminology we can use here (in addition to the existing)
Summary: "the active document of the script's browsing context" -- is there more autho...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-10 09:01 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-02-10 09:01:40 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#documents

Comment:
"the active document of the script's browsing context" -- is there more
author-friendly terminology we can use here (in addition to the existing)

Posted from: 64.134.222.102
Comment 1 Ian 'Hixie' Hickson 2010-02-14 13:36:32 UTC 
I don't know.

In modern graphical browsers, it basically means "the page that's showing in the frame that the script is from", but we can't really _say_ that because it has all kinds of problems when you start actually drilling down on what it means in lots of edge cases.

I don't really know how to clarify this case here. We could add a green note, but that might help as much as it hurts, since it would lead to people who really should know this in-and-out not looking closely at the actual requirements. It would also only help in this one specific case, and the terminology is all over the spec.

It's like quantum mechanics... you can explain it in layman's terms, but at the end of the day, you're not really explaining anything if you do, you're just drawing pretty pictures that aren't what's really going on.



EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Not sure how to fix this. Please definitely reopen if you have any ideas.