@Mike : so you were wrong then ? Although you carefully constructed
your post without any firm yes/no to the status of WebSockets...
I will open WebSocket thread on the forum, just so that we do not
waste more time, then necessary ...
--DBJ
--
You received this message because you are subscribed
1.
Are WebSockets officially part of HTML5 ? Mike I can see the specs,
yes. But this is definitely would be the most questionable HTML5
detail, it seems to me?
This almost introduces synhcronous two-way sockets in the middle of
totaly async www infrastructure... There is no amount of fibre today,
@Tato, WebSocket is specified by Google Inc, and (surpise?) it works
already in CHROME. Google has a plan to have 100% HTML5 compliant
browser to act as the only front end to its OS. In that context
WebSockets are a necessity. And (surprise?) CHROME OS will be talking
only with Goggle servers whic
James, In your source You have to mention whose idea was this
And where have you found out about it : this forum + this thread ...
Thanks : DBJ
On Jan 17, 9:22 pm, James Padolsey
wrote:
> Yesterday, after seeing this thread, I started work on a "jQuery Lint"
> script. You can see it here:h
How about a proxy (aka mediator, aka facade ) pattern ?
Let us call that "facade" : jQLint. An facade to the real jQuery
behind . Let's call its instance: $$
// inside jQlint
(function ( window, undefined ) {
// Define a local copy of jQLint
var jQLint = function( selector, context ) {
Of course by "first" I meant: first , but only on this latest thread.
This is just the latest incarnation of the idea which is not mine...
-- DBJ
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-.
@Jason: yes , you are (also) right, and also :
>
> I think you're still not quite understanding what Dave is suggesting.
>
Funny .. I could swear it was I who suggested this first ;o)
--DBJ
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
@Dave : thanks, you got it right
Also, jQueryLINT is not a plugin, it is version of jQuery itself. With
checks all over the place inside ...
If that effort is owned by jQuery team and efforts channelled, this
should be a great help for addressing the user related issues ... And
this will make ever
; > documentation is a proper anecdote to silence (hence the API docs are
> > > updated to mention this change in 1.4 and it'll be in the release
> > > notes).
>
> > > --John
>
> > > On Wed, Jan 13, 2010 at 11:40 AM, DBJDBJ wrote:
> > > > @John :
http://github.com/jquery/jquery/commit/44e6beb10304789044de2c5a58f5bb82e8321636#comment_42164
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group,
@John : your patience has no limits ...
Although "silent failures" are a "big no-no" in computing, since
primordial times ?
Nice and fresh text :
http://partnerteamblog.shavlik.com/2009/09/02/the-silent-failure-that-leads-to-the-destruction-of-the-system/
And something *much* closer to jQuery us
@Nathan: you just landed yourself a task ;o) Why don't you write
functionExtend() plugin ?
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, se
@blizzard : where is your rc1 coming from ? what OS are you on ?
On Jan 12, 7:22 pm, blizzard wrote:
> I promise I'm not going crazy. I just tried it on IE and Safari, same
> thing, then I tried it on another computer - same time.
>
> Any ideas?
>
> On Jan 12, 1:10 pm, John Resig wrote:
>
>
>
>
I have added this as an "big issue" on the V8 Google code home :
http://code.google.com/p/v8/issues/detail?id=573&q=JSON&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Area%20Stars
Please, "star" this issue to make it more noticeable by the V8
team ...
--DBJ
--
You received
support a little bit. Anyone
> > see any issues with this implementation?
>
> > Alex
>
> > On Jan 10, 5:48 pm, DBJDBJ wrote:
> >> Actually the simplest "way out" is to have new jQuery.support member :
>
> >> jQuery.support.nonstandard_json
Actually the simplest "way out" is to have new jQuery.support member :
jQuery.support.nonstandard_json_string =
function () {
try { JSON.parse("{ a : 1 }"); return true ; } catch(x)
{ return false; }
}();
As far as I know "only" in CHROME :
jQuery.suppor
@Scott, you surprise me ? must be
Also what are the legal attributes to the ?
And last but not the least: in which name space is defined?
--
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 Jan 7, 5:26 pm, John Resig wrote:
> Since we're going to be using JSON.parse, which throws an exception
> (and triggers the Ajax error handler) it should probably be consistent
> across platforms.
well it might not be consistent across platforms, since in CHROME
window.JSON.parse will happil
@John, I did not say it clearly, so I will do it now: I agree 100%
with no-compromise approach to "non-standard" (aka illegal) JSON
strings. It is only that in reality, there are well known and
(commercial) paid for RESTfull services, which return this wrong kind
of JSON. Especially this kind :
@Juilan, believe me I was on the JSON secuirty issue more than once
with Mr Crockford.
The issue I have pointed out is that one can have whole functions as
symbol names in JSON.
And then execute them with an inoccently looking "sleeper"
On Jan 7, 2:49 pm, Julian Aubourg wrote:
> What I'm worried
Sensible approach. But how is the following issue of using "non
standard" JSON strings solved :
IE8:JSON.parse("{ 'a':1 }") ---> Syntax Error
CHROME:JSON.parse("{ 'a':1 }") ---> OK
FF: JSON.parse("{ 'a':1 }") ---> Syntax Error
OPERA 10.10: JSON.parse
Sorry ... here is the proper cross browser version:
if (
("undefined" !== typeof JSON)
&&
(JSON.stringify(document.createElement("input").value)!== "" )
)
{
var _stringify = JSON.stringify;
JSON.stringify = function(o, f, s){
return _stringify(o === "" ? "" : o , f, s);
John,
I was wondering if You would like to add to 1.4, this simple solution,
for the IE8 JSON.stringify bug, as described here:
http://blogs.msdn.com/jscript/archive/2009/06/23/serializing-the-value-of-empty-dom-elements-using-native-json-in-ie8.aspx
if (JSON.stringify(document.createElement("in
"Confusion is always the most honest response."
-- Marty Indik
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-d
Ok, this is what exactly I wanted to mention but did not, in order not
to make a moot point...
Indeed, dom tree has 4 singletons (not one) :
html, head, document and body + window (aka host) which is not a dom
node "per se".
Whatever the "users are expecting". jQuery "holds" only one: a
document.
This is one of the many example of what am I talking about. People
just "don't care" about instances of jQUery, because they can. I would
alwys tryu to minimise the number of jQuery instances, and make them
"obvious" vs "hidden" :
var $b = $(document.body) ,
// why would anyone ever do : $("html,b
What would happen if jQuery would "force" a "singleton" for a host
document ?
What if :
$()
$("html")
$( document )
... etc
Would all point to the same jQuery instance ? One document one jQuery.
Do we already have it in core.js :
// A central reference to the root jQuery(document)
rootj
Oh, how true my daddy was: "Son (he said) always make the manual first
and then give it to the customers. And then son, wait for the dust to
settle. And then my son, then start making, whatever is that thing,
you are selling my son" ...
--DBJ
On Dec 18, 8:30 pm, John Resig wrote:
> > What about
17, 4:25 am, John Arrowwood wrote:
> And what would this mean in the case where I have downloaded an XML document
> via $.ajax()? That $ will not be an observer of the $(document) instance,
> will it?
>
> Or if I create fragments that are not yet in the DOM, such as
>
> va
MutationEvents are fired whenever and wherever any CRUD operation is
done on the document tree.
To do this, one needs to redesign jQuery to follow an Observer
pattern.
Where observable is a single instance of jQ 'mutator'. Imagine that
instead of this (currently in core.js )
// Handle $(""), $(nul
Thanks Paul. This (very usefull experiment ) shows mutation events
"faking", using jQuery.
What I am talking about is jQ 1.5 implementing and relying on mutation
events internal "infrastructure" to solve the problems that
MutationEvents are solving : CRUD operations on the persistent storage
(dom d
CHROME supports this ... but FF does not. same as IE8 .
http://www.w3.org/2003/02/06-dom-support.html
jQuery 1.5 perhaps ?
What I am actually talking is jQuery implementing support for
"Mutation Events" , which is DOM Level 2 ...
http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.
http://www.infoworld.com/d/windows/are-you-secret-ie-abuser-140
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+uns
ments and have the option of
> adding some or all of them back into the DOM at a later time.
>
> DBJDBJ, this is just FYI since you already retracted your suggestion
> to add a .detach() method, but jQuery 1.4a already has a .detach()
> method. It removes elements from the DOM with
Actually maybe new method is not needed. Instead maybe new argument to
"remove()" will
bring an end (and clarity) to the removal saga ?
var orphanage = document.createElement("div");
$("div.foo").remove( orphanage ) ;
If orphanage is provided, removed elements (aka "orphans") will be
added to it.
Maybe having a method "detach" would bring some clarity?
The removed child node still exists in memory, but is no longer part
of the DOM.
var orphan = this.removeChild(this.firstChild)
Above "orphan " is indeed not a part of the document. Why is this a
problem?
Why would I go back to the documen
@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
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 improve
/you too
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this
This made me to immediately change my google password ...
And to do a deep-scan on my (well protected) workstation >:o(
I have no clue what is this? Certainly not my post !
On Dec 8, 4:11 pm, John Resig wrote:
> > What? Never heard of that before...
>
> That's because i
Also please be sure to have jquery attribute present, like so:
This switches on, undocumented jQuery event handling. And also
greatley improves the overal conformance of the jQuery W3C/CSS3
related meta patterns
--
You received this message because you are subscribed to the Google Groups
The joys of the merge concept ;o)
On Dec 5, 2:19 am, John Resig wrote:
> Shamed Yehuda into fixing
> it:http://github.com/jquery/jquery/commit/d684122be0ce3484fb9a4ead11db98...
>
> ;)
>
> Thanks for the catch!
>
> --John
>
> On Fri, Dec 4, 2009 at 9:03 PM, helianthus
> wrote:
> > i guess i jus
Ugh, got bogged down with "something completely different" ... back
on track and proceeding today ...
On Dec 3, 5:29 pm, Dave Methvin wrote:
> > I was wrong. jQuery "building" on (almost) any windows can be done
> > with one wsf file.
> > I am making it right now.
>
> Please do share! :)
--
Yo
"There is always a well-known solution to every human problem--neat,
plausible, and wrong."
-- H. L. Mencken
I was wrong. msbuild is not necessary.
jQuery "building" on (almost) any windows can be done with one wsf
file.
I am making it right now.
--DBJ
--
You received this message becaus
"There is always a well-known solution to every human problem--neat,
plausible, and wrong."
-- H. L. Mencken
I was wrong. jQuery "building" on (almost) any windows can be done
with one wsf file.
I am making it right now.
--DBJ
--
You received this message because you are subscribed to th
To clarify:
I use VisualStudio and its web site (from file system) project kind,
for editing jquery project.
To build it I have jquery.proj which I execute with "open with
msbuild.exe"
For git I have Visual Studio GIT Extensions installed.
On Dec 2, 3:06 pm, DBJDBJ wrote:
> 1.
ted ;o)
I would also use it for MSVC. Same as MSVC team does. Among others:
http://www.infoworld.com/d/windows/microsoft-bares-its-soul-and-creates-opening-google-357?source=rss_infoworld_top_stories_
--DBJ
On Dec 2, 4:21 pm, Scott Sauyet wrote:
> On Wed, Dec 2, 2009 at 10:12 AM, DBJDBJ wrot
Alternatively try :
http://aspnet.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34488#DownloadId=87862
It *seems* really good ...
--DBJ
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-..
@Scott : I have never met any "poor soul" , who pays my fees and who
is in the same time not "stuck in the MS-land". Game over.
On Dec 1, 5:18 pm, Scott Sauyet wrote:
> On Tue, Dec 1, 2009 at 12:14 PM, DBJDBJ wrote:
> > Actually even better would be jquery.proj.
1.
I am using VS2008 + Git extensions - Visual Studio and Shell Explorer
Extensions for Git
version 1.79 made by Henk Westhuis ( henk_westh...@hotmail.com )
The only problem I had was simillar to yuors. It is easily rectified
by *not* using PuTTy.
I switched to OpenSSH. I am pretty sure Tortoise ha
d qunit.
Perfectly doable but a bit fiddly.
--DBJ
On Nov 30, 11:11 pm, DBJDBJ wrote:
> For ANT one needs JDK aka Java Development Kit ...
> For us several milion Microserfs, maybe one VisualStudio solution file
> (aka sln file) would be usefull ?
> Or I am missing something fundament
order to do the basic
> build of jQuery - only to do the minified build.
>
> --John
>
>
>
> On Fri, Nov 27, 2009 at 12:35 PM, DBJDBJ wrote:
> > I am (happily) using one (rudimentary) cmd file for (windows)
> > "building".
> > It is a bit of a overkil
I am (happily) using one (rudimentary) cmd file for (windows)
"building".
It is a bit of a overkill to install the whole JRE, +ant , just to be
able to concatenate jQuery files into one...With cmd file(s) one can
build a "real" make "system" no ant, make, gmake, etc ... necessary.
--DBJ
On Nov 25
http://groups.google.co.uk/group/jquery-en?hl=en
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@google
I noticed this by accident (I had a bug in some speed tests)
If i give them both an array of size 1e5, the latest one is twice as
fast as 1.2.6 ?
var A[1e5], j=1e5; while(j--) A[j] = j ;
$140(A), exits (on average) twice as fast as $126(A) ...
--DBJ
PS:
$126 --- jQuery 1.2.6
$140 -- jQuery 1
@John: Thanks .
After a "isObject or isObjectLiteral" episode, it seems it would be
usefull to spend some time to take a "step back" and decide what goes
where in jQuery and why. And what will be made available to users, of
what is inside. I think by this I mean: What is inside jQuery core,
and wh
You seem very confident.
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more opt
fusion.
> But we don't need any isObject using Object.prototype.toString.call
> anywhere in the code...
> This could be included in any plugin, where required.
>
> On Nov 10, 9:28 pm, DBJDBJ wrote:
>
>
>
> > All is ok then ?
>
> > We/You/me just need , soemthi
All is ok then ?
We/You/me just need , soemthing along these lines :
jQuery.isObject = function( obj )
{
return Object.prototype.toString.call(obj) === "[object
Object]" ) ;
}
jQuery.isObjectLiteral = function( obj )
{
if ( ! jQuert.isObject(obj) ) {
return false;
}
//ow
http://github.com/jquery/jquery/commit/c2bbcd88335cf6f8df4ac9389ecbae90291377fb
contains this version of isObject (changed by me to work as a stand-
alone ) :
isObject = function( obj )
{
if ( Object.prototype.toString.call(obj) !== "[object Object]" ) {
return false;
}
//own pr
Although I am not github-ing jQuery or its tests , this might help :
http://dbj.org/4/test/objlrl.htm
Here I also cater for IE, where dom methods are "object"-s ...
This also works on Opera 5 Mini (Symbian)
PS: I do not see that Robert solution fails on empty function? aka :
function () { }
--
This version of isObject, in IE returns true, when tested with
window.alert ...
--DBJ
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send e
For IE, isObject(), is perhaps not that trivial ... DBJ
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...
sh Sizzle won't return
> > that div in a search $("div"), do you follow me?
>
> > I know you simply brought here yet another inconsistency in the browsers
> > panorama, but to fix this doubtfully useful operation which logically does
> > not make sense I wou
Giammarchi
wrote:
> On Sat, Oct 24, 2009 at 12:22 AM, DBJDBJ wrote:
>
> > Well for the FF team this was not meaningless, since it is possible to
> > set/get css value on the non-attached newly created dom element in FF
> > and then get to it through getComputedStyle()
What a waste of time ...I have posted the code which neither of you
have checked in her browsers ...
@Scot : where is the definition/explantaion of the CSS2 computed
values about the created but un-attached dom element ?
If this would be defined, FF and Chrome would most likely do it in the
same
What does W3C DOM spec says?
--DBJ
On Oct 23, 12:05 pm, Andrea Giammarchi
wrote:
> I wonder how meaningless would be a get*Computed*Style for a node not in DOM
> neither rendered yet ... it's not clear in any case which browser does what.
>
> On Fri, Oct 23, 2009 at 11:58
Uhm, uhm ... AG is right ... Logically asynchronous events start
immediately upon firing, but they *finish* at an future undetermined
point on the time vector. (or "never")
This is why this paradigm is also called "fire and forget" ... vs
"wait for return" Synchronous paradigm.
Therefore: ordered
CHROME 4.0.223.9
If one does this :
var dumsy = $("").css
("color", "red");
C = window.getComputedStyle(dumsy[0], null).getPropertyValue
("color");
C will be empty string , aka "". Also observing
window.getComputedStyle(dumsy[0], null).cssText will reveal that
"color:" has no
gt; On Oct 23, 4:40 pm, DBJDBJ wrote:
>
>
>
> > Agreed: QUNIT could be documented better.
>
> > BTW: Just to be sure "we are by the book" ;o)
> > I would be so bold to recommend ,instead of this :
>
> > setTimeout(functi
Agreead.
Also: Not having QUnit introduce global functions would be *very*
usefull, too.
I dare to think we all understand how much more advisable is to have :
qunit.test()// or Q.test() or whatever else ...
instead of :
test()
--DBJ
--~--~-~--~~~---~--~~
Y
Agreed: QUNIT could be documented better.
BTW: Just to be sure "we are by the book" ;o)
I would be so bold to recommend ,instead of this :
setTimeout(function() {
$(window).unbind('hashchange');
start();
},
IHTMLWindow6 Interface and its implemenation is inside MSHTML.DLL.
Which "we" call Trident html rendering engine.
Which is used in IE8. Where we have this top vs window "feature" in
"action". And a "few more" other "features" ... unfortunately.
MSFT is dropping Trident in favour of new HTML rend
Strictly speaking top and window are two different things, aka two
instances of the two different classes in the C++ implementation of
the IE8 DOM.
(this is COM, therefore their CLASSID's are different)
I suppose the thinking of Gaurav Seth (MSFT) was to "reflect" this in
the JScript.
So *strictly
I was always in personal disagreement with the whole SVN
"religion" ...
The move to : http://github.com/jquery/jquery, will be beneficial in
more ways than one ...
I hope as soon as 1.4 is out ?
--DBJ
--~--~-~--~~~---~--~~
You received this message because you are
Thanks for your leg work Scott.
--DBJ
--~--~-~--~~~---~--~~
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 from this group, send
Ah, "elementary my dear Watson" ...
http://jquery.com/src/nightlies/jquery-nightly.js is version 1.4pre
While (until today 2009 OCT 07 )
http://jquery.com/src/nightlies/jquery-nightly.pack.js is/was version
1.3.3pre
That explains it ... While we are guessing and cogitating, The Team is
working
Using the PACKED nightly , I have also found that probably only TR's
in IE8 have this problem with toggle()
If using console in IE8 I add (for example) div to the dbj.org/h.htm I
can toggle() it succesfully.
Somehow in IE8 setting the TR style to: "display: table-row", does not
happen ?
And this h
oh yes and also in IE8 $(".child-row123:first").is(":visible"),
returns always "true" when it should not ... with the latest build
and yes, people have noticed something is wrong around this issue :
http://remysharp.com/2008/10/17/jquery-really-visible/#comment-174813
--DBJ
--~--~-~--~
@Scott ... It is really rather simple to prove that toggle() is not
working, using dbj.org/h.htm and IE8 or C or FF javascript
consoles We do not have to (re)create streams of simillar but
different pages.
So, open dbj.org/h.htm in IE8 and then in it's (very good) javascript
console execute
I do disagree. Matts original page is not working with the latest
jQuery.
Please see http://dbj.org/o.htm
I simply saved localy (using IE8) Matts original and then uploaded it
to dbj.org
I am sure you can see that it uses jQ nightly build, as the only
change.
(and of course "[@" from a old style s
@Scott: no reason to "defend" since no one is attacking ;o)
I have done two variants of code inside dbj.org/h.htm
1.
old is invoked with : http://dbj.org/h.htm?old
2.
workaround is invoked with : http://dbj.org/h.htm
In the page there is some utility code, nothing complicated. The two
key functi
@Scott, thanks for the effort. But the starting point still remains:
all of this was working OK with jQuery 1.2,
as evident on Matt Kruse original page :
http://www.javascripttoolbox.com/jquery/
While dbj.org/h.htm , shows that the jQuery nightly trips over this :
$(this).siblings('.child-
@Scott, please look into: http://jsbin.com/ipabi/edit
This code works (nicely) in FF and C, and (not so nicely) IE
(btw: there is no global 'toggle' in there)
The "suffering" the previous simple code is enduring is coming from
toggle() not working in IE ...
This is easy to see at http://dbj.or
Plot tihickens ;o)
If I do it this way , then it works fine in FF and C., display is
"dispplay-tablerow", on the TR's toggled to visible.
$(function() {
$('tr.parent')
.css("cursor", "pointer")
.attr("title", "Click to expand/collapse")
.click(
@John: Is there any idea about the start date on the jQuery Devl
Forum ?
(Vanilla works very good indeed)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email
toggle() and TR do not go very well together ...
http://jsbin.com/ipabi/edit
This is the version using fadeIn/fadeOut
Which behaves and is controllable (speed wise). And is not destructive
for TR's and TD's...
Although effect is different ...
Now is this jQuery bug or feature ?
--DBJ
--~--~--
There is no "version" but a "previous post". Anyway what I am taking
about is here :
http://dbj.org/h.htm
It shows outerHTML of each TR toggled ...
Do I log/make a ticket or is this already a known issue ?
Or am I wrong ;o)
--DBJ
PS: Everyone was very helpfull on this one. Thanks.
--~--~-
@Scott ... good work. The problem was in FF and C also, when doing
toggle(value).
When doing togle(/*no args*/) my IE8 does not toggle at all, while
both FF and C work same as Matt's original.
Please use/observe "my" version which alert's with the outerHTML of
each TR toggled. Each TR toggled has
I dont want to sound pompous but this/that page is including and using
the nighlty build ...
Also it is the TR style="" attribute problem. After being "treated"
with toggle(),
On my IE8 it becomes :
style="FILTER: ; ZOMM:1; DISPLAY:hidden"
--DBJ
--~--~-~--~~~---~--
I also did noticed that TR's toggled get not so valid markup.
Code I used is this:
jQuery.fn.outer = function() {
return $($('').html(this.clone())).html();
}
$(function() {
$('tr.parent')
.css("cursor", "pointer")
.attr("title", "Click to expand/co
$(function() {
$('tr.parent')
.css("cursor","pointer")
.attr("title","Click to expand/collapse")
.click(function(){
$(this).siblings('.child-'+this.id).toggle();
});
$('tr[class^=child-]').hide(
@Matt, thanks for the quick reply. I already did that. Please look
into the source of the page.
I can't understand why is that simple jQuery code so "sensitive".
Especially toggle(), misbehaves in IE.
I have not tried with the jQuery version you have used, but I can see
no relevant difference,
be
Matt Kruse has an nice and simple jQuery "ideas page". I could not
make it work for me.
http://dbj.org/h.htm
The difference is I am using the latest jQuery.And I have also removed
some parts from Matt's page.
The first example. "Details" Table . My page is (obviously) not
working. Why?
Link to t
I "guess" this might help :
http://stackoverflow.com/questions/1462649/jquery-memory-leak-with-dom-removal/1491317#1491317
--DBJ
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to
I think an Noble attempt to *guess*, and very true observation.
But why guessing? Let us wait for Ricardo's page ...
--DBJ
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this
you also please file a ticket (http://dev.jquery.com/newticket/
> ) for this once you are able to create a test-case. This way it
> doesn't get lost on the mailing list.
>
> --
> Brandon Aaron
>
>
>
> On Mon, Sep 28, 2009 at 3:54 AM, DBJDBJ wrote:
>
> >
Hi Ricardo,
Please present the url where the page with your problem/solution is,
and then please repost this in the "jQuery (English )" Google
group ...
Regards: --DBJ
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
General Sibling Combinator module: find(element ~ element) (2, 4, 6)
1.$('p').find('code ~ strong').length: 3
2.$('p').find('code ~ code').length, expected: 3 result: 0
3.$('p').find('strong ~ strong').length, expected: 2 result: 0
4.document.querySelectorAll("p code~ strong").length: 3
5.docume
... after Karl and DZ exchanged understanding , let us try and help
Karl ...
My thinking is this : is this a Sizzle issue ? Or jQuery core "does
something" ?
By answering this question we will narrow down this exciting "bug"
chase.
If we observe jQuery.find() (which is Sizzle() ) we can easily se
1 - 100 of 264 matches
Mail list logo
