Actually that's not the best example. There is some "standardisation"
that goes on for the href attribute. Especially with respect to IE and
how it deals with adding or leaving off the full path.
Oops sorry, that's true. That was just the first example that popped into
my head.
If you were
en faster and cleaner to
> just use plain 'ol javascript. Don't let this dissuade you from using
> jQuery. In most cases it will save you lots of time and effort.
>
> -- Josh
>
>
> - Original Message - From: "Chuck" <[EMAIL PROTECTED]>
>
ol javascript. Don't let this dissuade you from using jQuery.
In most cases it will save you lots of time and effort.
-- Josh
- Original Message -
From: "Chuck" <[EMAIL PROTECTED]>
To: "jQuery (English)"
Sent: Monday, April 28, 2008 3:17 PM
Subject: [jQ
> No, but
>
> I am generating XML to send to my server. I was replacing what was
> basically
>
> var xmlString = "';
>
> with
>
> var xmlString = " '"/>';
>
> Because I like the jQuery way of specifying items. And the above
> makes more sense then what is actually needed:
>
> var x
No, but
I am generating XML to send to my server. I was replacing what was
basically
var xmlString = "';
with
var xmlString = "';
Because I like the jQuery way of specifying items. And the above
makes more sense then what is actually needed:
var xmlString = "';
jQuery makes my code so
> I can stop in a callback with Visual Studio and run these three
> commands to get the value of the "checked" attribute of a radio button
> which is not selected. Why does the wrapped object not return "false"
> like the DOM object?
>
> document.all.ProtectLocal.checked
> false
> $('#Prot
6 matches
Mail list logo
