Hello again from the CF5 programmer trying to catch up.
I always used to write for Internet Explorer, and did so again after my return
to programming a few months ago, resulting in what is by now a rather complex
site. Many CF (and other internet-based) programmers have told me since then
that
First, I believe I already have Firebug: when Firefox tells me I have an error (lower righthand corner) I can click on that and see lots of info about it; and which I click on the '^' in that panel, it morphs into a window with 'Firebug' in its title. But I don't see how that helps me with
I have been using YUI (yahoo) library, it works well and has some nice built
in cross browser functionality.
firefox supports getElementByID and the childNodes property... they performa
a little differently than in IE.
On Mon, Feb 18, 2008 at 10:11 AM, Peyton Todd [EMAIL PROTECTED]
wrote:
I escape this by avoiding JavaScript if possible or any script that relies
on the browser and prefer to handle things on the server side. I guess
sometimes you can't get around it though and that may not be logical for
you.
Dusty
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
On Feb 18, 2008 10:11 AM, Peyton Todd [EMAIL PROTECTED] wrote:
First, I believe I already have Firebug: when Firefox tells me I have an
error (lower righthand corner) I can click on that and see lots of info
about it; and which I click on the '^' in that panel, it morphs into a
window with
Steven, did mean Firefox supports *parentNode* instead of getElementById? My Firefox always complains of an error whenever it sees getElementById. Or is there perhaps a different spelling for Firefox? (not likely, right?) The last letter in getElementById is lower case, not upper case as you have
never had any issues using getElementById (yes casing was wrong)...
On Mon, Feb 18, 2008 at 10:37 AM, Peyton Todd [EMAIL PROTECTED]
wrote:
Steven, did mean Firefox supports *parentNode* instead of getElementById?
My Firefox always complains of an error whenever it sees getElementById.
Or is
I'm just about to head to the bookstore looking for an update to the O'Reilly book. I've always loved O'Reilly books. But real quick: Does anyone have a recommendation for some other book that would deal with which properties - methods - collections are supported by which browser?-Original
Another option might be to look at what these Javascript libraries
have to offer:
Prototype and script.aculo.us
http://www.pragprog.com/titles/cppsu
These are not just for UI niceties. They handle a lot of the browser
issues correctly and transparently.
On Feb 18, 2008 11:10 AM, Peyton Todd
H. I'll definitely look into Spry. But just as a guess, that would mostly help me for future projects, right? Short of re-writing what I have done so far (a major task!), I still need to find a way our of my present dilemma. Lucky for me, this app is an INTRAnet just like all my previous ones
Red-faced, I am now compelled to report that my mistake with getElementById was that the elements reporting this error had no ID, but only a NAME. Duh! Internet Explorer evidently decided to be more forgiving on this point - at least that's my excuse for not noticing it...-Original
JQuery also looks nice...
On Mon, Feb 18, 2008 at 11:17 AM, Shifang (Frank) Sun [EMAIL PROTECTED]
wrote:
Another option might be to look at what these Javascript libraries
have to offer:
Prototype and script.aculo.us
http://www.pragprog.com/titles/cppsu
These are not just for UI niceties.
You gotta love IE's interpretation of coding errors... i hate stuff like
that.
On Mon, Feb 18, 2008 at 2:03 PM, Peyton Todd [EMAIL PROTECTED]
wrote:
Red-faced, I am now compelled to report that my mistake with
getElementById was that the elements reporting this error had no ID, but
only a
13 matches
Mail list logo
