The specified value ':)' does not conform to the required format, 'yyyy-MM-dd'.

[JRGould]

I'm receiving this javascript error in the latest build of chrome canary ( 39.0.2127.0 ) with modernizr 2.8.3 on line 536.

The specified value ':)' does not conform to the required format, 'yyyy-MM-dd'. modernizr.js:536

It looks like the variable smile is set to :) and is being used to set the values on HTML5 form elements that are being generated by modernizr and when the <date> element is created with a value of :) it's causing Canary to fire a validation error.

[ryanseddon]

@paulirish is this sort of message going to make it to stable dev tools? Seems a bit annoying to do that.

[paulirish]

Commit: https://codereview.chromium.org/461323006
Bug: https://code.google.com/p/chromium/issues/detail?id=397952

Currently this is on track to go to stable yup. I will talk to the engineers. I don't think this should be Error level messaging.

[paulirish]

What this looks like:

[paulirish]

Okay, watch this thread: https://code.google.com/p/chromium/issues/detail?id=397952#c3

The webforms engineers are in Tokyo so we should get a response "today". :)

[ryanseddon]

Sweet thanks @paulirish, we'll keep this open and track the chromium issue.

[chrishough]

+1

[paulirish]

thx for reporting @JRGould

[JRGould]

Glad I could help! :)

[paulirish]

Chromium ticket is now here: https://code.google.com/p/chromium/issues/detail?id=405227

Relatedly, Chrome forms team has had to work around Modernizr's feature detects before. :)
http://src.chromium.org/viewvc/blink?view=revision&revision=141086
Sorry about that!

[patrickkettner]

code is being merged - https://codereview.chromium.org/491703002

Its going to be updated/reverted in Chrome 38, which will be beta soon. Discussion is in the thread, but they are basically only showing the error when the input is visible

[paulirish]

​Slightly more specific:

• Chrome 38 is going to beta soon and will not have this error at all.
  The change will be completely reverted there tanks to the merge on the
  chromium ticket listed above.
• The codereview link features a patch that will be landing in Chrome 39
  (Canary now). It adjusts the error to be 1) a warning and 2) not triggered
  on Modernizr. Somehow. Magic mostly.

[heby]

Google Chrome 38.0.2125.0 dev-m (64-bit)

[patrickkettner]

@heby - to be clear, this change is happening between the versions of 38 that ships in dev and the version that ships to beta.

[L422Y]

:)

[isarmstrong]

What did I do before the days of rapid-indexing on Google? I would have spent hours trying to figure out what I'd broken.

[RobinQu]

+1

[patrickkettner]

This was fixed in chrome

[snymax]

I am getting this error in node-webkit am I stuck with it until nw.js is updated

[patrickkettner]

@snymax this isn't an error - its just a super annoying warning. you can ignore it.

[patrickkettner]

@brilyuhns what do you mean?