Archived posts, January 2011
Safari for iOS needs a text size preference and text reflow
Safari for iOS needs a text size preference or a control to change text size. It also needs to reflow text to make line lengths fit the screen.
iOS browsers that allow font scaling and text reflow
Safari for iOS doesn’t offer text resizing. Two third-party browsers that do are iCab Mobile and Atomic Web Browser, both of which also reflow text after a font size change.
Make your iPad and iPhone apps accessible
iOS has great potential for accessibility, but application developers need to do their part to make their apps fully accessible. Fortunately it seems pretty straightforward.
Merging directories (folders) on Mac OS X
Copying a folder on top of another folder with the same name in the Mac OS X Finder will replace the entire contents of the target folder. This is not always what you want, so luckily there are other ways of copying folders.
Why do drive-through ATMs have Braille keypads?
It may not seem obvious why drive-through ATMs would have Braille keypads to enable blind persons to use them. But once you know the answer it’s quite simple.
Media queries, viewport width, scrollbars, and WebKit browsers
WebKit-based browsers do not include vertical scrollbars in the viewport width, which goes against the Media Queries specification and differs from Firefox and Opera.
HTML5 now includes CSS3, SVG and WOFF?
Having a nice-looking logo for HTML5 is neat, but I think it’s unfortunate that the W3C are reinforcing the widespread misconception that HTML5 is pretty much anything “Web” that isn’t Flash.
HTML5 logo FAQ updated to add clarification
The W3C HTML5 logo FAQ has been updated to clarify what the logo and its accompanying icons represent and that CSS3 is not part of HTML5.
HTML beyond HTML5
The WHATWG announces that they will now work on a versionless version of HTML, making it a moving target that may make it less than ideal for web developers to reference in their daily work.
CSS Validator to report vendor-specific extensions as warnings, not errors
The W3C CSS Validator is about to add an option where you can choose to have vendor-specific extensions reported as warnings rather than errors, making it easier to find real errors in your CSS.