W3C home > Mailing lists > Public > www-svg@w3.org > October 2011

Re: Case-Sensitivity & SVG-in-HTML5

From: Dirk Schulze <vbs85@gmx.de>
Date: Mon, 31 Oct 2011 19:42:35 +0100
Cc: www-svg@w3.org
Message-Id: <C5D76A32-DAAD-4E25-8821-58F75038B674@gmx.de>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
I tested the example at the webkit bug report on a Firefox nightly again:

[19:38:52.403] document.getElementsByTagName('lineargradient').length
[19:38:52.405] 0
[19:38:57.755] document.getElementsByTagName('linearGradient').length
[19:38:57.757] 1

So I agree, Firefox is doing it right currently. I thought that both calls worked the last time I tested it. Sorry.


Am 31.10.2011 um 19:14 schrieb Boris Zbarsky:

> On 10/31/11 12:50 PM, Dirk Schulze wrote:
>> This is an implementation problem of WebKit and Opera (at least the last
>> time I tested Opera Next with HTML5 parser) that this doesn't work for
>> camel case local names. Firefox on the other side did not implement it
>> correctly either, since elements can be lowercase and uppercase there.
> The Firefox behavior here exactly follows the spec, as far as I can tell.  What am I missing?
>> If you want elements of all namespaces to be case insensitive for HTML documents, you should
>> send the request to the DOM WG (and maybe whatwg mailing list), since it
>> does not only affect SVG.
> This has been discussed before.  If that were done, there would be some immediate issues with html:textarea vs svg:textArea and such....
> -Boris
Received on Monday, 31 October 2011 18:43:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:26 UTC