Re: [whatwg] for year input

Nils Dagsson Moskopp writes: > Jonathan Watt writes: > > > is it wrong to use for year input. > > I am certainly not an expert on the topic, but I believe the > conceptual problem can be reduced to using an input designed for a > group (in the mathematical sensce) to represent a value that is

Re: [whatwg] for year input

Jonathan Watt writes: > is it wrong to use for year input. I am certainly not an expert on the topic, but I believe the conceptual problem can be reduced to using an input designed for a group (in the mathematical sensce) to represent a value that is torsor. Quote

Re: [whatwg] new autocomplete="" values for authentication forms (was Re: Autocomplete and autofill features and feedback thereon)

I've been meaning to suggest this for a while now, but just haven't gotten around to it. Chrome would be definitely implement autofill attributes along these lines. I'm relatively indifferent to the exact syntax. Another related issue that would be nice to address would be allowing sites to positi

Re: [whatwg] for year input

Ryosuke Niwa writes [re-ordered]: > > On Feb 19, 2014, at 7:36 AM, "Jukka K. Korpela" > > wrote: > > > > 2014-02-19 11:10, Smylers wrote: > > > > > Jukka K. Korpela writes: > > > > > > > The point is that year numbers aren't really "numbers" in a > > > > normal sense, any more than car plate n

Re: [whatwg] for year input

Let me point out that not every calendar uses simple 2-4 digit numbers to denote years. The Japanese era name calendar system, for example, requires an era name such as Showa and Heisei associated with each year. For example, I was born in Gregorian year 1986 but any Japanese government docume