I'm working on a new drupal

silverwing — Thu, 29 May 2008 06:15:35 +0000

I'm working on a new drupal theme for my site and I use a logo instead of the h1 sitename, but I keep the h1 in the code and set it to display:none just in case someone wants to look at my site without the stylesheet.

~silverwing

... On a more serious(?)

webwiz — Sat, 17 May 2008 18:10:24 +0000

... On a more serious(?) note, here's a practical example:

CSS
p.ie-warning {
display: none;
_display: block;
}

HTML
<p class="ie-warning">Your web browser sucks!</p>

webwiz wrote: You could use

silverwing — Sat, 17 May 2008 18:09:11 +0000

webwiz wrote:

You could use it to fix a lot of IE 6 bugs:

* html body { display: none; }

That's what I use it for.... except, usually not in the body....

~silverwing

You could use it to fix a

webwiz — Sat, 17 May 2008 17:43:05 +0000

You could use it to fix a lot of IE 6 bugs:

* html body { display: none; }

Here is something don't

Abhishek Reddy — Fri, 16 May 2008 22:08:42 +0000

Here is something don't display it but if X=Y display what was hidden.
Why not just if X=Y display this->

Because the HTML document retains its full content regardless of applying scripting and styling. That some parts are not displayed (like a dropdown menu) is an extra feature. I would think separating content from scripting is a better approach than mixing them.

it isn't in the HTML unless you "unhide" it

Actually, it is in the HTML whether the style is applied or not. Styling does not affect the semantic structure of the document. Neither does scripting in this case, supposing it doesn't modify the document tree beyond swapping the CSS properties.

He's a strange little

greg — Fri, 16 May 2008 20:44:41 +0000

He's a strange little character this display none!
So it's like not displaying something to then use JS or whatever to display it.
Seems like the wrong way to go about things to me.

Here is something don't display it but if X=Y display what was hidden.
Why not just if X=Y display this->

As for SE's, I presumed it wont affect keywords unless you display it, as it isn't in the HTML unless you "unhide" it, and then it's just the same as having something there all along.

I think the SE's apply the

Megan — Fri, 16 May 2008 18:17:14 +0000

I think the SE's apply the same rules they would to other text. If it's normal image replacement for headers, for example, then that's not a problem. If it looks like keyword spam then they would discount it.

Mainly for conditional

Abhishek Reddy — Fri, 16 May 2008 17:21:00 +0000

Mainly for conditional display.

You might want to show some element only when some event occurs (say, a drop-down element in a navigation menu).

Or you might want to include text for screen readers or CSS-less browsers, in a manner analogous to the noscript tag. Screen reader behaviour is flaky, though.

Incidentally, I wonder if SEs still give any weight to text that isn't displayed. Probably not, or much less than normal text. Might be worth checking.

It's also useful in development since you can turn on or off displaying some elements easily, rather than deleting or commenting out large parts of HTML code.

Often so you can dynamically

Megan — Fri, 16 May 2008 17:20:43 +0000

Often so you can dynamically re-show it using Javascript. (The best way to do this is to have it visible by default then hide onload with javascript)

Sometimes so you can hide something in code outside of your control e.g. in CMS templates or in user stylesheets.

Those are two that I use most often...