http://www.w3.org/Bugs/Public/show_bug.cgi?id=14364
Simon Pieters sim...@opera.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
On Fri, 04 Nov 2011 00:48:29 +0100, Anne van Kesteren ann...@opera.com
wrote:
On Thu, 03 Nov 2011 16:44:49 -0700, Tim Down timd...@gmail.com wrote:
Have you looked at the createContextualFragment() method of Range?
http://html5.org/specs/dom-parsing.html#dom-range-createcontextualfragment
(Sorry for replying to somewhat ancient thread)
On Wed, Sep 28, 2011 at 1:43 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Sep 27, 2011 at 6:12 AM, Kinuko Yasuda kin...@chromium.org
wrote:
Just to confirm: Yes the interfaces are vendor prefixed (WebKit), and
WebSQL, AppCache, IDB are
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14694
Summary: innerHTML in DocumentFragment
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
On 11/3/11 5:16 PM, ext Peter Saint-Andre wrote:
On 11/3/11 8:28 AM, Anne van Kesteren wrote:
On Thu, 03 Nov 2011 08:07:20 -0700, Julian Reschke
julian.resc...@gmx.de wrote:
Reminder: this was a past-LC change. I think I'm not asking too much
when I'm asking for a precise explanation of what
On 2011-11-04 17:10, Arthur Barstow wrote:
...
The group discussed this on October 31 [1]. The gist of the agreement is
that since the text that is now in the API spec used to be in the
protocol spec, the totality of a review of the two specs is effectively
the same. In this view, the change to
On Fri, 04 Nov 2011 09:18:29 -0700, Julian Reschke julian.resc...@gmx.de
wrote:
On 2011-11-04 17:10, Arthur Barstow wrote:
The group discussed this on October 31 [1]. The gist of the agreement is
that since the text that is now in the API spec used to be in the
protocol spec, the totality of a
Instead of simply switching the insertion mode when you see an element that
doesn't belong in in-body mode for context-less parsing, would it make
sense to synthesize the appropriate context elements instead?
Daniel
On Fri, Nov 4, 2011 at 05:54, João Eiras jo...@opera.com wrote:
On Fri, 04 Nov
On Fri, Nov 4, 2011 at 9:33 AM, Daniel Cheng dch...@chromium.org wrote:
Instead of simply switching the insertion mode when you see an element that
doesn't belong in in-body mode for context-less parsing, would it make sense
to synthesize the appropriate context elements instead?
If I
On 2011-11-04 17:36, Anne van Kesteren wrote:
On Fri, 04 Nov 2011 09:18:29 -0700, Julian Reschke
julian.resc...@gmx.de wrote:
On 2011-11-04 17:10, Arthur Barstow wrote:
The group discussed this on October 31 [1]. The gist of the agreement is
that since the text that is now in the API spec used
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14695
Tab Atkins Jr. jackalm...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Questions and thoughts while reading
http://dev.w3.org/2006/webapi/FileAPI/#enctype:
What does cannot determine the encoding mean in step 1? Does that mean
if the UA doesn't support the encoding? If not, is this spec actually
requiring that every registered encoding be supported?
It's odd that
In that example, there was a clear context element though--I'd argue
that Range.createContextualFragment should have been used instead.
It seems like the general use of such a function would be to add some
nodes from a snippet of HTML markup into a div for example, where
synthesizing the correct
2011/11/4 Daniel Cheng dch...@chromium.org:
In that example, there was a clear context element though--I'd argue
that Range.createContextualFragment should have been used instead.
It seems like the general use of such a function would be to add some
nodes from a snippet of HTML markup into a
On Fri, Nov 4, 2011 at 11:19, Tab Atkins Jr. jackalm...@gmail.com wrote:
2011/11/4 Daniel Cheng dch...@chromium.org:
In that example, there was a clear context element though--I'd argue
that Range.createContextualFragment should have been used instead.
It seems like the general use of such a
Sent from my iPhone
On Nov 4, 2011, at 11:55 AM, Daniel Cheng dch...@chromium.org wrote:
On Fri, Nov 4, 2011 at 11:19, Tab Atkins Jr. jackalm...@gmail.com wrote:
2011/11/4 Daniel Cheng dch...@chromium.org:
In that example, there was a clear context element though--I'd argue
that
On Fri, Nov 4, 2011 at 12:15, Yehuda Katz wyc...@gmail.com wrote:
Sent from my iPhone
On Nov 4, 2011, at 11:55 AM, Daniel Cheng dch...@chromium.org wrote:
On Fri, Nov 4, 2011 at 11:19, Tab Atkins Jr. jackalm...@gmail.com wrote:
2011/11/4 Daniel Cheng dch...@chromium.org:
In that example,
My use-cases all want pure DOM nodes with no extra cruft added,
because they assume insertion into proper containers. This is true
about both jQuery and future updates to template content inserted in
the DOM.
For the use case of give me nodes that I can insert into a regular
context and then
Hi All,
One of the topics discussed this week was to designate a Test Spec
Editor(s) for each of our specs.
One reason to identify Test Spec Editors is to acknowledge that some
Spec Editors don't have the cycles to lead their spec's testing effort
and another is to try to prevent the
19 matches
Mail list logo
