On Tue, 9 Jun 2009, Kristof Zelechovski wrote:
* Let a COLOR element have a value DOM property in the DOM that returns a
color.
.value already does so.
* Let a NUMBER element has a value DOM property that returns a number.
.valueAsNumber already does so.
Actually, the latter use case is
* Let a COLOR element have a value DOM property in the DOM that returns a
color.
* Let a NUMBER element has a value DOM property that returns a number.
Actually, the latter use case is one I have bumped into:
* The DOM does not provide a numeric value,
* JavaScript support for parsing localized
Being unable to deal with all use cases sometimes is a feature. For
example, regular expressions are unable to recognize all recursive
languages; it is a feature. As a compensation for that loss, they do not
suffer from the halting problem.
HTH,
Chris
I do not think anybody in WHATWG hates the CURIE tool; however, the
following problems have been put forward:
Copy-Paste
The CURIE mechanism is considered inconvenient because is not
copy-paste-resilient, and the associated risk is that semantic elements
would randomly change their
On 15/5/09 14:11, Shelley Powers wrote:
Kristof Zelechovski wrote:
I do not think anybody in WHATWG hates the CURIE tool; however, the
following problems have been put forward:
Copy-Paste
The CURIE mechanism is considered inconvenient because is not
copy-paste-resilient, and the associated
On Fri, May 15, 2009 at 1:44 PM, Kristof Zelechovski
giecr...@stegny.2a.pl wrote:
I do not think anybody in WHATWG hates the CURIE tool; however, the
following problems have been put forward:
Copy-Paste
The CURIE mechanism is considered inconvenient because is not
On Fri, May 15, 2009 at 9:17 AM, Eduard Pascual herenva...@gmail.com wrote:
On Fri, May 15, 2009 at 1:44 PM, Kristof Zelechovski
Link rot
CURIE definitions can only be looked up while the CURIE server is
providing them; the chance of the URL becoming broken is high for
home-brewed
