As commented in your commit, I think the support approach is cleaner and
more future-proof (that is when Chrome implements JSON parsing controls
properly).
2010/1/12 John Resig
> As a note: I added identical errors earlier today but skirted around
> the need to have any sort of support property:
On 11/01/2010, at 10:16 PM, Scott Sauyet wrote:
... while keyboard input
is so broken already.
What you said certainly looks important to me. I think it's as Dave
Methvin said, you just have unfortunate timing trying to discuss this
while developers are so focused on the release.
I'll raise
On 1/11/10 8:26 PM, DBJDBJ wrote:
Simple and effective ... Thanks.
My approach is 'slightly' different ( http://dbj.org/dbj/?p=470 ) but
perhaps sacrifices size and simplicity to be (maybe) faster.
Does anyone know why CHROME window.JSON.parse accepts non-standard
strings ? I am writing this in
Simple and effective ... Thanks.
My approach is 'slightly' different ( http://dbj.org/dbj/?p=470 ) but
perhaps sacrifices size and simplicity to be (maybe) faster.
Does anyone know why CHROME window.JSON.parse accepts non-standard
strings ? I am writing this in CHROME 4.0.228.1.dev and it accepts
It is definitely odd that which is standardised in mouse button
events, but button is not.
On Jan 11, 12:01 pm, helianthus wrote:
> http://github.com/jquery/jquery/blob/master/src/event.js#L401
>
> I did not know that there has been normalization for event.which until
> looking up the new API bro
As a note: I added identical errors earlier today but skirted around
the need to have any sort of support property:
http://github.com/jquery/jquery/commit/44e6beb10304789044de2c5a58f5bb82e8321636
--John
On Mon, Jan 11, 2010 at 7:51 PM, AlexSexton wrote:
> I went ahead and wrote a support flag
I went ahead and wrote a support flag and an implementation of a check
for nonstandard window.JSON.parse methods (including chrome) inside of
the ajax httpData method.
My change is here:
http://github.com/SlexAxton/jquery/commit/57313eb69a7c87f862440b062932e91c0e162c6c
I think consistently throw
With Windows Mobile, IE is a very poor mobile browser, so I usually replace
it with Opera, which I others may do as well, so it would be good if it was
supported. I wouldn't be surprised if it was as standards complaint as the
desktop version.
--Sam
2010/1/11 John Resig
> > Thanks, nice intervi
> Thanks, nice interview. And, yes, agree with John, the devices
> selection is key. Also, IMO 3rd party browsers should not be a
> priority (focusing on the device default browser would bring a better
> reach)
I use to think similarly to you but Opera has such a dominant position
in the mobile sp
Thanks, nice interview. And, yes, agree with John, the devices
selection is key. Also, IMO 3rd party browsers should not be a
priority (focusing on the device default browser would bring a better
reach)
Jeremy,
On Jan 11, 1:13 pm, Rick Waldron wrote:
> I've been using jQuery 1.4a2 with webOS ap
Seemed simple enough so I fixed it. Thanks for the heads-up.
--John
On Fri, Jan 8, 2010 at 11:35 AM, Marc Diethelm wrote:
> I want to bring attention to two possible patches for bug #3552.
>
> They have been in Trac for 10 months now... Can someone please have a
> look and commit one of the so
Good catch. Filed and fixed.
http://dev.jquery.com/ticket/5785
Also, in the future, you may want to use the new .unwrap() method
which is designed for this exact purpose:
c.children.unwrap();
(Although unwrap uses replaceWith so you would've hit the same bug, it
seems. Glad it's fixed!)
--John
I've been using jQuery 1.4a2 with webOS apps as-is, so far no real issues.
One thing I'm working on as a personal project is creating a plugin to
support the following events:
acceleration, orientationchange, shaking, shakestart, shakeend
More news as progress continues.
Rick
On Sun, Jan 10,
Just wanted to chime in so you know I'm not ignoring the topic and still
interested in the enhancement's progress. I still support all four points.
Rick
--
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to
Hi,
I would like to know if I have found a bug or the new version of
jQuery works different. The problem is with this code:
var c = inner.wrapInner("").children
();
//some stuff
c.replaceWith(c.children());
When using jQuery 1.3.2 then everything works fine but when I use
1.4a2 then children of "
My vote goes to #1 and #2. Anyone else care to vote or discuss?
On Tue, 5 Jan 2010 18:18:25 -0500, Rick Waldron
wrote:
> I vote *YES *on all of these.
>
>
>
>
>
> On Tue, Jan 5, 2010 at 4:55 PM, webbiedave
> wrote:
>
>> OK. Not sure where we're at on this but I'm hoping some sort of
conse
Yep, I confirmed it on my own and came to a similar conclusion:
http://github.com/jquery/jquery/commit/5a0ac24e35c07fe4be22df828e6b909fe65237b9
The events fire in the same order in IE 8 and in other browsers with
my change. Thanks for the test case!
--John
On Mon, Jan 11, 2010 at 12:13 PM, Mar
Did a little further investigation on this...
I added a 'return false;' statement to the end of
jQuery.event.special.submit.setup,
'submit' is now handled but only after it's bubbled...
jQuery(function($) {
$('#test-form').bind('submit', function(event) {
alert('catch submit');
Great - thanks :)
On Mon, 11 Jan 2010 17:09:27 -, John Resig wrote:
Already been fixed. jQuery 1.4rc1 will be out today with the fix in it.
--John
On Mon, Jan 11, 2010 at 11:21 AM, Kelvin Luck
wrote:
Hi,
I've had a few reports from users of my plugins that
$(window).bind('unload')
Already been fixed. jQuery 1.4rc1 will be out today with the fix in it.
--John
On Mon, Jan 11, 2010 at 11:21 AM, Kelvin Luck wrote:
> Hi,
>
> I've had a few reports from users of my plugins that
> $(window).bind('unload') causes an "too much recursion" error in Firefox.
> Are there any known i
http://github.com/jquery/jquery/blob/master/src/event.js#L401
I did not know that there has been normalization for event.which until
looking up the new API browser today.
I could (partly) understand the choice of using event.which for
keyboard event, since it is a mess and there is no standard for
Hi,
I've had a few reports from users of my plugins that
$(window).bind('unload') causes an "too much recursion" error in Firefox.
Are there any known issues around this or should I try to put together a
reduced test case?
Thanks,
Kelvin :)
--
You received this message because you are s
Quick heads up... submit event is broken in IE8.
Demo below. (tried using jsbin but the nightly build of jquery is out
of date and very broken in IE! So this was tested against the latest
from git)
For jQuery 1.3.2 you'll see two alerts after clicking Submit... 'catch
submit', then 'submitted'.
I
Hi Toshiro,
You can get more information about Websockets from here:
http://tech.kaazing.com
http://www.websockets.org
You can also download a Gateway product supporting Websockets from
here: http://www.kaazing.com/download/
It comes with a good set of demos, doc, tutorials, and examples.
[Dis
On Sun, Jan 10, 2010 at 2:20 AM, helianthus
wrote:
> I have just looked into the code and have found out where it goes
> wrong.
>
> It is at this line:
> http://github.com/jquery/jquery/blob/master/src/event.js#L102
> where it overwrites the original handler with a modified one even for
> other t
On Fri, Jan 8, 2010 at 6:41 PM, Clifford Heath wrote:
> On 09/01/2010, at 12:26 AM, Scott Sauyet wrote:
>>
>> It seems to me that you did get serious responses when you posted in
>> one of the innumerable recent threads about JSON changes.
>
> I've said nothing about JSON.
No, actually looking at
26 matches
Mail list logo
