Damn, sorry, my fault - I gotta learn GIT better.
On Dec 10, 3:05 pm, John Resig wrote:
> Unless I'm misunderstanding something, isn't rtrim exactly as you
> proposed, right now?
> rtrim = /^(\s|\u00A0)+|(\s|\u00A0)+$/g,
>
> --John
>
> On Wed, Dec 9, 2009 at 6:54 PM, Mr Speaker wrote:
> > Hey gu
Thanks for digging in to this, Jeff - I'll look into it and see if
there's a potential solution.
--John
On Tue, Dec 8, 2009 at 12:00 PM, Jeff Adams wrote:
> Hello everyone,
>
> I've just added some new comments to an old bug #2551 (
> http://dev.jquery.com/ticket/2551 ) that is still open from
Unless I'm misunderstanding something, isn't rtrim exactly as you
proposed, right now?
rtrim = /^(\s|\u00A0)+|(\s|\u00A0)+$/g,
--John
On Wed, Dec 9, 2009 at 6:54 PM, Mr Speaker wrote:
> Hey guys,
>
> I was using 1.4a1 and I noticed that $.trim was killing ALL spaces
> (not just leading/trainli
Hey guys,
I was using 1.4a1 and I noticed that $.trim was killing ALL spaces
(not just leading/trainling). I checked GIT and there was a fix for
it. Buuut, it looks like the fix was to return it to how it was
originally - but i think that means the bug it was trying to fix
should be reopened...
ht
I like the first, there was an issue with multi-string .append where the
first one was '[' that resulted in me needing to use
document.createTextNode to work around it.
Don't like the second, I don't see the purpose and it looks like it
might have some issues working as an implementation.
Not re
Ah, today I ran across a duplicate bug here: #4984 (
http://dev.jquery.com/ticket/4984
)
On Dec 8, 2:00 pm, Jeff Adams wrote:
> Hello everyone,
>
> I've just added some new comments to an old bug #2551
> (http://dev.jquery.com/ticket/2551) that is still open from back in
> the 1.2 days. I just
Attached are four extensions to jquery.
One is a
$.text('Test text') utility function, that simplifies cases like
$('div.content').append($.text('Test test here'));
Second the same thing with
$.html('some html with everything')
Third the combination:
$.toHtml('some < special')
which for exa
Thanks for the awesome tip on getting those undocumented event
handlers working!
This cool tip is now in place on http://yayquery.com/
On Dec 8, 8:28 am, DBJDBJ wrote:
> Also please be sure to have jquery attribute present, like so:
>
> jquery="1.3.2" >
>
> This switches on, undocumented jQuery
Right, the redirection is because the live submit event is being
triggered but not blocked - which means that live submit isn't
working, which is why I referred to that commit (which is the only
change to live submit/change since 1.4a1).
--John
On Wed, Dec 9, 2009 at 11:58 AM, Julian Aubourg
w
I tested quickly with the two first tests in unit/event.js but IE doesn't
report any javascript error. Tests fail though. Sad thing is, if you try &
test all of unit/event.js, at one point, the page tries to redirect to
another page:
http://127.0.0.1/zend/jquery/test/?T3=%3F%0D%0AZ&H1=x&H2=&PWD=&T
For the time being, it's in the tree. It's far less than a kilobyte once
minified and optional (needs the jsonpOverIFrame option set) : I know for a
fact the technique fails on IE when document.domain is set (even to its
default value) and I have no clue how to feature test for it. The advantage
of
Oof, ok - I wonder what I broke.
I wonder if it's failing on this:
http://github.com/jquery/jquery/commit/7d36ccfa8eb018fcf349e1f74e3a0a614385558f
(Maybe the support change & submit checks aren't reporting false
properly in IE?) Any help remote-debugging this issue would be
appreciated.
--John
Did you add this as a plugin? It doesn't seem like that's something
that we'd ship in jQuery core.
Glad to hear that it's really coming together, though!
--John
On Wed, Dec 9, 2009 at 11:33 AM, Julian Aubourg
wrote:
> Another update: I added a jsonp over iframe transport similar to the
> one
Another update: I added a jsonp over iframe transport similar to the
one I had developped for my jquery-jsonp plugin (soon to be obsolete,
hopefully). Made me confident enough coding a new transport and
binding it to a dataType is both easy and non-intrusive. I have some
refactoring to do between $
OK, I tested to be sure. Latest source tree does not pass tests in IE.
2009/12/9 DBJDBJ
> @John, never be "away from an IE capable computer" ;o)
> Just when you think you are free, they pull you in again ;o)
>
> PS: Yes,yes.. this is really me : DBJ
>
> On Dec 9, 4:15 pm, John Resig wrote:
> >
Although, certainly any page that lacks support for iframes is going
to also have significant problems running jQuery.
At this point though, I do agree - a bit too much magic.
--John
On Wed, Dec 9, 2009 at 9:24 AM, Dave Methvin wrote:
> This creates a divergence between what a CSS selector me
> Fixed the ant build (build.xml) to clone/pull both Sizzle and QUnit. Tested
> on Windows XP.
So *that's* why it started working. Thanks, Jörn!
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-.
This creates a divergence between what a CSS selector means and what a
jQuery selector means. Think about this code:
http://google.com";>
This browser doesn't support iframes, or has them disabled.
This css selector will make the error message bold:
iframe p { font-weight: bold }
With th
@John, never be "away from an IE capable computer" ;o)
Just when you think you are free, they pull you in again ;o)
PS: Yes,yes.. this is really me : DBJ
On Dec 9, 4:15 pm, John Resig wrote:
> The code as of when 1.4a1 came out was passing 100% in IE 6, 7, and 8.
> I'm away from an IE-capable co
That "post" is an obvious fake, ... although it is indeed
hillarious ;o)
Of course, can't wait for this google group to be closed ... I
remember much worse posts than this one...
--DBJ
On Dec 8, 7:01 pm, Ali Karbassi wrote:
> I want to see how many people will actually add this to their code.
>
I want to see how many people will actually add this to their code.
On Dec 8, 8:28 am, DBJDBJ wrote:
> Also please be sure to have jquery attribute present, like so:
>
> jquery="1.3.2" >
>
> This switches on, undocumented jQuery event handling. And also
> greatley improves the overal conformance
Hello everyone,
I've just added some new comments to an old bug #2551 (
http://dev.jquery.com/ticket/2551 ) that is still open from back in
the 1.2 days. I just ran into it today and dug into what was really
the problem.
Basically if you don't add a "selected" attribute to one of your
options and
Is there a reason why in the jQuery.ajax() method beforeSend() is
called AFTER the xhr.open() method?
The problem is that the readystatechange event for OPENED (1) is not
called in WebKit browsers(Safari, Chrome) when you bind a handler to
the xhr.onreadystatechanged after the connection has been
Hello,
On Tue, Dec 08, 2009 at 11:06:31PM -0800, John Resig wrote:
> The problem with this particular proposal is that it kind of throws
> out the fact that Sizzle works right to left on the selector. We
> currently evaluate the left-hand-side of the selector first ONLY if
> there's an #id at the
The code as of when 1.4a1 came out was passing 100% in IE 6, 7, and 8.
I'm away from an IE-capable computer at the moment (traveling) so I'm
not sure if it's still the case - at least it was as of last Friday.
--John
On Wed, Dec 9, 2009 at 7:51 AM, Julian Aubourg wrote:
> Just curious, do the
Just curious, do the event module unit tests pass in IE ? Acts all weird for
me (including a nasty redirection) but I'm not sure if it's because of my
ajax rewriting or not.
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this g
2009/12/9 Matt :
> On Dec 5, 5:42 pm, Mike Taylor
> wrote:
>> You're probably getting the Exception 5 due to the "-" in the attribute
>> name, which is illegal.
>
> Should jQuery crash when passed a value it doesn't like?
>
It's not a jQuery thing, it's a browser thing. I would imagine that
check
On Dec 5, 5:42 pm, Mike Taylor
wrote:
> You're probably getting the Exception 5 due to the "-" in the attribute
> name, which is illegal.
Should jQuery crash when passed a value it doesn't like?
Matt Kruse
--
You received this message because you are subscribed to the Google Groups
"jQuery De
28 matches
Mail list logo
