Works very nicely! I've had some small issues with getting the HTML
Tidy plugin to work, but I think thats a local paths issue rather than
a bug in your code, but I'll let you know more - i'm looking into it
today.
On 6/8/07, Jean-Francois Hovinne <[EMAIL PROTECTED]> wrote:
This one could d
This one could definitely solve the problem, if it complies to
jQuery's requirements.
FYI, WYMeditor 0.3 has been released, as a jQuery plugin.
Any feedback is welcome.
On 7 juin, 14:17, Volker Mische <[EMAIL PROTECTED]> wrote:
> I've written a new patch, please take a look
> athttp://dev.jque
Hi,
> I've added a new patch to the ticket based on Volker's patch. Can you please
> confirm that it does indeed fix the problem?http://dev.jquery.com/ticket/1143
No it doesn't work as it doesn't travers all node recursively. I've
written a new patch, please take a look at http://dev.jquery.com/
I've added a new patch to the ticket based on Volker's patch. Can you please
confirm that it does indeed fix the problem?
http://dev.jquery.com/ticket/1143
--
Brandon Aaron
On 5/24/07, Jean-Francois Hovinne <[EMAIL PROTECTED]> wrote:
Thanks for your quick reply, John, and sorry for annoying y
Hi John, I quickly tested jQuery 1.1.3a with my jVariations plug-in and it
crashed Safari (immediately). I'm going to take a look into it this week and
will hopefully be able to provide more information. The page I was testing
it on was quite complex and Safari was already struggling (taking a few
Hi,
> > I have to admit that I haven't found a faster solution.
> > removeAttribute() just takes to much time. So perhaps the serializer
> > should be "fixed". This would mean a slow down for Internet Explorer
> > on html(), but this seems ok for me, as this is a Internet Explorer
> > bug.
>
> Th
I have to admit that I haven't found a faster solution.
removeAttribute() just takes to much time. So perhaps the serializer
should be "fixed". This would mean a slow down for Internet Explorer
on html(), but this seems ok for me, as this is a Internet Explorer
bug.
That's absolutely a possibi
Hi,
I have to admit that I haven't found a faster solution.
removeAttribute() just takes to much time. So perhaps the serializer
should be "fixed". This would mean a slow down for Internet Explorer
on html(), but this seems ok for me, as this is a Internet Explorer
bug.
Something different: merg
I think mergeNum won't be added everytime, it gets only added if you
need to run an uniqueness test (when find() was called). I even think
unique() can be removed when merge gets changed a bit. I've some
ideas, at the end it should be faster and have a smaller file size.
Cu,
Volker.
On 24 Mai,
Hi,
On 24 Mai, 22:39, "John Resig" <[EMAIL PROTECTED]> wrote:
> $(...).find("*").each(function(){ delete this.mergeNum; });
This won't work in Internet Explorer.
> Having the value come up as mergeNum="null" tells me that there's
> something very wrong at play here. What exactly are you using
Just a side note, that will probably crash IE. IE doesn't like to
delete things from elements.
--
Brandon Aaron
On 5/24/07, John Resig <[EMAIL PROTECTED]> wrote:
What if you straight-out delete the property?
$(...).find("*").each(function(){ delete this.mergeNum; });
Having the value come up
What if you straight-out delete the property?
$(...).find("*").each(function(){ delete this.mergeNum; });
Having the value come up as mergeNum="null" tells me that there's
something very wrong at play here. What exactly are you using to
serialize the contents of the designMode area?
--John
On
Not sure. There's still a lot of tricky bugs that have popped up, that
we still need to find the root cause of (then patch, fix, and
re-test). Not to mention backporting the documentation from the wiki
into the codebase again. I'm leaning more towards mid-next week.
--John
On 5/24/07, Shelane E
Thanks for your quick reply, John, and sorry for annoying you with
that issue, but it seems to be a major blocker for WYMeditor to work
correctly with jQuery in MSIE.
I did test the fix you propose (this.mergeNum = null).
The attribute is still there, i.e. mergeNum="null" for each element.
This
Is there still the possibility of a final release this week?
I've tested against the basics and some of my more complicated internal apps
and all is working well.
On 5/24/07 1:10 PM, "John Resig" <[EMAIL PROTECTED]> wrote:
>
> Did you test it against the test suite? And did you test it for sp
Did you test it against the test suite? And did you test it for speed
changes? The reason why this is being done, in the first place, is
purely for speed reasons. Added extra checks or loops significantly
slows down the speed of jQuery selectors. The mergeNum technique is
the fastest means of che
I've applied and tested the patch with MSIE, FF (Win + Linux) and
Opera.
Works fine for me! Thanks Volker :)
I've committed the patched jQuery to WYMeditor SVN [1].
A test page is available at [2].
[1]: svn://svn.wymeditor.org/wymeditor
[2]: http://dev.wymeditor.org/wymeditor/trunk/src/test/adva
Hi,
please take a look at my patch for ticket http://dev.jquery.com/ticket/1143
I'm not sure why mergeNum was actually used, I think a simple boolean
should be enough.
Cu,
Volker.
On 21 Mai, 14:39, Jean-Francois Hovinne <[EMAIL PROTECTED]>
wrote:
> Thanks for your help.
>
> Actually, I can re
On 5/21/07, Daemach <[EMAIL PROTECTED]> wrote:
The tabs plugin uses the fadein/out effects - I'll bet it has
something to do with a bug I just found. It's hard to describe - I'm
just glad I could replicate it. Test case below.
http://ideamill.synaptrixgroup.com/jquery/test/113fxbug.htm
Go
The tabs plugin uses the fadein/out effects - I'll bet it has
something to do with a bug I just found. It's hard to describe - I'm
just glad I could replicate it. Test case below.
http://ideamill.synaptrixgroup.com/jquery/test/113fxbug.htm
On May 21, 4:38 pm, "Aaron Heimlich" <[EMAIL PROTECTE
You're right. When I was testing that it turns out that I wasn't
passing any arguments to my function, and it would have behaved the
same way in 1.1.2. However, my example is a good one - in this case,
I still want the last object's properties applied. Does it make sense
to modify the extend fu
I can confirm the same issue on Firefox 2.0.0.3, Safari 2.0.4 (build 419.3),
and Opera 9.20 (build 3669) (all on Mac OS 10.4.9)
On 5/21/07, Glen Lipka <[EMAIL PROTECTED]> wrote:
Working tabs plugin with 1.1.2
http://www.marketo.com/about/contact.php
Broken with 1.1.3
http://www.marketo.com/tem
On 5/21/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Daemach wrote:
> It appears that extend no longer extends objects with more than one
> object. In 1.1.2 I could do:
>
> this.settings = jQuery.extend({}, this.defaults,
> arguments.options, this.userOptionsFromCookie); // named to
> il
Daemach wrote:
It appears that extend no longer extends objects with more than one
object. In 1.1.2 I could do:
this.settings = jQuery.extend({}, this.defaults,
arguments.options, this.userOptionsFromCookie); // named to
illustrate purpose
Now, only the arguments.options values extend th
It appears that the helper method "left" has been removed from the
API. Try replacing left with $().css('left', 260);
--
Brandon Aaron
On 5/21/07, Dragan Krstic <[EMAIL PROTECTED]> wrote:
2007/5/21, Brandon Aaron <[EMAIL PROTECTED]>:
>
> Do you know what version/rev of the dimensions plugin y
It appears that extend no longer extends objects with more than one
object. In 1.1.2 I could do:
this.settings = jQuery.extend({}, this.defaults,
arguments.options, this.userOptionsFromCookie); // named to
illustrate purpose
Now, only the arguments.options values extend the defaults. Is t
2007/5/21, Brandon Aaron <[EMAIL PROTECTED]>:
Do you know what version/rev of the dimensions plugin you are using?
What browser(s) are you having problems with?
I'm not quite sure. I'm using striped off version. File is created on
January,18th. In firebug I'm getting the following:
headlines
Do you know what version/rev of the dimensions plugin you are using?
What browser(s) are you having problems with?
Here is the latest version's test suite running on 1.1.3:
http://brandonaaron.net/jquery/plugins/dimensions/test/unit.html
--
Brandon Aaron
On 5/21/07, Dragan Krstic <[EMAIL PROT
I have a problems with dimensions plugin. width and height couldn't be read
John Resig wrote:
Hi Everyone -
A test build of the upcoming 1.1.3 release is ready for everyone to
try. We need to be super-sure that there haven't been any regressions
in this release, and in order to do that we'd like you to download
this alpha release and try it in place of jQuery 1.1.2 (w
I've just tested it with Chili 1.8 and all is ok.
Just a little thing: the show() / hide() functions work much slower than
before and they have a 'nice' (quoted because not needed nor requested)
transition effect, which is maybe responsible for the slow-down factor.
hide() is a bit faster than s
I think we are supposed to ignore $attrs in IE.
I was amazed to see mergenum sneak through! $mergenum should work as well,
but should be ignored.
in http://jqueryjs.googlecode.com/svn/trunk/plugins/debug/
I happily ignore attributes that start with $
On 5/21/07, Jean-Francois Hovinne <[EMAIL PR
Thanks for your help.
Actually, I can remove the attribute using removeAttr, but the extra
DIVs remain (for example if you create inline elements in lists).
IMHO, as the problem only occurs in MSIE - no mergeNum issue in Gecko
nor in Opera - I'm rather thinking about a browser specific issue.
T
Jean-Francois Hovinne ha scritto:
Well, I've replied to Brandon (by email) that his fix didn't work: the
mergenum attr simply becomes $mergenum in the resultant HTML code.
Using other variable names (such as 'mytest') doesn't fix the problem.
Using the code you propose (this.mergeNum = null;)
Well, I've replied to Brandon (by email) that his fix didn't work: the
mergenum attr simply becomes $mergenum in the resultant HTML code.
Using other variable names (such as 'mytest') doesn't fix the problem.
Using the code you propose (this.mergeNum = null;) generates
mergenum="null" attributes
Max -
Your bug came up here:
http://dev.jquery.com/ticket/1217
It was just being really slow. Thanks for the catch.
--John
On 5/21/07, mpenet <[EMAIL PROTECTED]> wrote:
Keyboard event handling seems broken. event.which seems to be read-
only.
I tried to create a ticket about it but trac do
Keyboard event handling seems broken. event.which seems to be read-
only.
I tried to create a ticket about it but trac doesn't want me too .
You can test it with :
$(document).keypress( function() { alert("Hello"); } );
- then press any key:
"event.which = event.keyCode;"
setting a property th
The proposed fix is not valid, however - due to the fact that it
breaks how the unique() function works (removing duplicate items).
Additionally, the only 'fix' is to traverse through every element and
remove all the mergenum properties - which is a major slowdown for all
selectors.
In what cas
Hi,
It would be very nice if bug #1143 could be fixed because it is a
major blocker for WYMeditor (MSIE version) to generate correct XHTML.
A fix is proposed (commenting out one line), and seems to work fine
(also tested with 1.1.3a).
http://dev.jquery.com/ticket/1143
Thank you,
Jean-François
h
I've posted my thoughts here:
http://dev.jquery.com/ticket/1212
"This is because both of the plugins overwrite the easing object
instead of extending it :-( The default easing in jQuery is called
'swing' - which isn't available in either plugin (thus causing the
errors). I assume that if the eas
Hey John,
tested tons of selectors and all appear to be working as expected.
also, .fadeIn() after .hide() is working again, as is .fadeIn
() / .fadeOut() with table rows. Hooray!!
looks like there is a bug with animations whenever an easing plugin
is included in the file. Created ticket :
Glen -
A more-specific example would be great (using a copy of 1.1.3a). Feel
free to post the URL once you have it up.
--John
On 5/20/07, Glen Lipka <[EMAIL PROTECTED]> wrote:
Just to see, I swapped our 1.1.2 and put in the link you had above.
It broke the Tabs plugin.
http://www.marketo.com/
I've tested it and zebra striping is fine, mouseover/out highlighting
is fine, getJSON is still fine as well.
Tested with Fx 2.0.0.3, IE7 and IE6 (SP2) on Windows XP.
On May 21, 11:29 am, "John Resig" <[EMAIL PROTECTED]> wrote:
> Hi Everyone -
>
> A test build of the upcoming 1.1.3 release is re
Just to see, I swapped our 1.1.2 and put in the link you had above.
It broke the Tabs plugin.
http://www.marketo.com/about/contact.php
Also, my RSS problem previously posted.
Firefox still worked both, but now IE couldn't load either one.
http://www.marketo.com/rsstest.htm
I can put up sample pa
ohh me goodies, will try. thanks for the heads up
cheers
-Nilesh
On May 20, 9:29 pm, "John Resig" <[EMAIL PROTECTED]> wrote:
> Hi Everyone -
>
> A test build of the upcoming 1.1.3 release is ready for everyone to
> try. We need to be super-sure that there haven't been any regressions
> in this r
45 matches
Mail list logo
