Archive for the 'Front-end code' Category
Posted February 11th, 2013 in Browsers, Front-end code, Mobile.
Taking my arguments about pixels being relative another step, the CSS pixel sizes that device makers use actually tell us the distance away from your eye that they think you should hold a device. Applying a bit of maths lets us work out what that distance is.
Posted in Browsers, Front-end code, Mobile | 1 Comment »
Posted November 8th, 2012 in Browsers, Front-end code, Mobile.
I keep reading recommendations for using EMs or other typographical units for layout, which I still don’t understand. At best it is an extra layer of abstraction, at worst it is misleading and likely to cause more issues than it solves. I will try to demonstrate why pixels are the best relative unit.
Posted in Browsers, Front-end code, Mobile | 12 Comments »
Posted April 7th, 2012 in Browsers, Front-end code, Mobile.
Layout methods in web design have gone through a transition in the last few years, unfortunately we’re still using floats a lot, but flexible layouts have made a comeback in the form of responsive design – which is great. Recently though, I have been puzzled by people suggesting that we should use EMs for layout…
Posted in Browsers, Front-end code, Mobile | 4 Comments »
Posted January 12th, 2012 in Accessibility, Browsers, Front-end code.
I’ve noticed a bug in Webkit browsers that impacts accessibility: Zooming in does not trigger media queries. Responsive design techniques can really help people who zoom in with their browser, but not in Chrome or Safari at the moment.
Posted in Accessibility, Browsers, Front-end code | 10 Comments »
Posted March 30th, 2010 in Front-end code, Mobile.
I came across a situation recently where a JavaScript widget didn’t ‘work’ on the iPhone. It did technically work, but without knowing about two-fingered scrolling (and when you need to use it), it didn’t appear to work. So how do you differentiate the iPhone (and other touch based devices) from a regular browser?
Posted in Front-end code, Mobile | 5 Comments »
Posted March 29th, 2010 in Front-end code, WYSIWYG editors.
A little post for those that run into the same problem I had with TinyMCE and blank instances not quite being blank. I created a little configuration to remove empty HTML tags.
Posted in Front-end code, WYSIWYG editors | Comments Off
Posted November 1st, 2009 in Front-end code, Mobile, Operating Systems, Web APIs.
I’ve just gotten back from a great day at the Stackoverflow Dev Day, I didn’t take my usual copious notes, but I thought a flavour of proceedings would be good to get down. For those who don’t know me, I have to add the caveat that I’m not a …
Posted in Front-end code, Mobile, Operating Systems, Web APIs | Comments Off
Posted February 11th, 2009 in Front-end code, W3C.
You may have noticed the W3C was asking for contributions for the running the validator. There is a way that you can support the W3c validation service – by not using it. The public version that is. If you use OSX, you can install it locally.
Posted in Front-end code, W3C | 4 Comments »
Posted September 7th, 2008 in Front-end code, Usability / IA, Web APIs.

My journey to d.construct was a long one, I hadn’t even checked which talks were when, so I was very thankful for the schedule built into your name tag! I took quite a few notes for general use, but please to refer to the originals where possible:…
Keynote: The urban
Posted in Front-end code, Usability / IA, Web APIs | 4 Comments »
Posted July 25th, 2008 in Accessibility, Front-end code, PDF / Flash.
I was writing a little accessibility article for .net magazine about text-replacement techniques, including sIFR. I was blithely saying that “yea, don’t worry, it’s fine” with a couple of caveats. But, rather than rely on memory I did a quick test, and discovered something strange.
Posted in Accessibility, Front-end code, PDF / Flash | 8 Comments »