There are 19 entries matching ‛Sandbox’:
The Web developers among you may be interested in what appears to be a Safari bug. Essentially clear:none does not over-ride clear:left. I’ve posted more details and an example in my sandbox.
I’ve been admiring the ‘image loading…’ and subsequent fade-in of (spectacular) photos on Couloir. It seems they use a rather nifty trick to achieve this.
I’ve been playing around with ways of displaying images in variable width columns, particularly with images that are wider than their container. Please cast your eye over my experiments.
DOM scripting is much more than getElementById. Elements can be isolated and manipulated without having an id at all. To demonstrate this I’ve put together a simple script which redefines the styles of a class.
Using the DOM to automatically underline the letter of a link text which matches its accesskey.
Those of you who have just updated OS X to 10.3.9 may have noticed that Safari is now a full point release older at 1.3. And this means that the clear:none bug I reported a year ago is finally fixed. In fairness Dave Hyatt fixed this bug ages ago but he’s had to wait…
Browser Stickies is a little experiment I knocked together in the lull between SxSW Interactive and SxSW Music.
There’s more to the lives of many typefaces than just Bold and Regular, but almost no browsers follow the proper CSS 1 way of specifying Light, Semibold, Black and other weights. There is a workaround, but it’s nasty.
Typographers divide words using hyphens to increase readability. All books and newspapers of any quality use this technique to ‘justify’ their text, yet it is not a tool available to Web designers in any useful form.
Investigation into, and a fix for a peculiar bug in Mac-based Webkit browsers, including Safari and Chrome.
As a way of enabling address input, the UK postcode look-up is fraught with danger and is rarely implemented well. As is often the case in UX design, everything is fine until an exception is reached.
Semantically speaking, should we be using tables to lay out forms, or should we be using some other mark-up combined with CSS? There arguments for both, but I reckon the most flexible answer is hidden in HTML 2.
The font-stretch property was removed from CSS2 in the transition to CSS2.1. Unfortunately this leaves us with a rather gaping hole in overall font support.
Just recently Jeffrey Zeldman was bemoaning the sub-standard state of text rendering in Firefox on a Mac. And the sad truth is he only skimmed the surface; Firefox, Safari, Opera and Camino may render even the same font differently.
When inline images are displayed in box with -webkit-border-radius applied to it, the image is not cropped as expected. There is a simple workaround, at least for Safari.
There’s a different approach to web page layout which is gradually getting some traction. The idea is that the layout is changed to best accommodate the window size.
A tale of how typesetting a beautiful poster led to an exploration and explanation of how manually kerning type on the web can be tricky, but also made to work across browsers.