[Webkit-unassigned] [Bug 28232] New: "Null after navigation" in major-objects.html is unclear
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Aug 12 14:33:19 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=28232
Summary: "Null after navigation" in major-objects.html is
unclear
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Enhancement
Priority: P2
Component: WebKit Website
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: joe.mason at torchmobile.com
CC: abarth at webkit.org
Adam Barth explains the "null after navigation" comment in major-objects.html
like this:
> > "NULL after navigation" could be clearer - it suggests that DOMWindow and
> > everything below it only exists if you type the URL, but not if a page is
> > loaded by clicking a link, which can't be true.
>
> Oh, I meant navigate to cover both typing in the location bar and
> clicking a link. Is there a better word to use for that?
>
> > Does it mean that it's NULL
> > immediately after navigation, while waiting for the load, and is replaced by
> > a valid pointer after loading?
>
> I wasn't sure the best way to represent this in the diagram.
> Typically, the edge becomes null in the "up" direction and replaced
> with a new object in the "down" direction. If you can think of a nice
> way to explain this on the page, please file a bug, CC me, and upload
> a patch.
I think the best way to represent this is with a footnoted explanation. (Patch
forthcoming)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list