- This topic has 3 replies, 2 voices, and was last updated 17 years, 11 months ago by
.
-
Posts
-
I have an interesting situation this morning with a simple web page that incorporates two DWR calls. If I access this page from within your Web 2.0 browser it works fine. If I run it using your standard browser (or even IE) I only get the response from the first call back to the browser!
Here is my code:
<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>
<html>
<head>
<jsp:include flush=”true” page=”includes/heads.jsp”></jsp:include>
</head><body onload=”load()”>
<fieldset>
<legend>
Now
</legend>
<label id=”timeNow” />
</fieldset><fieldset>
<legend>
Bikes
</legend>
<select name=”bikes” id=”bikes”>
</select>
</fieldset>
</body></html>
function load(){
now();
bikesFn();
}
function now(){
JsDate.toString(nowResponse);
}
function nowResponse(data){
DWRUtil.setValue($(“timeNow”),data);
}function bikesFn(){
JsBikeBean.getBikeInfo(bikesResponse);
}
function bikesResponse(data){
DWRUtil.removeAllOptions($(“bikes”));
DWRUtil.addOptions($(“bikes”),data);
}
function unload(){
alert(“listeners have been stopped” );
}The solution here is quite easy… have every single one of your clients buy MyEclipse, and only use the Web 2.0 Browser to view your page.
Ok, more seriously now, can you try with another browser like Firefox or Opera? Also if you use Firefox, install the WebDeveloper plugin (https://addons.mozilla.org/firefox/60/) it is fantastic and will notify you of javascript errors and such on the page as it runs.
Riyad —
This is great; a techie with a sense of humor! I’ll see about adopting your Web 2.0 browser as our standard!
Can you tell me what the difference is between your two browsers? I was under the impression you were simply using the hosted browser (eg IE) before introducing the Web 2.0 browser. I can imagine the new browser is “special,” but I’m still confused how opening the same page in the two browsers yields different output. This sort of shakes your faith.
Peace,
ScottOur web 2.0 browser is based on the mozilla/firefox code base. It’s specially instrumented to hook the debugger into the page-processing cycle.
My suggestion of using plain firefox with that web developer plugin is a good sanity check. If it doesn’t work there, then something fishy is going on. I never take “it doesn’t work in IE” as any final indication of a problem. Unfortunately *lots* of things don’t work in IE that should when you start getting into heavy CSS and JavaScript programming. (Getting better in IE7 though)
