I resized the window to 800x600. Hmm, no problem here. In fact, the fixed width page seems to fit perfectly with no more than maybe a 5px margin on either side. How about 640x480? Aha, here the problem becomes apparent. The problem is that the scroll bar does not allow the user to scroll to the area that runs off the left side of the page.
Archive for the 'css' Category
While I understand why each occurrence of the the ID attribute must be unique in HTML, sometimes I find it annoying. Sure, I can always include a class, or two, but that seems redundant at times. Besides, isn't that not quite a complete separation of presentation from content?
Ouch! I just checked this site in IE. I thought I had done so after the initial layout and it all looked ok. Either I only thought about it but never actually did so, or I changed something since then. Either way, the layout breaks in IE. And to think that was the part of this design I was least likely to change as the design evolved. Oh well. It is probably just as well. As it currently stands, the content comes after all the links and other such clutter on the sidebar in the markup. That really should be switched around so that the content comes first. This is, after all, supposed to be an accessible site. I guess I won't be finalizing the Wordpress template tonight as planned.
On another note: the more observant reader may have noticed that the links in 'of interest' on the side bar are updated more frequently that my weblog entries. You can follow these every day and follow some of my daily browsing if you so desire. I think I found a workable solution for these in Wordpress, so once that is up and running (I pretty much decided I am going with it) you should find even more. Now to find a way to date the entries (I'm listing them as links under separate category in Wordpress, rather than a separate weblog) and decide how to indicate where I came across the link. After all (I seem to like that phrase today), credit belongs where credit is due.
The Web Standards Project announced some CSS Spec Updates yesterday. Among them was the CSS3 Hyperlink Presentation Module. If you recall, the 'target' attribute was depreciated with xhtml (causing xhtml strict to fail validation), thereby forcing one to use JavaScript to open a link anywhere but the current window/tab of the browser. This "first working draft" proposes the addition of the 'target' property to CSS3 and is even fully aware of tabbed browsing as found in modern browsers. For instance, a designer/developer (or whatever you call them/us) could cause a link to open in a new tab directly in front of the current tab in the users' browser with the following CSS:
Apparently my inline dropdown menu is not as original of an idea as I once thought. I came a cross this today, which linked to this. even so, mine is the only one where the submenu appears on rollover. Ha! So there!
Or is that maybe a usability issue thing? I suppose by having the sub-menu not visible, I could be making it inaccessible to some who don't have the ability to hover. Hmmm.
To be honest, one of the reasons I never developed a better looking version was because I couldn't get it to look right unless I did away with the fancy rollover stuff. I guess it just goes to show that there is no such thing as an original idea. Man, this manual editing just to add a post is getting to be a real pain.
