CSS troubles
- Started
- Last post
- 34 Responses
- MrWhite0
add a ";" after color: #FF9900
- bulletfactory0
there are some conflicting tags in there..... the body tag has 2 different background color properties - one set w/ background-color: #ffffff and the second with background:#000000 url...
- doesnotexist0
fixed those, still not working. weird.
- MrWhite0
what are you seeing? I am seeing an HTML page that is formatted using the stylesheet. it appears to be correct.
post a screenshot of what you are seeing
- nocomply0
Yeah you got a number of issues going on in there, and the page renders very differently in FireFox and IE.
One thing I'd say is to stay away from using percentages to define width and height whenever possible. That's really just my personal preference, but it makes things a lot easier for me to use pixels. I'm a fan of fixed width layout because they always "work" for me.
- doesnotexist0
thanks? kind of why im asking for help, as i dont understand why it's not working.
- doesnotexist0
hmmm...just tested it on my pc...the borders and background for the element is coming through....why not safari?
- doesnotexist0
ahhhhhh wtf?!?!
i dont see those in dreamweaver...but i replaced what i see on your screen with spaces, IT WORKS!
thanks, dude
- nocomply0
Yes I too see the "?" when I view your CSS in firefox. Perhaps thats the issue at hand. Maybe remove any whitespace characters you think you may have??
- bulletfactory0
glad i could help!
- MrWhite0
yeah, i saw those in BBEdit too....I removed them and it works on my safari
- doesnotexist0
now...dont elements only last for one use?
- nocomply0
Not sure if this is what you're getting at...
but an ID (#) can only be used properly once per page.classes (.) can be used multiple times.
to actually style an element (for example or ) leave off the . or the # and type:
p { style as normal... }
Now every single p tag will be styled.
- MikeDubs0
You got owned by Dreamweaver.
- nocomply0
pwn3d!
- version30
oh btw
dreamweaver sucks
learn to code by hand, you'll avoid these problems and try sticking to css1 for now
- doesnotexist0
i used to do it by hand, i should probably go back to doing that.
yeah i have the # on there twice and it's coming through both times.