On 2013/06/29 4:30, Tom Wiltzius wrote:
The only major Canvas2D features being actively developed in Chromium right
now are:
- having a canvas context alpha attribute
- text decoration
I thought some pretty strong objections were raised to text decoration.
Why are you actively developing
On Sun, Jun 30, 2013 at 9:44 PM,
Jussi Kalliokoski jussi.kallioko...@gmail.com wrote:
On Sat, Jun 29, 2013 at 5:01 AM, Boris Zbarsky bzbar...@mit.edu wrote:
This is actually false. For example, getElementById(foo:bar) is just
querySelector(#foo\\:bar), which is ... nonobvious.
It
First, Beside the already mentioned good arguments, I'd says that even for
consistency purpose those DOM get methods should be available on
DocumentFragment.
I mean, that's easy to think about libs / frameworks / devtools, public or
internal, providing methods expecting a Document as parameter
On Mon, Jul 1, 2013 at 1:56 AM, Octavian Damiean odami...@linux.comwrote:
I completely agree with Jussi here. It's also not really constructive to
argue whether querySelector is more powerful not, we're talking about
consistency.
It's a little inconsistent to agree with something other
On Sun, Jun 30, 2013 at 11:49 PM, Mark Callow callow.m...@artspark.co.jpwrote:
On 2013/06/29 4:30, Tom Wiltzius wrote:
The only major Canvas2D features being actively developed in Chromium right
now are:
- having a canvas context alpha attribute
- text decoration
I thought some
There have been a number of high-impact normative changes and high-risk
editorial changes to the HTML parser in the last few days.
This refactored the parser logic for foster parenting:
http://html5.org/tools/web-apps-tracker?from=7997to=7998
This defined ownerDocument for the parser, which
On Sat, 3 Nov 2012, Yasuhiko Minamide wrote:
This is about Adaption Agency Algorithm in 12.2.5.4.7 The in body
insertion mode.
Limits of loops in the adoption agency algorithm were introduced in
http://html5.org/tools/web-apps-tracker?from=5641to=5642. However, the
limit for the inner
On Fri, 15 Mar 2013, Mohammad Al Houssami (Alumni) wrote:
I just want to make sure that in places where no state change is called
it means we stay in the same state right? Take the RCDATA state below.
In the anything else branch we emit character token and then go consume
another
On Mon, 25 Mar 2013, Mohammad Al Houssami (Alumni) wrote:
Can someone explain wat is meant in the attribute value double quoted
state in the tokenization specs [...] What does the additional allowed
character mean? [...] It didn't make any sense to me. Im still a
beginner and know very few
On Tue, 26 Mar 2013, Henri Sivonen wrote:
In various places that deal with encoding labels, the HTML spec now
requires authors to use the name of the encoding from the Encoding
Standard, which means using the preferred name rather than an alias.
Compared to the previous reference to the
On Thu, 9 May 2013, Michael Day wrote:
Hilarious spec bug of the week: HTML5 requires implementations to loop
indefinitely if they see a menuitem start tag.
12.2.5.4.7 in body insertion mode
= see a menuitem start tag, process using rules for in head
12.2.5.4.4 in head insertion mode
On Thu, 18 Apr 2013, Michael Day wrote:
Another issue regarding recent changes to 12.2.5.5 The rules for
parsing tokens in foreign content.
When a HTML start tag is seen (specifically b, big, blockquote,
body, br, center, code, ...) the following procedure is given to
recover from the
On Fri, 10 May 2013, Thomas F�tiveau wrote:
- The initial insertion mode of the tree construction stage specifies to add
a doctype to the associated document when a doctype token shows up:
On Tue, 16 Apr 2013, Michael Day wrote:
Recently the spec has been changed to introduce the concept of the
adjusted current node defined in 12.2.3.2 The stack of open elements.
The intention seems to be to handle the case of setting innerHTML on a
MathML or SVG element, and hence
On Tue, 14 May 2013, Michael Day wrote:
If a newline character token follows a pre or textarea start tag, it
is supposed to be ignored as an authoring convenience.
However, what if a NULL character token gets in the way?
It's the next token. I've clarified the spec (in response to the bug
On Sun, 23 Jun 2013, Mohammad Al Houssami (Alumni) wrote:
I am building an HTML5 parser according to the specs on the whatwg
website. I am currently in the tree construction stage and it seems to
be so complex to have a general view of what is happening by reading the
specs or at least
On Mon, Jul 1, 2013 at 1:20 AM, Alexandre Morgaut
alexandre.morg...@4d.com wrote:
First, Beside the already mentioned good arguments, I'd says that even for
consistency purpose those DOM get methods should be available on
DocumentFragment.
I mean, that's easy to think about libs /
On Mon, Jul 1, 2013 at 6:16 PM, Ian Hickson i...@hixie.ch wrote:
It seems bad, and maybe rather full of hubris, to make it conforming to
use a label that we know will be interpreted in a manner that is a willful
violation of its spec (that is, the ISO spec).
It's hard enough to get people to
18 matches
Mail list logo
