469,625 Members | 1,741 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,625 developers. It's quick & easy.

PC IE6 & Prototype AJAX

Hi folks.

I built an ajax.updater reply in a website on a Mac, and she works
fine. It's a simple reply, the html supplied is correct, and I also
supply the target DIV as well.

Just wondering why a PC won't show anything.

Cheers

Oct 29 '06 #1
7 1632

BeeRich wrote:
Hi folks.

I built an ajax.updater reply in a website on a Mac, and she works
fine. It's a simple reply, the html supplied is correct, and I also
supply the target DIV as well.

Just wondering why a PC won't show anything.
Just wondering why you aren't showing anything - it's not useful to
comment on what we can't see. Maybe guesses are all you want. :-)

--
Rob

Oct 29 '06 #2
BeeRich said the following on 10/28/2006 8:17 PM:
Hi folks.

I built an ajax.updater reply in a website on a Mac, and she works
fine. It's a simple reply, the html supplied is correct, and I also
supply the target DIV as well.

Just wondering why a PC won't show anything.
Why does my stereo hit a harder bass note listening to Marvin Gaye than
it does when listening to the Beastie Boys? You can't diagnose what you
can't see.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Oct 29 '06 #3
I thought there might be a common experience to this. Anyway, this is
what I'm returning:

<p>0307: Piano Solo - Bach - Age 13 & Under ($37)</p>

My function:

function classLookup(myClassNumber) {
ajax = new Ajax.Updater(
'classDisplay', // target div
'includes/backComm.lasso?choice=getClassName&cn=' + myClassNumber, //
URL
{ // options
method:'post'
});
}

Nothing really to see. I'm using a doctype header on my backComm file,
and I've been told maybe the two doctypes are confusing IE.



RobG wrote:
BeeRich wrote:
Hi folks.

I built an ajax.updater reply in a website on a Mac, and she works
fine. It's a simple reply, the html supplied is correct, and I also
supply the target DIV as well.

Just wondering why a PC won't show anything.

Just wondering why you aren't showing anything - it's not useful to
comment on what we can't see. Maybe guesses are all you want. :-)

--
Rob
Oct 29 '06 #4

BeeRich wrote:
I thought there might be a common experience to this. Anyway, this is
what I'm returning:
Please don't top post to this news group, reply below trimmed quotes.

<p>0307: Piano Solo - Bach - Age 13 & Under ($37)</p>

My function:

function classLookup(myClassNumber) {
ajax = new Ajax.Updater(
'classDisplay', // target div
'includes/backComm.lasso?choice=getClassName&cn=' + myClassNumber, //
URL
{ // options
method:'post'
});
}
Please use 2 or 4 spaces for indents, not tabs, and manually wrap code
at about 70 chararcters to prevent auto-wrapping.

Nothing really to see. I'm using a doctype header on my backComm file,
and I've been told maybe the two doctypes are confusing IE.
I guess you are saying that the page has one doctype and the response
another - I can't see why that would be an issue unless you are using
innerHTML - after all, the basis of AJAX is that the response will be
XML (though most of the time it probably isn't, it is more likely JSON,
HTML or plain text). Browsers generally ignore the doctype in the file
and rely on the MIME type provided by the server - I don't know if that
is an issue with XMLHttpRequest. If you are returning HTML with a
doctype, I can't see why it would be different from the main page.
Anyone using AJAX should be using HTML 4.01 strict.

You seem to be using Prototype.js, it is not supported here. The
general advice is to post to a Prototype news group or other forum.

The prototype news group seems to be poorly supported, so you might
like to try elsewhere:

<URL: http://groups.google.com.au/group/Prototypejs?lnk=li >
--
Rob

Oct 29 '06 #5

Randy Webb wrote:
BeeRich said the following on 10/28/2006 8:17 PM:
Hi folks.

I built an ajax.updater reply in a website on a Mac, and she works
fine. It's a simple reply, the html supplied is correct, and I also
supply the target DIV as well.

Just wondering why a PC won't show anything.

Why does my stereo hit a harder bass note listening to Marvin Gaye than
it does when listening to the Beastie Boys? You can't diagnose what you
can't see.
Nothing really to diagnose. It's a typical ajax.updater function.
Others have told me it has to do with IE6, as it doesn't like the
doctype for some reason.

So, the posting here was about IE6, and not the ajax.updater. I
thought someone might have run into this before.

In any case, Prototype isn't supported here. I hope I posted in the
right font, location, etc.

Nov 2 '06 #6
BeeRich said the following on 11/2/2006 8:56 AM:
Randy Webb wrote:
>BeeRich said the following on 10/28/2006 8:17 PM:
>>Hi folks.

I built an ajax.updater reply in a website on a Mac, and she works
fine. It's a simple reply, the html supplied is correct, and I also
supply the target DIV as well.

Just wondering why a PC won't show anything.
Why does my stereo hit a harder bass note listening to Marvin Gaye than
it does when listening to the Beastie Boys? You can't diagnose what you
can't see.

Nothing really to diagnose.
Hmmm, nothing to diagnose means no problem. Since there isn't a problem,
then there shouldn't be a post asking how to solve a non-problem.
It's a typical ajax.updater function.
Whatever that is.
Others have told me it has to do with IE6, as it doesn't like the
doctype for some reason.
Hmmm, should I guess what the doctype is? Oh wait, there is nothing to
diagnose.
So, the posting here was about IE6, and not the ajax.updater. I
thought someone might have run into this before.
What issue is it? Oh, the one that doesn't need to be diagnosed, I
understand <eyeroll>
In any case, Prototype isn't supported here.
You finally got something right. Try asking the person/group who wrote
Prototype why it doesn't work.
I hope I posted in the right font, location, etc.
Probably not but we won't mention it.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 2 '06 #7
BeeRich wrote:
<snip>
In any case, Prototype isn't supported here. I hope I posted
in the right font, location, etc.
It is not reasonable to say "Prototype isn't supported here" (beyond
saying that nobody here is likely to be recommending its use). This
group doesn't support, or not support, anything beyond javascript in
general, and the majority of questions asked are in relation to code
that is either unique or broadly unknown to the people who are being
asked to answer the questions asked. Yet questions do get answered.

If people asking questions in relation to Prototype.js would present
the code they were using, including (in isolation) the parts of
Prototype.js they were employing (that is, the whole context of the
question, and nothing else) then their questions would likely receive
the same consideration as any other.

The problem as it stands seems to be that people asking questions about
Prototype.js are expecting everyone here to be familiar with its code,
despite the fact that it is a poorly conceived, convoluted library that
has never been cross-browsers and is now not even ECMAScript compatible
(that is, few will want to study Prototype.js as most could write there
own code and get a far superior result). And the individuals using
Prototype.js are not themselves capable of reducing it to just the
pertinent code in order to ask there questions in a form that can be
answered (partly a consequence of its being overly convoluted).

Richard.

Nov 3 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

10 posts views Thread by Steve | last post: by
17 posts views Thread by Steve-O | last post: by
5 posts views Thread by Gerry Vandermaesen | last post: by
23 posts views Thread by Dautkhanov | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.