[Calendar] Chrome chooses wrong hour on time-only calendar

[exoego]

Description

Fomantic-UI/src/definitions/modules/calendar.js

Lines 1355 to 1358 in 0269a82

	var textDate = new Date(text);
	if(!isNaN(textDate.getDate())) {
	return textDate;
	}

The above code expects parsing on partial input, e.g. 1, to be failed on new Date("1").
However, there are incosintency between browsers on how new Date consturctor or Date.parse works.

input	Chrome	Firefox
new Date("1")	success	invalid
new Date("10")	success	invalid
new Date("100")	success	invalid
new Date("1000")	success	success

On Chrome, new Date("1") or such can create instance of Date.
So, getDate is a number, then hour is not chosen correctly.

This PR adds a check input is number-only `^[0-9]+$ or not.
If input is number-only, it should go to time-only or date-only logic.

Testcase

Broken (on Chrome)

https://jsfiddle.net/m8a4r3t9/

Fixed (on Chrome)

https://jsfiddle.net/9og37k1t/1/

Closes

#1354

[lubber-de]

LGTM

[ko2in]

LGTM.