John Resig schreef:
> Hi Everyone -
>
> We've just pushed jQuery 1.1a live. This is a testing release - so
> your help would be appreciated in testing it out and finding any bugs.
> 1.1 will be released this weekend (January 14th).
>
> Here's the quick-and-dirty on jQuery 1.1:
> * Its selectors ar
First bug (let me know if I'm crazy):
$("garbage")[0] returns window, not undefined as I'd expect.
-- Yehuda
On 1/8/07, John Resig <[EMAIL PROTECTED]> wrote:
Hi Everyone -
We've just pushed jQuery 1.1a live. This is a testing release - so
your help would be appreciated in testing it out and
Hi Everyone -
We've just pushed jQuery 1.1a live. This is a testing release - so
your help would be appreciated in testing it out and finding any bugs.
1.1 will be released this weekend (January 14th).
Here's the quick-and-dirty on jQuery 1.1:
* Its selectors are 10-20x faster than those in jQue
it's a silly offset() exception that doesn't work when you don't give it
elements. That's not normal jQuery behavior and, imho, should be changed.
-- Yehuda
On 1/7/07, Aaron Heimlich <[EMAIL PROTECTED]> wrote:
Hey Yehuda,
Very cool stuff! But I get the following error in Firefox whenever I cl
One other thing:
It only happens when you're NOT looking at the docs for a particular
function.
On 1/7/07, Aaron Heimlich <[EMAIL PROTECTED]> wrote:
Hey Yehuda,
Very cool stuff! But I get the following error in Firefox whenever I click
on the blue arrow in the header that points to the right:
Hey Yehuda,
Very cool stuff! But I get the following error in Firefox whenever I click
on the blue arrow in the header that points to the right:
uncaught exception: jQuery.fn.offset requires an element. (no line # given)
It happens in IE (and, given the message, I would assume others as well)
t
You can IM me at outlookeic.
-- Yehuda
On 1/7/07, Ⓙⓐⓚⓔ <[EMAIL PROTECTED]> wrote:
I understand about browsers stuck at xsl 1, and when you try something
new... they break!
Do you have a handle on the incompatibility or do you need some xsl
help? I've written some mean xsl 2 code, that won't ru
I understand about browsers stuck at xsl 1, and when you try something
new... they break!
Do you have a handle on the incompatibility or do you need some xsl
help? I've written some mean xsl 2 code, that won't run on any
browser, but makes some pleasant xhtml.
PS
I read every line of the original
Excellent work - Looks great. As Karl mentioned, having a wider content
area makes it look alot neater.
Allan
Yehuda Katz wrote:
> Mozilla wasn't liking the XSL sheet this time around, so I'm doing the
> transform through Oxygen. I'm going to be finding a better solution to
> automate this t
Mozilla wasn't liking the XSL sheet this time around, so I'm doing the
transform through Oxygen. I'm going to be finding a better solution to
automate this thing better.
I'm also going to be releasing an offline version in the near future in
conjunction with jQuery 1.1.
Regarding the Methods plu
Excellent job, Yehuda! It's looking fantastic! Love the shorter title
bar and the wider text area.
Looks like Jörn's Methods plugin is showing up in the JavaScript
section, but unless it's moving into core, it should probably go in
the Plugins section.
Keep up the great work!
--Karl
___
It's beautiful! Your site has always been my first stop for reading the docs!
is it still xsl based? Did you have to do it offline because of xsl 2 stuff?
On 1/7/07, Yehuda Katz <[EMAIL PROTECTED]> wrote:
> Hey guys,
>
> I've been listening to all of the feedback I've gotten about Visual jQuery,
Hey guys,
I've been listening to all of the feedback I've gotten about Visual jQuery,
and I've built a new version that I believe responds to many of those
concerns:
* a dramatically reduced title-bar (20px high)
* a "path" in the titlebar indicating the current location in the API tree
* the "te
I think the feature I like most is
- Added attr(String,Function) to calculate the value and support for
attr("key", "${formula}") syntax, a shortcut for the former...
that opens a lot of doors!
On 1/7/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Ⓙⓐⓚⓔ schrieb:
> > that looks sweet... are the sp
Ⓙⓐⓚⓔ schrieb:
> that looks sweet... are the specs of 1.1 online anywhere?
>
Sort of: http://jquery.com/dev/svn/trunk/jquery/ChangeLog.txt?format=txt
--
Jörn Zaefferer
http://bassistance.de
___
jQuery mailing list
discuss@jquery.com
http://jquery.c
Thanks Brandon! For the lazy, get the latest version here:
http://jquery.com/dev/svn/trunk/plugins/dimensions/dimensions.js?format=raw
Or all the files related to the plugin here:
http://jquery.com/dev/svn/trunk/plugins/dimensions/
--Erik
On 1/7/07, Brandon Aaron <[EMAIL PROTECTED]> wrote:
> I ju
that looks sweet... are the specs of 1.1 online anywhere?
On 1/7/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Fabien Meghazi schrieb:
> >> $('#foo').mouseout(function(e) {
> >>if (this == e.target) {
> >> // do your magic
> >>}
> >> }
> >>
> >> In essence, check that the item being
Give this a try.
http://methvin.com/jquery/splitter/
Oskar, it sounds like you may have solved some of the problems with IE6 I
haven't tackled yet. This version doesn't yet handle min-width and max-width
for IE6 but I plan to put it there. Maybe we could join forces on this? It
looks like you've
Fabien Meghazi schrieb:
>> $('#foo').mouseout(function(e) {
>>if (this == e.target) {
>> // do your magic
>>}
>> }
>>
>> In essence, check that the item being moused out of is in fact the
>> item that the handler is attached to.
>>
>
> Wow ! Thanks a lot ! It is indeed what I'm se
if delete means get rid of that binding forever, unbind('mouseout')
if delete mean don't bother with the event anymore, jquery's
e.stopPropagation() should do it.
We've learned a lot in this thread!
On 1/7/07, Fabien Meghazi <[EMAIL PROTECTED]> wrote:
> > $('#foo').mouseout(function(e) {
> >
I just finished checking in some major updates to the dimensions plugin.
* Added unit tests
* Fixed a bug in .innerHeight() and .innerWidth()
* Major refactor of .offset() method to be faster and fix a couple of bugs
* Added a test/example/benchmark page for the .offset() method
All of this can b
Dan Atkinson schrieb:
> Hey all!
>
> I'm currently in the review process for an extension which basically puts
> jQuery on EVERY page. I did it after reading something on learningjquery
> which uses a bookmarklet.
>
> I'm pretty sure that there will be issues surrounding it (GMail had a weird,
> lo
> $('#foo').mouseout(function(e) {
>if (this == e.target) {
> // do your magic
>}
> }
>
> In essence, check that the item being moused out of is in fact the
> item that the handler is attached to.
Wow ! Thanks a lot ! It is indeed what I'm searching for.
By any chance, is it possible
Thanks, that worked!
Brandon Aaron wrote:
>
> Well if you want to replace the HTML within the div you should use
> .html() but if you want to just add some HTML to the div then you
> should use .append() or .prepend().
>
> So if you first .load() and then in the callback do a .prepend() to
> a
On Jan 5, 2007, at 17:30 , Fabien Meghazi wrote:
> I'm trying to have a div displayed over the link when we click on it.
> When we mouse over the displayed div, I want it to disapear.
> My problem is that in the div I have many elements and some links.
> When the mouse come over a link, the mouseo
Great idea!
The extension should be able to provide different versions of jQuery.
And something off the topic, so far jQuery is popular in web page
development, I wish Firefox extension development could benefit from jQuery
too.
On 1/8/07, Dan Atkinson <[EMAIL PROTECTED]> wrote:
I suppose that
Well if you want to replace the HTML within the div you should use
.html() but if you want to just add some HTML to the div then you
should use .append() or .prepend().
So if you first .load() and then in the callback do a .prepend() to
add HTML to the top of the div that should solve the problem.
Have you tried to use the .hover() event? You can find the docs for it
at http://jquery.com/api/ and then click on 'H' or via
http://visualjquery.com/ and click on 'events' and then 'hover'
--
Brandon Aaron
On 1/7/07, Sanyi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I have a site:
>
> http://mumor.
Hi All,
I have a site:
http://mumor.freeweb.hu/gocsej/
on the left side there is a menu, left beside there is a picture with
transparent gif's to emulate some stonemovings. I used normal Javascript and
Jquery mix on the mouseover and mouseout event to handle the hovering event.
But when you run
I suppose that the inclusion of jQuery in each and every web page is in my
aim of providing jQuery-using plugins inside the browser, rather than a
single website.
The Wordpress plugin is borne out of intense frustration with the powers
that be behind it. In their short-sightedness, they're forcin
Hello,
I've been stuck for a moment trying to do as following:
1) Insert the specified HTML code to a div
2) Append whole content of the specified HTML file to the same div.
As for know I may only do one of these points. Can't combine them together.
Any suggestions how to easily combine load(
This sounds very cool Dan. In terms of including jQuery on every page,
what are the applicabilities? Can you give some examples of usage? This
would be very helpful in our jQuery evangelism efforts and will help me
tell users how to best use this.
The Wordpress plugin is also a great idea and w
Kelvin: I should have known that syntax was available. I use it all the
time in ColdFusion, but didn't realize I could use it in JavaScript too.
I know to avoid eval, but thought I had no choice in this case. You can
be sure I'll use this method! :o)
Klaus: Thanks so much for your comments on
Hey all!
I'm currently in the review process for an extension which basically puts
jQuery on EVERY page. I did it after reading something on learningjquery
which uses a bookmarklet.
I'm pretty sure that there will be issues surrounding it (GMail had a weird,
long button when I put jquery on my i
Christopher Jordan schrieb:
> Yeah, that's actually where I found my answer Klaus. I'm a bit
> embarrassed that I basically posted the question a second time. It
> didn't immediately occur to me that I could do the same thing with
> "input:type" that I could with ".classA". I'm not a css stud so
Ⓙⓐⓚⓔ schrieb:
> the simple way to stop bubbling is to return false.
> the only time I needed anything else was to activate the href after
> the click got caught.
> if (!e) {
> var e = window.event
>
>
> var obj = new Object;
> // all inputs of type text, hidden, select and textarea
>
> $("input:text,input:hidden,select,textarea").each(function(){
> eval("obj." + this.name + " = '" + this.value + "';");
> });
Hello folks,
Despite my best efforts to understand previous posts about multiple
firings of functions, I'm still having difficulty with a section of
code that persists in firing twice.
When a particular section of a page is loaded, a function is
triggered which completes an ajax call to load
38 matches
Mail list logo
