Example isn't working at all about better-dateinput-polyfill HOT 10 CLOSED

What browser you are using?
It seems to be working in both last version of Chrome and Firefox.

from better-dateinput-polyfill.

Hi and thanks for your help.

i'm using chrome Version 45.0.2438.3 dev (64-bit), on linux. it doesn't have any weird flag because i use it to test our websites.

from better-dateinput-polyfill.

I don't know for sure but I think it's suppose to be like this because the demo isn't forcing the polyfill from the plugin.
If you go here and here you are going to see more about how to format the date and force the polyfill, respectively.
Oh, and FYI I got the exact same behavior in my version of Chrome.

from better-dateinput-polyfill.

i though it was the other way around, that you can force having a native support:

For example, the code below defines a dateinput that uses a native implementation on mobile phones, but ALL desktop browsers (even Chrome desktop) will have a consistent widget created by the polyfill.

<input type="date" data-native="mobile" name="foo" value="bar">

if you click onit, does it open the plugin's calendar?

from better-dateinput-polyfill.

Yes, it does. Using this code snippet I can see the plugin's calendar even in Chrome as was stated in the text above.

from better-dateinput-polyfill.

on firefox i get the plugin calendar and the placeholder is showing too.

from better-dateinput-polyfill.

Yep, same as me.
I think Firefox don't have full support for date input yet so that's why the plugin's polyfill is being used by default.

from better-dateinput-polyfill.

that makes sense!

so, how did you force it to show on chrome?

from better-dateinput-polyfill.

I use the data-native="mobile" property as I said before.

from better-dateinput-polyfill.

Read docs guys ;)

from better-dateinput-polyfill.