> Well, I have very little interest in checking through the
JS that
> produces all the resulting markup, but I can see the generated code, and
> that lets me generate what will seem like a smart-aleck answer. Ready?
That's fine as I have the
JS in order :-) My problem is CSS and
browser behavior.
> Your CSS error is putting it inline. For every day in the calendar, I
> see stuff like style="left: 83.3333%; top: 87.0968%; width: 16.6667%;".
> This stems from what I think is a much larger (and more general) error:
> coding the page as a huge clump of absolutely positioned divs and spans.
> A calendar is a classic example of tabular data. I recommend you use
> <table>.
I did make the calendar with tables before but I had all kinds of
problems + I hate tables! I think it will be easier to manipulate (the
DOM) with divs rather than trs and tds. Especially because the divs
are absolute positioned, I can remove a div with out worrying about
the layout. Also my solution (printing images) requires that the
elements are taken out of the page flow, so I can use z-index. As far
as I know that requires absolute positioning.