Can someone explain this to me a bit more? I thought to position elements and images, I had to whack an ID, Div's, or some sort of defined XHTML "element root" around the thing and then define how that behaves. (Element root being the opening and closing HTML tags or "Body" tags.)
Is this guy saying that an unordered list can act as an "element root" for everything inside the list? He's CSSing the list into a table with graphics, and has just said something about position relative giving a
"framework" to things within it. That confused me, because until then my definition for "position relative" was something like:
...in my own weird understanding...
Is this guy saying that an unordered list can act as an "element root" for everything inside the list? He's CSSing the list into a table with graphics, and has just said something about position relative giving a
"framework" to things within it. That confused me, because until then my definition for "position relative" was something like:
...in my own weird understanding...
CSS positioning
relative: relative to where the element or image would have been if we had left it alone, relative to it's original position, relative to itself, offset to where it "is" and the page still thinks that it "is" still in it's original position and leaves a space where it "was".
It can also give a framework to things within it, such as calling an unordered list or "ul" position: relative; will tell things in the list how to behave.