Seems it’s Christmas in July around here with the new design and graphics. I wasn’t intentionally going for a wintery look, but once it got going it was hard to stop. I’ll probably put this one (design) away for this winter. Meanwhile, enjoy the frosty air!
I was recently given a Canon Powershot A60 as a thank you gift! WOW! Too nice!
Here is a picture I just took with it (resized to fit in this space)
I’ve recently been thinking about the problem of rounded box corners in CSS. There are several solutions to this floating around. From the use of multiple layers of nested divs to provide the ‘hooks’ from which to hang the corner elements to another solution of nested divs and list bullets to graphically create a rounded line. Other approaches dispense with the problem of boxe resizing and instead use a graphic that has a fixed width and contains the corners for both right and left sides.
Of all the approaches, I think the list bullet idea is the most creative. However, there’s also alot of screaming going on about extraneous markup. “Why have multiple nested divs when we are trying to seperate presentation from content?!” they shout.
While I think this is a valid point, the current state of the CSS spec implemented in current browsers just isn’t up to fufilling the dream of true content/presentation separation. There are many points on which this may be argued, but I think the rounder box corner problem illustrates this nicely. For this problem specifically, the ability to specify a border corner type would be perfect. There are already some proprietary CSS rules available for this (which, if you are using a Mozilla based browser, you will notice on my side menus), but that doesn’t help towards the goal of standards…which we are after.
So let’s start by thinking about all the goals involved in creating rounded box corners.
While three main goals doesn’t seem like much, it truly is a tall order using CSS1 and the smattering of CSS2 available to most browsers. Is there a solution that fufills these goals? Who knows. I haven’t seen it yet and I haven’t thought of it myself. Rest assured, I will keep thinking about though…
George W. Bush Sings! After your done laughing…check out the G.W. speach recording archive
Once again it is Friday. yay!
I was made aware of a strange CSS bug today. Although I’ve encountered numerous CSS browser bugs, I’d never heard of this one. It turns out the select boxes basically have z-index:infinity so they overlay any other element in the page.
I guess my real problem with calling this a bug is…why would you want something to cover a select box? Aren’t they there to drop down and let the user select something? What would be the point of having them overlaid by a div or other element?
Can anyone explain why you’d ever need to cover a select list menu?
Update
Ok, ok…I guess there is the case of DHTML type menus that pop open in the vicinity of a select menu. I guess one solution might be to use javascript and the DOM to hide the select box when the menu opened. That seems like a fairly flaky way to go, but…
Of course, this isn’t a problem in Firefox or Mozilla…
Changing the wine world.
Changing the wine world.
