| Summary: | Frame::document() should return a reference | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Gyuyoung Kim <gyuyoung.kim> | ||||||
| Component: | Frames | Assignee: | Gyuyoung Kim <gyuyoung.kim> | ||||||
| Status: | NEW --- | ||||||||
| Severity: | Normal | CC: | kling | ||||||
| Priority: | P2 | ||||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Gyuyoung Kim
2014-04-22 02:15:54 PDT
Created attachment 229872 [details]
WIP
Kling, I wonder if there is any chance that a frame has a null document. Created attachment 229953 [details]
WIP
Frame::document() will be null when the Frame is created, until the FrameLoader has completed loading the initial document. It will also become null during teardown. We shouldn't make document() return a reference until we've eliminated those cases where it can be null. (In reply to comment #4) > Frame::document() will be null when the Frame is created, until the FrameLoader has completed loading the initial document. It will also become null during teardown. > > We shouldn't make document() return a reference until we've eliminated those cases where it can be null. Kling, thank you for your answer. Let me check those cases. |