Bug 12335
| Summary: | Setting location.href on frame has no effect if frame starts on about:blank | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | ss2cire |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Major | CC: | ap |
| Priority: | P2 | ||
| Version: | 419.x | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
ss2cire
<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)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
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.
Alexey Proskuryakov
No reply in 6 months, closing as WFM.