On Mon, 1 Jul 2013, Ian Hickson wrote:
>
> One option would be to remove from the stack of open elements any
> elements that we are skipping when we bail out of the AAA.
>
> Can anyone see a problem with doing that?
I think that this solves the issue and clarifies the behaviour of
the parser.
On Jul 26, 2013, at 11:20 AM, Ian Hickson wrote:
> On Wed, 24 Jul 2013, Ryosuke Niwa wrote:
>> On Jul 16, 2013, at 11:25 AM, Ian Hickson wrote:
>>> On Tue, 16 Jul 2013, Takayoshi Kochi (河内 隆仁) wrote:
IIUC WebKit uses internally node's language to determine which font
to use to
On Wed, 23 Jan 2013, L. David Baron wrote:
>
> A few comments on the 'position: absolute-anchored':
> http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#css-position-absolute-anchored
>
> (1) The interaction with CSS transforms is different from the
> interaction that 'posi
On Thu, 1 Aug 2013, Peter Occil wrote:
>
> - "Let the current column be the first col element child of the colgroup
> element" is not considered ambiguous because the "colgroup element"
> mentioned is understood to be "the colgroup element in question" (see
> the beginning of the step: "If the
On Mon, 21 Jan 2013, L. David Baron wrote:
>
> I thought I'd brought this issue up before, but I can't seem to find a
> record of it.
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped
>
> currently says that, inside scoped style sheets, @page rules
On Wed, 20 Mar 2013, Benjamin Stürmer wrote:
>
> I've been thinking about this exact thing for the last few weeks,
> because I have a use case in which it would be beneficial to use an
> in-body to include CSS files, especially if could be
> updated to support the "scoped" attribute with the
- "Let the current column be the first col element child of the colgroup
element" is
not considered ambiguous because the "colgroup element" mentioned is
understood
to be "the colgroup element in question" (see the beginning of the step: "If
the current
element is a colgroup, follow these subs
On Thu, 1 Aug 2013, Peter Occil wrote:
>
> Sec. 12.2.4 (Tokenization) [...]
I mean not in what is today section 12.
For example, where the spec says "Let the current column be the first col
element child of the colgroup element". Why is that not ambiguous?
Right at the top of the spec it says "
Sec. 12.2.4 (Tokenization) doesn't contain ambiguous "so-and-so element"
wordings;
it involves not elements but tag tokens, which are not yet assigned to a
namespace.
Secs. 12.2.3 (Parse state) contains definitions used only in the tree
construction stage. And
some of these definitions contain
On Thu, 1 Aug 2013, Peter Occil wrote:
>
> Many of these cases occur in the normative portion of the tree
> construction stage. Most of them involve checking whether an element
> (as opposed to a tag token) has a certain name:
>
> Accordingly, these cases are ambiguous: [...]
Thanks for listin
Many of these cases occur in the normative portion of the tree construction
stage. Most of them involve checking whether an element (as opposed to
a tag token) has a certain name:
Accordingly, these cases are ambiguous:
* If foster parenting is enabled and target is a table, tbody, tfoot, thead
Our user agent is a HTTP proxy, currently we are feeding it HTML5 pages,
then we are parsing custom data-* attributes and replacing them with UI
components, for example data-carousel becomes a touch carousel, and so on.
Instead of creating another data-splashscreen attribute, we always try
standar
On Wed, 10 Jul 2013, Peter Occil wrote:
> >
> > Short of explicitly putting "in the HTML namespace" at every
> > occurrence of this, I don't know how to fix this. Putting "in the HTML
> > namespace" everywhere is a non-starter, there's something like ten
> > thousand occurrences of element names
> On Wed, Jul 31, 2013 at 9:15 PM, Ian Hickson wrote:
>> On Wed, 31 Jul 2013, Laurent Perez wrote:
>> >
>> > Is there work going on on a Splash screen specification ?
>>
>> What's the use case?
>>
>> Generally speaking, Web pages load incrementally, so by the time you've
>> downloaded an image, yo
On Thu, 1 Aug 2013, Laurent Perez wrote:
>
> The use case is to show a "please wait, loading..." message until all
> resources of an index page (js, css, html, images, fonts) are
> downloaded. When the message dismisses, the index page is ready for a
> non-blocking UI navigation since js was alr
The use case is to show a "please wait, loading..." message until all
resources of an index page (js, css, html, images, fonts) are downloaded.
When the message dismisses, the index page is ready for a non-blocking UI
navigation since js was already loaded.
We plan to implement it in our own user
16 matches
Mail list logo
