iandevlin

6 ms·

1.
by iandevlin 9y ago
In these cases, no, they wouldn't be thrown out. The aim is always to accept accessibility changes but they still need to be tested first, just in case they have negative affects which would need further investigation to be fixed.
2.
The woes of date input(html5doctor.com)
1 points by iandevlin 11y ago|0 comments
3.
On Accessibility and the Lack of Proper HTML(iandevlin.com)
1 points by iandevlin 11y ago|0 comments
4.
Using the Web Speech API to control a HTML5 video(iandevlin.com)
1 points by iandevlin 13y ago|0 comments
5.
Resimagecrop - a RESS based responsive image solution(iandevlin.com)
1 points by iandevlin 13y ago|0 comments
6.
CSS Stacking with display:table(iandevlin.com)
1 points by iandevlin 13y ago|0 comments
7.
Hgroup element removed from the HTML5 specification(iandevlin.com)
4 points by iandevlin 13y ago|0 comments
8.
Testing for Internet Explorer just got a little easier(modern.ie)
1 points by iandevlin 14y ago|0 comments
9.
by iandevlin 14y ago
Hi, I wrote HTML5 Bones and to be fair Simon has a good idea (detailed in the GitHub pull request) in that there should be two versions, a file with all the comments and one without - and so catering for both types of users. I definitely do
10.
by iandevlin 14y ago
I certainly can't reproduce it :-/
11.
HTML5 video for retina displays(iandevlin.com)
2 points by iandevlin 14y ago|0 comments
12.
Responsive images in HTML5 without using JavaScript(iandevlin.com)
1 points by iandevlin 14y ago|0 comments
13.
HTML5 media and data URIs(iandevlin.com)
2 points by iandevlin 14y ago|0 comments
14.
Responsive HTML5 video(iandevlin.com)
1 points by iandevlin 14y ago|0 comments
15.
by iandevlin 14y ago
I think this is a bad idea as it's supporting bad, lazy developers who can't be bothered to learn their craft correctly. I've written a bit more about these "WODs" at http://www.iandevlin.com/blog/2012/04/css/on-vendor-prefixes...
16.
On vendor prefixes and WODs(iandevlin.com)
1 points by iandevlin 14y ago|0 comments