Bug 12335 - Setting location.href on frame has no effect if frame starts on about:blank
Summary: Setting location.href on frame has no effect if frame starts on about:blank
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 419.x
Hardware: Mac OS X 10.4
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-19 02:34 PST by ss2cire
Modified: 2007-07-13 04:35 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ss2cire 2007-01-19 02:34:32 PST 
<html>
<script language="JavaScript">
function getsection()
{
	window.content.location.href = "otherpage.html";
}
</script>
<frameset rows="*,50" noresize="noresize" onLoad="getsection();">
<frame name="content" src="" />
<frame name="navigation" src="navigation.html" />
</frameset>
</html>

that code doesn't seem to change the content frame's href like it should, but it does seem to work if the content frame has an initial source value other than about:blank (or just blank to begin with)
Comment 1 Alexey Proskuryakov 2007-01-19 11:23:18 PST 
Have you tested with a WebKit nightly build from <http://nightly.webkit.org>? I can reproduce this issue with shipping Safari, but not with a recent version of WebKit.
Comment 2 Alexey Proskuryakov 2007-07-13 04:35:38 PDT 
No reply in 6 months, closing as WFM.