In my new job I recently discovered what seems to be a bug in Firefox 3.5: when there is a link (or anything else to which an outline could apply, i.e., any element with an :active state or a tabindex) that is floated (i.e. float: left or float: right) inside a container with overflow set to auto, the outline on that link will take up space, contrary to the W3C spec. This means that such a link, if it fills the container in either the X or Y dimension, will cause scrollbars to appear when it is active (tabbed to or pressed).
But there’s a fix: If you apply CSS outline-offset with a negative value, e.g. outline-offset: -2px;, I suspect it still takes up space (in a sense), BUT that space is inside the element’s current boundaries, so no harm done (unless you really needed that outline to conform precisely to the boundaries.
No long explanation about why I haven’t posted in a while. If you’re still reading, you want content, not apologies. But a short explanation: I took a new job (full-time, in an office) and moved to Seattle. That means that twelve8 creative is now based in Seattle, not Chicago!…
A while ago, I was directed to this prototype for the mozilla.org redesign, notable particularly for it’s use of an intelligent, fluid grid. I bookmarked it within a folder I keep for quick design inspiration, since there are several aspects of the design that I think are pretty great. Looking at it again the other day, I discovered a clever bit of CSS coding.…
Some of you may know that I’ve been looking to move into a full-time role as a web interaction designer for the right company. [Potential clients: Don’t let this scare you! I’m adamant about keeping alive the possibility of freelance work alongside any full-time position I may accept, and I’ll always be honest about my ability to perform requested work in a timely manner.]
Sorry it’s such poor image quality. Best I could come up with.
via The Dieline