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
On Wed, Oct 7, 2009 at 11:50 AM, DBJDBJ wrote:
>
> 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
Good catch. I gu
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
On Wed, Oct 7, 2009 at 4:12 AM, DBJDBJ wrote:
> @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
Yeah, that's pretty useless unless you're trying to figure out what
the problem is and how to fix it!
In
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
On Tue, Oct 6, 2009 at 10:34 PM, Scott Sauyet wrote:
> 2. You are using a min-ified version of jquery. I'm not.
>
> Because of how we've been going in circles, I suspect #2. Have you tried
> with a non-minified version? If that's the issue, then it should be easy to
> get a simple regressio
DBJDBJ wrote:
> I do disagree. Matts original page is not working with the latest
> jQuery.
> Please see http://dbj.org/o.htm
For comparison, see
http://scott.sauyet.com/Javascript/Demo/2009-10-06a/
> I simply saved localy (using IE8) Matts original and then uploaded it
> to dbj.org
> I am
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
> "...Can you build a page that works properly with 1.2 and not with the
> latest? ... "
> On dbj.org/h.htm , just click on the link to Matt Kruse original and
> you will have that page ... It uses "jQuery 1.2.1"
Right, and the link I sent above (http://jsbin.com/atojo) is a version
of the same p
@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
On Tue, Oct 6, 2009 at 8:38 AM, DBJDBJ wrote:
>
> @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/
And I've been trying to point out that this
@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-
On Mon, Oct 5, 2009 at 2:48 PM, I wrote:
> If you're calling with a number of functions, it looks as though [toggle]
> will choose a successive function to run after each call, but in that
> case, it does not automatically hide or show the element; is that
> right?
No, it's not right. A single f
On Mon, Oct 5, 2009 at 11:42 AM, DBJDBJ wrote:
> @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)
Perhaps not global, but it is shared among everything matching
"tr.parent". It
@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
On Fri, Oct 2, 2009 at 8:11 PM, DBJDBJ wrote:
>
> toggle() and TR do not go very well together ...
>
> http://jsbin.com/ipabi/edit
>
> This is the version using fadeIn/fadeOut
This suffers from the problem that you are using one global 'toggle'
variable for all rows. There are other ways to ach
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(
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
On Oct 2, 2009, at 1:40 PM, DBJDBJ wrote:
>
> 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:hidde
> Btw, I find this change very annoying. It has prevented a few projects
> I've touched from upgrading their jQuery version
Matt,
I, for one, don't mind the removal of xpath-y syntax from a CSS
selector engine. Regardless..
Here's a rough monkeypatch that will allow your @ attribute syntax to
wor
I see the problem in FF, so I don't think it has anything to do with
IE specifically.
Using Matt's original markup, modifying the code only by removing the
"@", and making minor tweaks to the CSS to make borders visible in
jsBin, I got it working with the nightly here:
http://jsbin.com/ixofe
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 think the problem there is with the way IE reports height or TR
elements, even if they have display none. Something like that. For
performance reasons, jQuery 1.3.2 changed the way it detects
visibility. This broke a few things, including jQuery misreporting TR
elements' "visible" status
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
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 wrote:
>
> My example code uses this selector syntax: t...@class^=child-]
>
> Support for [...@attribute...] has been changed to just [attribute...]
> with jQuery 1.3.
My example code uses this selector syntax: t...@class^=child-]
Support for [...@attribute...] has been changed to just [attribute...]
with jQuery 1.3. Remove the @ and it should work for you.
Btw, I find this change very annoying. It has prevented a few projects
I've touched from upgrading their
32 matches
Mail list logo
