Hello everyone,
I have a problem submitting a form tag with submit buttons. many of
the scripts used in that page require the name of these submit buttons
to work correctly. I already read about the serialize function and
submit buttons so tried the form plugin as suggested on the jQuery
page but
Further details:
This behavior was noticed only in FF browsers.
- in FF 2.0.0.12 it is exactly as described in the previous message
- in FF 3.0.10 the difference is that val() does not return the value
attribute if that attribute is set by html markup, but does retrieve
it if it's set with val().
I noticed val() ignores the 'value' attribute on html elements.
If i have this markup:
< div id="test" value="45" >< / div >
$('#test').val() - will return empty string
$('#test').attr() - will return '45'
If i set a value using $('#test').val(88)
$('#test').val() - will return '88'
$('#test')
on
$.browser.msie. I'll be supporting it in 1.3 so you might want to
check it out:
http://github.com/alexrabarts/jquery-platformselector
http://plugins.jquery.com/project/platformselector
Cheers,
Alex
--~--~-~--~~~---~--~~
You received this message because you a
rrect me if I'm wrong) every DOM element. And again, correct me if
I'm wrong but every other browser adheres to the standard.
Alex
On Oct 21, 12:53 pm, Janis <[EMAIL PROTECTED]> wrote:
> actually these values somehow differ on IE6
--~--~-~--~~~---~
eing the word "Gzipped" and
> not understanding it.
>
> Try reading this excellent article on the subject:
>
> http://www.julienlecomte.net/blog/2007/08/13/
>
> JK
>
> -Original Message-
> From: jquery-dev@googlegroups.com [mailto:[EMAIL PROTECTED] On
>
>
ion to the page) will be 15kb.
>
> - Richard
>
> On Wed, Oct 15, 2008 at 7:55 AM, Alex Weber <[EMAIL PROTECTED]> wrote:
>
> > or if not the download link is bloated... =P
> > just a heads up
--~--~-~--~~~---~--~~
You received this messag
or if not the download link is bloated... =P
just a heads up
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe
nough to identify whats
good in each one and combine efforts to make just one!
5) Best plugin Contests! :)
PS - I like that the jQuery core is small and extensible and even
though there's tons of plugins that "could" or "should" be part of the
core, props to hold
detecting computer speed is probably not a very good option because
there are x factors that could contribute and also storing it in a
cookie is no good because cookies get deleted all the time...at least
by me :)
the most sensible thing to do imho is make 0 make the effect instant,
as proposed.
Just done some double checking, and my problem's root cause was
actually using an older version of jQ (1.1.3) which did indeed have
this bug
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
*Smashes head upon table in realization of one's own stupidity, and
sticks "stupid" badge to forehead*
I think I must have got confused between two versions of the same
thing via a misplaced symlink.
Sorry for wasting your time, and thanks for the pointers.
--~--~-~--~~~
> I assume you didn't mean to do $('inside') and meant to do $("#inside").
Yes, I did use the right method in my test code (mistake here a legacy
from mootools habits)
> Could you make a working test case? This has worked for us, in all our
> tests, so I'm not sure what the exact issue is here.
I expected clone(true) to be deep (ala MooTools); that is, clone all
the child elements exactly, down to events and all. It appears this
isn't the case:
Example:
$('inside').bind('focus', function() { alert('You focussed me!') })
//Result: if you focus on the input, you get an alert
$('
14 matches
Mail list logo
