[Webkit-unassigned] [Bug 35063] Particularly constructed WebFrames can try to access a null HistoryItem

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=35063





--- Comment #10 from Brady Eidson <beidson at apple.com>  2010-02-22 09:07:20 PST ---
(In reply to comment #9)
> I was looking into a separate crash recently and noticed that this also fixes
> it. You don't need to use WebKit APIs to trigger this; another case is if you
> open an empty window and then document.write() into it. I've attached the file
> I had been testing with.

Thanks David, see the comments right above yours - this alternate way to crash
was discovered after the fix and API test for this bug landed.

> (It appears that WebKit also doesn't follow what the standard says with regard
> to inserting history entries on document.open(). See 3.5.1. It looks like
> currently the type and replace arguments are ignored and no history
> modifications take place? Could be wrong about that --- only just started
> navigating the codebase.)

That seems completely orthogonal to this bug.  If you think something's wrong,
please file a bugzilla with:
-A test case
-What you think expected behavior should be (and how it differs from real
behavior)
-What other browsers do.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.