A reminder to review the Web Socket Protocol v10 spec by July 25:
https://datatracker.ietf.org/doc/draft-ietf-hybi-thewebsocketprotocol/
http://www.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-10.txt
Individual WG members are encouraged to provide individual feedback
directly to the
[ Bcc www-style ]
Marcos is gathering and organizing implementation data for the view-mode
Media Feature Candidate Recommendation [VMMF-CR] with a goal of moving
this spec to Proposed Recommendation:
http://dev.w3.org/2006/waf/widgets-vmmf/imp-report/
If you have any implementation data
* Arthur Barstow wrote:
A reminder to review the Web Socket Protocol v10 spec by July 25:
https://datatracker.ietf.org/doc/draft-ietf-hybi-thewebsocketprotocol/
http://www.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-10.txt
Individual WG members are encouraged to provide individual
On Thu, Jul 7, 2011 at 6:38 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 7, 2011 at 5:23 PM, Rafael Weinstein rafa...@google.com wrote:
So yes, my proposal only solves the usecase outside mutation handlers.
However this is arguably better than never solving the use case as in
your
Thanks for the new proposal, Jonas. I'm very excited about the progress
we're making towards a saner world!
On Tue, Jul 19, 2011 at 4:01 PM, Jonas Sicking jo...@sicking.cc wrote:
[ { target: node1, type: childlist, added: [a, b, c, d], removed: [x, y]
},
{ target: node1, type: attributes,
On Thu, 28 Apr 2011, Magnus Kristiansen wrote:
Context: http://krijnhoetmer.nl/irc-logs/whatwg/20110428#l-707
Current browsers disagree about how to handle div
id=x/divscriptvar x;/script. Webkit browsers leave x pointing to
the div, whereas IE, Firefox and Opera make x undefined [1].
Ian Hickson:
Is this still something I should do, or did this get resolved using
another solution?
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8241
The proposed solution I made in the bug was to have the [[Get]] etc.
internal methods of Window handle the resolution order of window named
On Tue, Jul 19, 2011 at 4:18 PM, Ryosuke Niwa rn...@webkit.org wrote:
Thanks for the new proposal, Jonas. I'm very excited about the progress
we're making towards a saner world!
On Tue, Jul 19, 2011 at 4:01 PM, Jonas Sicking jo...@sicking.cc wrote:
[ { target: node1, type: childlist, added:
On Wed, 20 Jul 2011, Cameron McCormack wrote:
Ian Hickson:
Is this still something I should do, or did this get resolved using
another solution?
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8241
The proposed solution I made in the bug was to have the [[Get]] etc.
internal methods of
On Tue, Jul 19, 2011 at 4:56 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Jul 19, 2011 at 4:18 PM, Ryosuke Niwa rn...@webkit.org wrote:
For editing purposes, it's also crucial to know from/to where nodes are
removed/inserted. It seems like adding an offset trivially solves this
On Jul 19, 2011, at 6:47 PM, Boris Zbarsky wrote:
On 7/19/11 7:43 PM, Ian Hickson wrote:
On Thu, 28 Apr 2011, Magnus Kristiansen wrote:
Context: http://krijnhoetmer.nl/irc-logs/whatwg/20110428#l-707
Current browsers disagree about how to handlediv
id=x/divscriptvar x;/script. Webkit
On 7/19/11 7:18 PM, Ryosuke Niwa wrote:
For editing purposes, it's also crucial to know from/to where nodes are
removed/inserted. It seems like adding an offset trivially solves this
problem without much overhead.
I'm not convinced about without much overhead. In general, adding an
offset
On 7/19/11 4:01 PM, Jonas Sicking wrote:
[ { target: node1, type: childlist, added: [a, b, c, d], removed: [x, y] },
{ target: node1, type: attributes, changed: [class, bgcolor, href] },
{ target: node2, type: characterdata },
{ target: node3, type: childlist, added: [r, s, t, x],
13 matches
Mail list logo
