Hi all,
I just got a little burned by Chrome's new date popup for HTML date-type
inputs!
*Why?*
- Because when I wrote the original code, I hadn't read up on the new
properties being added to HTML5 input types
- Because I was using a js-based datepicker plugin to implement the same
On 02/07/2012 01:55, James Ducker wrote:
element.valueAsDate
This property is designed to solve your locale woes, and it is also an
easy way to feature-detect a browser's native support for the date input
type. I haven't gone through all current browsers yet, so if you do use
this method, make
The only issue I've found so far is that Safari's implementation of the
date type sucks. It gives you little up/down chevrons which add or subtract
one day at a time. So my working code also treats Safari as
datepicker-not-implemented.
For me, as I make use of the valueAsDate property when it's
Thanks David.
I think ePub3 and HTML5 support is still not here. When converting the HTML5
doctype files to ePub, Sigil (an ePub editor) forces ePub2 version and stripped
all HTML5 tags.
Converting to mobil format for Amazon Kindle is even worse, I feel as if
dealing with the IE6 7.
Tee
These e-mails aren't intended for me, but I keep on receiving them.
Ted Knoy
On Mon, Jul 2, 2012 at 10:52 AM, tee weblis...@gmail.com wrote:
Thanks David.
I think ePub3 and HTML5 support is still not here. When converting the
HTML5 doctype files to ePub, Sigil (an ePub editor) forces ePub2
These e-mails aren't intended for me, but I keep receiving them.
Ted Knoy
On Mon, Jul 2, 2012 at 9:57 AM, James Ducker james.duc...@gmail.com wrote:
The only issue I've found so far is that Safari's implementation of the
date type sucks. It gives you little up/down chevrons which add or
