I realize this thread is solved, but I would just like to include that text for the web is rather different from physical documents. We read about 25% slower on our computers, and designers often rewrite text to a more condensed, scannable, web-friendly form. It is by no means uncommon and should be encouraged.
If I'm not mistaken, the book is simply using the blockquote element as an example of how to have two selectors in a CSS rule. Continue reading and you should find that they don't actually include the blockquote element in the .greentea rule. Yes, that would be redundant but keep in mind that both are block level elements. So one doesn't actually have to be inside of the other.
Visually yes, but no. Margin is part of the box model, while the top and left properties interact with elements a little differently, and typically require the element to be removed from the normal flow of the page.
relative-placed blocks? Do you mean relatively positioned block level elements?
The problem is only occurring in IE7. Modern browsers have no problem with it, so it's doubtful that there is anything actually wrong with the code. Taking apart the site would be pointless, not to mention a huge waste of time for a problem that's exclusive to a browser that's known for its many flaws.
Try removing the width and float from your #horizontal_line rule. This should allow the element to cover the entire width of the page. Is it still being moved?
You're positioning everything absolutely. This removes those elements from the normal flow of the page, and therefor the z-index will not effect those elements the same way.
Alright, it looks like JavaScript is used to position the slider. Adding the drop-down menu is throwing off the height which is why it isn't working. There's probably just a portion of the JavaScript that needs to be tweaked to make this work, but JavaScript is not my forte. You could try asking in the JavaScript forum.
To make the slider extend all the way down the page, even though it's not sliding. Find this CSS rule in your code:
Ah, you said width with an inch value. Anyways that's rather annoying. I think that the purpose of changing a resolution originated for visibility rather than quality.
That's a good question. Inch is a fixed value, so changing the screen resolution will change the value of an inch. Try using a dynamic unit, such as percentage or em.
I've been told that this may be a good idea so that the scrollbar is always displayed no matter how long the content is. However, my question still remains that this page should actually have nothing to scroll (though it still does).
This is an optional display technique which is basically useless. If the content extends past 100% of the browser window a scrollbar will appear on its own. If the inconsistency across pages bothers you, then use it.
This is because I want some gray (the html background-color) to show above the blue (the body background-color). Is this not how I would achieve this?
It pushes the body element and everything in your page, 10% from the top. You should use a division and probably margin instead.
This is because I want some blue (the body background-color) to show above the white (the whitebox background-color). Is this not how I would achieve this?
No, that's fine but in Firefox and Chrome it does nothing (on a Mac)
Should I make it a div instead? Surely that is not what is causing the page to be about 10% taller than the screen, right?
Right, but you do have another element being pushed exactly 10% from the top.
Things to keep in mind~
Your footer is absolutely positioned. This removes it from the normal flow of the page. Also, there are better ways of positioning it at the bottom.
Every browser has its own default margin and padding. …
Please post the complete markup or a link to your test page. Simply telling us you want it at the top could mean several things, and wastes everyone's time.
This just made things worst. Position:absolute and margin are the only ways of positioning elements that are shown on tutorials. If there are other ways I don't know how.
I'll read some more before starting my own page. Thanks for your help.
Both .className td, th {border: 1px solid #CCC;} and .className td, .className th {border: 1px solid #CCC;} are valid. They simply tell the browser different things.
The first states that the styles should be applied to any td element within an element with a class of className , and any th element within the document. The second states that the styles should be applied to any td element within an element with a class of className , and any th element within an element with a class of className .
Most forums use vBulletin, hence the consistant theme.
Yes, a list could work - if done properly. While this could make reading easier for screen-readers, it would have the adverse effect on web developers. Hunting through a giant list would be a lot more difficult; assuming that you coded the forum yourself.
If you only want the opacity to affect the background, place the text in a separate element and position it over the background. Absolute positioning, floats, z-index, etc.
By textbox do you mean textarea? Are there scrollbars? Are you wanting it to start at the bottom or scroll down on its own? Please be more specific when asking questions.
