On 12-12-11 5:23 PM, Ralph Giles wrote:
> That said, I'm not convinced this is an issue given the primary
> use-case, which is pretty much that web content wants to do more
> sophisticated things with the metadata than the user-agent's
> standardized parsing allows. If one cares to that extent, an
On Wed, 16 Jan 2013 13:48:43 -, Bronislav Klučka
wrote:
3/ Way for styling native controls are pseudo-classes, the fact, that we
do not have those yet is hardly reason for abandoning it. We would have
no progress at all if we had dropped every technology that is not
perfect for every
On 16.1.2013 14:16, Bruce Lawson wrote:
On Wed, 16 Jan 2013 11:01:14 -, Tab Atkins Jr.
wrote:
Strongly agree. I think any arguments that sites will refuse to use
the native controls because they don't match the site's theme are
countered by the observation that most sites using JS-libr
On Wed, 16 Jan 2013 11:01:14 -, Tab Atkins Jr.
wrote:
Strongly agree. I think any arguments that sites will refuse to use
the native controls because they don't match the site's theme are
countered by the observation that most sites using JS-library
equivalents today still don't theme t
On Wed, Jan 16, 2013 at 1:03 AM, Bronislav Klučka
wrote:
> On 16.1.2013 8:23, Jukka K. Korpela wrote:
>> Since the use cases are rare, is it better to force browser vendors to
>> develop code to implement it, in their own ways, than to let various
>> software developers set up libraries for it? Si
On 2013-01-08 01:47, Ian Hickson wrote:
The next best choice would be to have datetime-with-timezone but
unfortunately
(1) Official database for all timezones does not exist
(2) Official timezone names (or labels) do not exist
(3) Timezones are subject to future political decisions
The problems
On 16.1.2013 8:23, Jukka K. Korpela wrote:
Since the use cases are rare, is it better to force browser vendors to
develop code to implement it, in their own ways, than to let various
software developers set up libraries for it? Since the browser
implementations would, with practical certaint
