Release Modernizr 1.6

[paulirish]

1.6 changelog

new features:

• webgl
• touch
• flexbox
• inline svg
• text-shadow

  fixes

• ie9 h264 fix
• input type range android false positive fix
• ie9 hsla fix
• strengthened input type tests
• try/catch around local/sessionStorage to prevent exceptions in security-minded firefox users.

  todo:

• revised (and much smaller) @font-face detect: DONE
• inline all the strings for smaller filesize and more clarity: DONE a7e834218e7fb923556e31feeb55f5a6a2a5fc8d
• assure accurate IE9 results: see #99 DONE
• wait for IE9 beta. test. DONE
• wait for chrome 6 stable, and re-enable touch detection. DONE
• revise API for some properties: see #101 Done.
• collect all additional tests and make them accessible somehow? probably on the github wiki. (mostly done. also has.js)

[paulirish]

touch status is here http://modernizr.github.com/Modernizr/touch.html i'll probably add in firefox multitouch support before its done.

we went from 11.04KB (5.04KB gzipped) to 9.06KB (3.67KB gzipped)

[paulirish]

web sql database.

it's annoying. so we have to try out it forreal because otherwise its a false positive in chrome incognito.

but that has two side effects

• prompts to safari users who change their security settings about creating a database (eh. they deserve it)
• litters databases on all these domains (you see them on mobile webkit settings).. we cant expire or delete them. kinda sucks.

should we remove web sql test?

so far, twitter had a problem with the Firefox session/localStorage ... but didn't complain about web sql... soooo.. shrug.

[SlexAxton]

I'd be in favor of fixing the web sql test for chrome incognito, but also in favor of pulling it out into an optional test. It's just too much cruft for such an uncommon test. Perhaps a build tool would help with this, but until then, I think pulling it out may be best.

[paulirish]

yeah websql is out of favor in place of indexeddb.. but indexeddb is still not ready and prefixed implementations are only just landing like.. this week.. in ff and webkit. so it'll be a bit.. but who knows.

right now i'm leaning towards getting rid of it. (or just commenting out the incognito fix and documenting that shit)

also adding textshadow might be a good idea. it was in css2.0 but out of 2.1.. which is why its sorta new in css3 (same thing with @font-face)

[KuraFire]

I'm okay with commenting out the incognito fix and documenting this issue. Web databases (the lot of them) are in so much flux right now, I think that we're better off trying to cause as little impact as possible whilst the situation continues to be volatile. Thus, avoiding having to physically create a database and letting that linger in the user's browser, for each domain. Does that sound okay?

Text shadow was taken out originally because it had false positives in Firefox… 3, I think. Whichever version was still widely used at that time. I think by now we could put it back in, but with a warning/comment about it, and also documenting that there are some browsers it false-positives on.

[KuraFire]

Oh, I forgot the elephant in the room. Touch.

Am I missing a simpler delta in the touch test page results? It seems to me that the only way we can reliably claim touch support is to execute all four tests and map it out. And even then we can't identify the Palm Pre/WebOS touch devices because [per 1.4] it doesn't support any touch events.

Mind you, who knew that Safari 3.1.2, 4.0 and 4.0.4 would add to our list of issues with reliably detecting this. That kind of really sucks.

[KuraFire]

Returning to the subject of text-shadow: I knew I forgot something, but couldn't remember what. We placed the text-shadow test in the Docs as sample for the addTest() API, and explained with a comment in the docs that it false-positives. I'm okay with moving it into the main library as long as we keep that comment in there, but if we do that we should also mention the false positive in the 1.6 release notes.

[paulirish]

websqldatabase now is back to the chrome incognito false positive, but we're not creating databases. in 2.0 when people include these tests by choice, we should flick back on the db creation.

i've finalized the rest of the code and tweeted to get some beta testers: http://twitter.com/Modernizr/status/27354274026

[paulirish]

IE print protector has been updated. some extra unit tests.

f1lt3r said the multitouch test didnt pass on his FF4 multitouch device.. i'm going to have him look into that.

[paulirish]

touch is all set.

modernizr 1.6 is ready.

[SlexAxton]

EFF YEA

[KuraFire]

http://www.modernizr.com/news/modernizr-1-6 is out, this issue is now done.