[Webkit-unassigned] [Bug 28011] New: Javascript core in webkit seems not work under 2 "window.location" issued
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Aug 4 20:25:52 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=28011
Summary: Javascript core in webkit seems not work under 2
"window.location" issued
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: Critical
Priority: P2
Component: JavaScriptCore
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: yu.tsunghua at gmail.com
CC: yu.tsunghua at gmail.com
Dear Webkit Experts:
Right now we are using Linux x86 + qt embedded 4.5.2 to build a
VOD client. The problem what we met is that if contiguous two
"window.location=" be issued in a javascript code section,
QT webkit moudle seems can't send out the first one
window.location. in other word, the first window.location was
overwrite by the second one.
the first window.location is an RTSP URL. the second is an HTTP
URL. we build a test enviroment to simulate the whole process.
here is the followings.
1. for first page, just an index page.
index.html
<html>
<head>
</head>
<body>
<a href="http://192.168.11.5/darkmomo/rtsp.html">RTSP</a>
</body>
</html>
2. for second page, launch the rtsp url via javascript in body tag
onload action.
rtsp.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=big5" >
<title>RTSP URL Test</title>
</head>
<body topmargin="0" leftmargin="0" text="#FFFFFF" onload="playContent()" >
<script language="javascript">
function playContent() {
window.location="rtsp://192.168.11.5/";
onBack();
}
function onBack() {
window.location="http://192.168.11.5/show.html";
}
</script>
</body>
</html>
3. for third page, just show the current program end.
<html>
<head>
<title>In On Back Page</title>
</head>
<body>
<a>Back Page</a>
</body>
</html>
when we using the QWebView to test the three pages, we can't get
the RTSP URL request via qt's way. and we got the trolltech's expert
advise to seek webkit experts to find out a workaround way to address
this problem. the trolltech's expert tell us the problem seems come
from the webkit's javascript core. would any body to do us a favor
to show us how to trace the window.location was be handled? we want
to know where the window.location was be handled and add some debug
message to see what is really happened.
Thanks in advance.
Best Regards,
Albert
--
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