Isn't that just a quick regex away from making it work with the new syntax?
-- dz
On Fri, Oct 2, 2009 at 10:26 AM, Matt Kruse m...@thekrusefamily.com wrote:
My example code uses this selector syntax: t...@class^=child-]
Support for [...@attribute...] has been changed to just
He's using the unit testing framework, so that part isn't needed
-- dz
On Tue, Sep 22, 2009 at 3:38 PM, DBJDBJ dbj...@gmail.com wrote:
It is blatantly obvious and therefore difficult to spot ...
I think your test page does things without
$( function () {
...
}) ;
It that matters ?
On Sep 2, 2009, at 9:33 PM, DBJDBJ wrote:
@dz: At last a number for you ;o) Andrea says that IE versions of jQ
are 10 times slower ...
We already knew that -- jQuery in IE is slower because:
1. The workarounds are slower.
2. IE6/7/8's js engines are slower.
The slowness of jQuery -- or
Then run some tests! Take your no brainers, apply them to a recent
checkout of jQuery, and record some data!
You said that separating out IE stuff from jQuery into a separate
branch would show measurable benefits (in spead increase and
stability).
I'll repeat, because you seem to have missed
On Tue, Sep 1, 2009 at 11:45 AM, DBJDBJdbj...@gmail.com wrote:
@dz No offence, but why are you taking part in this pointless
discussion ?
Because if there *is* a significant speed increase, it's valid and
therefore interesting. There's a lot of sound and fury, but not a lot
of data.
I am
The easiest way is to just use a class or id on the body:
body class=base_theme theme_1
js:
$('body').removeClass('theme_1').addClass('theme_2');
-- dz
On Tue, Sep 1, 2009 at 11:08 AM, Badbeerinsyn...@gmail.com wrote:
If it were me, I'd do it differently. For example:
In my page, I
On Mon, Aug 31, 2009 at 3:08 AM, DBJDBJdbj...@gmail.com wrote:
My intent
Develop simpler, faster and more stable jQuery. This kind of delivery,
would show measurable benefits (in spead increase and stability). It's
a no brainer: Imagine jQuery with zero IE workarounds inside.
I've yet to
Couldn't you do:
if(!!$(ele).attr('disabled')) {
//stuff
}
-- dz
On Thu, Aug 27, 2009 at 1:15 PM, William Changdiehardb...@gmail.com wrote:
Hey Matt,
I understand now. Thanks!
So, how do you avoid using attr() when you need to check for an
attribute in the element? And, getting
jQuery and IE old : I am wondering why mainstream jQ supports IE6
actually? How many developers actually need and use that? Who and when
will be developing an web app today , that will run on IE6 too ? 99%
of web apps developed on jQ are new apps for new browsers.
That's a pretty myopic
To clarify: run on does not mean fully support. Products can and
should have different grades of support. But this does not mean
completely disregarding IE6 or 7.
In any case, jQuery should not be making that sort of decision.
Unless supporting IE6/7 is imposing significant roadblocks to the
Exactly. Also, two things:
1. Can we stop with the silly M$ nomenclature? We're not script
kiddies with an axe to grind.
2. Again, building an advanced web application does not mean
forgetting the lessons of progressive enhancement. Using advanced
features of newer browsers does not preclude
On Mon, Jul 20, 2009 at 2:46 AM, DBJDBJdbj...@gmail.com wrote:
Well the only reason this is a link to a blog is the image present.
Which speaks a thousand words. Which in turn should make the
discussion here productive.
Same as any other useful discussion on this good forum about legacy
jquery-dev is not your personal soapbox. If you're going to
shamelessly plug your blog, can you at least plug a post that's
reasonably related to jquery development?
/rant
-- dz
On Sun, Jul 19, 2009 at 1:13 PM, DBJDBJdbj...@gmail.com wrote:
http://dbj.org/dbj/?p=244
--DBJ
Checkout the jQuery svn repo, make your changes and generate a diff.
-- dz
On Tue, Jun 16, 2009 at 11:34 PM, vdhant vdh@gmail.com wrote:
Hey guys
In the meantime how could I go about creating my own patch that fixes
this issue???
Cheers
Anthony
On Jun 17, 1:11 pm, Daniel Friesen
Just do a document.write() and bypass jQuery.
if (thehour = 18)
document.write(...);
Since you're just checking time, you don't need to wait for the DOM to be
ready or any of that sort of thing.
-- dz
On Thu, Jun 4, 2009 at 12:23 PM, jez j...@h4x3d.com wrote:
Hello,
I am almost certain
I wonder if it's feasible to monkeypatch debugging wrappers around
jQuery core methods. You don't even need it to throw errors -- a
simple console.log warning would suffice.
-- dz
On Tue, May 19, 2009 at 8:38 AM, Julian Aubourg
aubourg.jul...@gmail.com wrote:
jquery.debug.js /
or else you won't know anything about the
context of the problem.
Of course, I'm talking from the point of view of someone who develops sites
that are ultra-heavy in the js department.
2009/5/19 David Zhou da...@nodnod.net
I wonder if it's feasible to monkeypatch debugging wrappers around
jQuery
wrote:
On May 19, 7:51 am, David Zhou da...@nodnod.net wrote:
I wonder if it's feasible to monkeypatch debugging wrappers around
jQuery core methods. You don't even need it to throw errors -- a
simple console.log warning would suffice.
Definitely feasible. See something I posted here
On Thu, Apr 16, 2009 at 12:48 AM, Pink Pig
b...@grandcentralapartments.com wrote:
On Apr 15, 7:11 pm, Ricardo ricardob...@gmail.com wrote:
Try a search for '@' in the plugin files, it shouldn't be hard.
On Apr 15, 3:59 am, Pink Pig b...@grandcentralapartments.com wrote:
Maybe you guys
On Fri, Apr 3, 2009 at 8:42 AM, Dev ajoymahat...@gmail.com wrote:
script language=jscript
This should be:
script type=text/javascript
-- dz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
jQuery
Yup. From http://docs.jquery.com/Release:jQuery_1.3:
The '@' in [...@attr] has been removed. Deprecated since 1.2 this old
syntax no longer works. Simply remove the @ to upgrade.
-- dz
On Fri, Apr 3, 2009 at 12:43 PM, Elijah Insua tmp...@gmail.com wrote:
using @ to specify attributes was
How many times did you run your tests? Are these averages?
Also, did you try the tests on a non-Windows XP or Vista machine to
get more accurate results? (At least for Firefox and Opera).
I don't doubt that pure DOM manipulation is going to be faster, but
it's certainly surprising to see how
, Apr 2, 2009 at 10:41 AM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
if you want to try the test you can visit this page:
http://bill.dojotoolkit.org/taskspeed/
or create a local TaskSpeed implementation
On Thu, Apr 2, 2009 at 3:19 PM, David Zhou da...@nodnod.net wrote:
How many
On Wed, Apr 1, 2009 at 2:08 PM, Ryura yoyobo...@gmail.com wrote:
This is not great, its absolutely terrible. IE6 is the WORST browser
on the web. I would have expected the jquery-dev list to be a bit more
intelligent toward this matter. IE is slow and clunky. ActiveX is not
a good feature,
On Tue, Mar 24, 2009 at 4:29 PM, Dean Edwards dean.edwa...@gmail.com wrote:
On Mar 24, 8:09 pm, John Resig jere...@gmail.com wrote:
Why would you want this?
It will stop plugins from interfering with each other.
If a plugin has an error in its document.ready handler it will prevent
Emacs doesn't float everyone's boat -- and I'm a Vim user myself --
but the best javascript editing mode I've ever used or seen is
probably js2 mode in Emacs. I think it ties with IntelliJ at the very
least. YMMV.
-- dz
On Mon, Mar 16, 2009 at 4:59 AM, Mark Gibson jollyt...@gmail.com wrote:
To help with test cases, here are a couple tools to help with the boilerplate:
http://jquery.nodnod.net/
http://jsbin.com/
-- dz
On Tue, Feb 24, 2009 at 10:32 PM, John Resig jere...@gmail.com wrote:
The best technique to get started is to go in the bug tracker, find an
open ticket and to
I'm not sure I understand your question, but what about something like this:
var itemname1, itemname2;
$('.list-item').each(function(){
if (this.innerHTML.match(/Item Name/))
itemname1 = this;
if (this.innerHTML.match(/Item Name 2/))
itemname2 = this;
});
-- dz
On Sun, Feb
http://dev.jquery.com/ticket/4165 -- sounds like he needed to use live events.
http://dev.jquery.com/ticket/4159 -- invalid
http://dev.jquery.com/ticket/4158 -- patch of fix discovered by initjh
Thanks!
-- dz
--~--~-~--~~~---~--~~
You received this message
http://media.nodnod.net/test.html works for me. Is it because I'm not
serving the page as application/xhtml+xml?
-- dz
On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote:
Me too.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/
2009011913
I wonder if it would be helpful to have a backwards incompatible
changes section for every jQuery release, and a master page somewhere
collating all those changes. The changes are usually highlighted in
the release notes, but it'd be more clear if there was a section
specifically calling out the
that as just general
changes in the upgrade.
-- dz
On Thu, Feb 12, 2009 at 10:31 AM, David Zhou da...@nodnod.net wrote:
I wonder if it would be helpful to have a backwards incompatible
changes section for every jQuery release, and a master page somewhere
collating all those changes. The changes
Couldn't you just do:
jQuery.fn.and = function(sel){
return this.length? this.add(sel) : jQuery([]);
};
-- dz
On Tue, Feb 10, 2009 at 8:57 PM, Dave Methvin dave.meth...@gmail.com wrote:
If you want to work on the elements, though, the .and()
plugin will return either [] or [#field1,
)
-MonkeyScript (http://monkeyscript.nadir-point.com)
-Animepedia (http://anime.wikia.com)
-Narutopedia (http://naruto.wikia.com)
-Soul Eater Wiki (http://souleater.wikia.com)
David Zhou wrote:
Things like .hide() also modify css properties, so I don't see any
aesthetic issue with borderRadius
-tools.com)
-MonkeyScript (http://monkeyscript.nadir-point.com)
-Animepedia (http://anime.wikia.com)
-Narutopedia (http://naruto.wikia.com)
-Soul Eater Wiki (http://souleater.wikia.com)
David Zhou wrote:
While that's true, I think John's point was that since IE doesn't
support it, it shouldn't
That would be pretty sweet. But in the mean time, Jorn, maybe you
could use something like:
jQuery.fn.ifFound = function(condition) {
return (this.length === condition)?this:jQuery([]);
}
So you could do $('#field1, #field2').ifFound(3).length
-- dz
On Sun, Feb 8, 2009 at 5:39 AM, Daniel
Wouldn't this be better as a plugin?
-- dz
On Sun, Feb 8, 2009 at 12:03 AM, Daniel Friesen
nadir.seen.f...@gmail.com wrote:
Both Mozilla and WebKit have built support for border radius (meaning
now only IE and Opera should be left without this kind of feature):
Mozilla with
Isn't that basically:
if ($('.container a:first').length)
$('.container').css('background-color', 'red');
Unless I misunderstand what you're asking for?
-- dz
On Fri, Feb 6, 2009 at 6:58 AM, Jörn Zaefferer
joern.zaeffe...@googlemail.com wrote:
I'm trying to solve the follow selector
;
}).length;
});
filtered.css(background-color, red);
});
That selects the target's parents once, and filters them once for each
container, which is quite acceptable. There probably still is some
better way...
Jörn
On Fri, Feb 6, 2009 at 6:09 PM, David Zhou da...@nodnod.net wrote:
What
', 'red');
});
That avoids fetching parent() twice.
-- dz
On Fri, Feb 6, 2009 at 7:44 PM, David Zhou da...@nodnod.net wrote:
Hmm, what about:
$(function() {
var selection = $(.container);
var target = $(a:first);
while (target.parent().length (target = target.parent
On Wed, Feb 4, 2009 at 11:10 AM, Paul Bakaus paul.bak...@googlemail.com wrote:
On Wed, Feb 4, 2009 at 6:35 PM, ajp alistair.po...@gmail.com wrote:
- Even though STYLE is supposed to live in the HEAD all browsers are
happy to have as many style elements sprinkled around as you like. All
the
I don't have IE8 at hand, but here's a test case with the code above:
http://jquery.nodnod.net/cases/95
-- dz
On Tue, Feb 3, 2009 at 9:00 AM, John Resig jere...@gmail.com wrote:
Do you have a sample page that we can look at? I'm not sure what the
issue is - it may be a problem with IE 8.
On Mon, Feb 2, 2009 at 11:24 PM, Sam Minnee sam.min...@gmail.com wrote:
Is there any way of doing this kind of debugging in jQuery? Or are
there other solutions to this debuggability problem? Perhaps I'm
structuring my code in an inappropriate way?
Check out Visual Events:
Er.. a class with a space is two separate classes.
-- dz
On Thu, Jan 29, 2009 at 4:01 PM, rhasson rhas...@gmail.com wrote:
I run this command $(^.WasPrice) which suppose to find the class
that starts with WasPrice. The actual class name is WasPrice
PriceM. My issue is being to select a
http://dev.jquery.com/ticket/3104
Seeing as last activity was around 4 months ago, is this still being
worked on? I was thinking about working on a patch, but was unsure if
someone had decided to leave the behavior as it currently is.
-- dz
the specifc value for the option
value = jQuery(option).val();
--Karl
Karl Swedberg
www.englishrules.com
www.learningjquery.com
On Jan 28, 2009, at 4:24 AM, David Zhou wrote:
http://dev.jquery.com/ticket/3104
Seeing as last activity was around 4 months ago, is this still
On Wed, Jan 28, 2009 at 10:30 AM, John Resig jere...@gmail.com wrote:
It doesn't matter - one way or the other the broken browser is still
going to be broken - the only difference is that IE is going to be
slower.
I think most of this was hashed over in a prior thread, but the only
tried the lastest nightly build, still got no luck...
On 1月28日, 上午3時09分, helianthus project.heliant...@gmail.com wrote:
Tried that, same result...
On 1月28日, 上午3時07分, David Zhou da...@nodnod.net wrote:
What happens if you use the full un-minified version?
-- dz
On Tue, Jan 27, 2009
This is already in the bug tracker as #3988:
http://dev.jquery.com/ticket/3988
-- dz
On Tue, Jan 27, 2009 at 11:24 AM, John Resig jere...@gmail.com wrote:
Do you have a demo page that we can look at?
--John
On Fri, Jan 23, 2009 at 11:01 AM, helianthus
project.heliant...@gmail.com
He's talking about YASS. The code is here:
http://code.google.com/p/yeasss/source/browse/trunk/src/yass.js
The speed claims are interesting if true, though it looks like it's
still using browser sniffing.
-- dz
On Tue, Jan 27, 2009 at 4:06 PM, Elijah Insua tmp...@gmail.com wrote:
link is
from trunk. At some point there will be an
actual release, probably combined with a blog post, so you'll know
when its done.
Jörn
On Fri, Jan 23, 2009 at 12:15 PM, David Zhou da...@nodnod.net wrote:
Sure, I can add it in. Are there releases of QUnit or do you
typically just grab
Partially out of personal laziness in manually creating test cases
with the same boilerplate over and over again, I made a really simple
app that'll help that process along.
http://jquery.nodnod.net/
For example, here's a sample case:
http://jquery.nodnod.net/cases/7
The dropdowns allow easy
If the behavior of hide or other functions bother you,there's no
reason why you can't override those methods with your own in, say,
jquery-customized.js that you include after jquery.js.
You can also do it similarly for other stuff that bothers you.
There's already an API to the backend, in that
I have a feeling it's related to http://dev.jquery.com/ticket/3873 --
especially with the two .testing classes on the span and div.
On Fri, Jan 16, 2009 at 2:40 PM, John Resig jere...@gmail.com wrote:
Thanks for the test case - I'll be looking in to it!
--John
On Fri, Jan 16, 2009 at
described in the documentation.
I'm a bit new to jQuery development, so if I have wrong expectations
or there's a better way for this, please enlighten me. But I thought
I'd report this in case it really is a bug in Sizzle or jQuery 1.3.
--
---
David Zhou
da...@nodnod.net
, Jan 14, 2009 at 6:45 AM, John Resig jere...@gmail.com wrote:
Hey Everyone -
jQuery 1.3 is out! Full details here:
http://blog.jquery.com/2009/01/14/jquery-13-and-the-jquery-foundation/
Happy 3rd Birthday, jQuery!
--John
--
---
David Zhou
da...@nodnod.net
tabindex=-1Three/li
li tabindex=-1Four/li
li tabindex=-1Five/li
/ul
/body
/html
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
jQuery Development group
other_method
else
other_method2
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
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
is in
the list of options for #usa_reference_state_id.
--
---
David Zhou
da...@nodnod.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
jQuery Development group.
To post to this group, send email to jquery
On Wed, Jan 14, 2009 at 11:39 PM, Matt m...@thekrusefamily.com wrote:
On Jan 14, 3:11 pm, David Zhou da...@nodnod.net wrote:
A new browser to be support would be enough to warrant a new version
of jQuery, I think.
Which would be entirely unnecessary if feature detection is done
correctly
a single option on
my testpage, causing all tests related to selects to fail. Is there an
alternative that I can use that also works with 1.2.6?
There are more which I haven't yet pinned down...
Jörn
--
---
David Zhou
da...@nodnod.net
61 matches
Mail list logo
