ansaurus

Question

Answer 1

A:

$(document).ready(function(){
   $('#stuff').css('display', 'block');
});

jAndy 2010-06-01 14:11:37

Which is *basically* exactly what `.show()` is doing.

Felix Kling 2010-06-01 14:13:47

This shouldn't be any difference from what he's already doing, it's an instantly animated css change that does exactly this already.

Nick Craver 2010-06-01 14:19:30

well, its faster anyway @Felix: its way beyond from doing the exactly same thing

jAndy 2010-06-01 14:20:24

@jAndy - Provide one example where `.show()` wouldn't work, but `.css('display','block')` would? I'm having trouble seeing a situation where this would be a fix...

Nick Craver 2010-06-01 14:30:41

@jAndy: What is the a big difference? The only difference is that `.show()` will use the previous `display` value if it was not `none`.

Felix Kling 2010-06-01 14:30:44

Tried this before i posted question... No joy...

musoNic80 2010-06-01 14:35:10

@Felix Kling: .show() must call like a ton of functions to accomplish this actually pretty simple behavior due how jQuery internally handles fx requests

jAndy 2010-06-01 14:35:39

@jAndy - It doesn't if you're not giving it a speed, you can see this for yourself... http://github.com/jquery/jquery/blob/master/src/effects.js

Nick Craver 2010-06-01 14:36:54

I could swear I recently read an article about this topic (performance of show() and how slow it is even without a speed). Whatsoever

jAndy 2010-06-01 14:53:47

Answer 2

+4 A:

Make sure your code run when the DOM is ready, like this:

$(function() {
  $("#stuff").show();
});

$(function() {}) is short for $(document).ready(function() { });, this runs the code when the DOM is ready, e.g. your div is actually there to find. Otherwise your selector (unless this is at the end of your <body>) probably isn't finding anything. You can see this by putting alert($("#stuff").length); where your code is now, if it alerts 0, this is most likely the problem.

Nick Craver 2010-06-01 14:12:51

This is more than likly the issues, your running your function before the actual html content is parsed into the DOM, so it does not exists. by running the function when the DOM is fully loaded more than likely your div will be in scope.

RobertPitt 2010-06-01 14:33:47

See above comment... Also, although I haven't tried alert, it does show up as expected as part of the DOM with original CSS rules when I inspect the HTML in firebug.

musoNic80 2010-06-01 14:34:00

@musoNic80 - What does the alert show? Ignoring the debugging tips we're giving and only providing one line of code with no markup isn't the best way to find the problem...

Nick Craver 2010-06-01 14:38:38

Sorry Nick, I've had to leave my computer for a bit which is why I haven't tried the alert tip. I'm not ignoring suggestions. I'll try it when I can. I have a long jquery file which is working as expected, apart from this one line. This is the only line that tries to target thar div and so I thought that everything would be irrelevant.

musoNic80 2010-06-01 14:54:11

Ok, so the alert test resulted in "1". I also tried reversing things. I removed the "display:none" attribute in the css and swapped show() for hide(). Worked as expected. Any other ideas?

musoNic80 2010-06-01 15:18:26

What version of jQuery are you using?

Matt 2010-06-01 16:52:52

@musoNic80 - I don't have any other solutions off the top of my head...if you had a URL we could see it would be pretty quick to figure out though, but it's just guessing without seeing the rest of it.

Nick Craver 2010-06-01 18:54:12

@Nick: Thanks for your help. Unfortunately I'm developing on localhost so don't have a URL to give you.... Are there any other debugging tips you could give me so I can keep trying to figure it out?!?! Or is there someother way to show you the code or recreate the problem?

musoNic80 2010-06-01 19:11:25

ansaurus

tags:

views:

answers:

Weird jquery behaviour

related questions