Div content not showing…

Another rant…

This is another huge problem with Divs/Css:

Parent Divs that dont know they are Parent divs, thus not dropping down to contain the child/nested div content.

WTH is up with that crap?

I’ve come across this a dozen or more times.

 

asdfasdf

asdfadsfa

 

the default stupid way of doing css

I’ve seen a lot of css like this:

table {

}

label {

}

td {

}

This crap css coding style sucks. Why? Because the designer dude who has dealt little with the actual content of the site, writes whole template encompassing css for ONLY the template.

Then comes along the grunt who puts that content into the site, and true to css’s nature…it cascades causing the content integrator to have little to no control over td’s labels, tables, etc.

The worst offenders of this are those POS templatemonster templates. They suck beyond words, not to mention how slow they are loading, how bloated they are code wise, and how unchangable they are due to machine generated crappy code.

If you’re going to css up a html document give it a class too.

label.class

Don’t make it all encompassing the whole document.

 

The Problem with Stylesheets IS the cascading part

My situation. I edit many different sites on a weekly basis. Some of these are templates, coded by hand, and coded beautifully. Others are not. Recently I needed to update a site with new content. This required changing the div/css ul/li menus that some one originally used on the site.

Here’s what you do if you come across an ul/li menu. DELETE > Start Over

Old school is better and easier to understand and most importantly…editable.

This site I’m ranting about right now had 2000+ lines of css in it to make it work….yes…2000 lines! WTF???

Anyway…my original point about css being stupid is the fact that it cascades.What if I want to turn off the cascading for a line or two of html???

There is no way of doing it. There is no way to prevent cascading from happening. The creators of css are effing stupid for not considering that yes, in some circumstances turning off the cascading effect would be an effective tool.

 

Ban IE5,5.5,6,7 and 8

Since the Internet Explorer browser was coded by morons, implemented by morons, bundled with their operating system by morons, and implements code like a good moron does, I vote we ban IE for good.

Worst !@#$ing browser ever!

 

Anonymous Comment From a Blog…

CSS’s strongest argument is only its swarm of fanboys(& girls).

At least with tables, when I resized my browser window, it didn’t break a site’s design or make it completely unreadable. It kept the content locked in place.

It says a lot about CSS when Photoshop’s table slice-generater, though it creates nightmarish html - it can autogenerate readable code and looks the same on every browser. If CSS can’t even claim the same functionality of the jokish “Adobe Photoshop’s HTML” could accomplish, it’s simply pathetic.

BTW,  current versions of photoshop can generate CSS code. While it is possible, it’s not exactly usuable since every slice is absolutely positioned.

 

only microsoft could screw it up this bad…

I’m installing .net 2.0 to use with a program. it’s 22 meg and it just took about 4 minutes to install. ms is the worst company ever. only ms could make a program take that long to install….while they screw up my system because the program infiltrates every particle of the operating system gauranteeing there being NO possibility of it ever being removed without a hard reformat.

 

css = no containment

tables = containment.

If you nest DIV elements together as you would table cells a funny thing happens that SHOULD NOT when child elements get larger than their parent elements. The larger element stays the same size and the child element completely oversteps any “bounds” you thought you had on it.

This doesn’t happen with tables. Yet another reason why divs and css are dumb.

 

Just a Thought.

Tech Support

 

So true.

Web Standards