http://www.w3.org/Bugs/Public/show_bug.cgi?id=10127
Summary: EventSource does not need to deal with HTTP 3xx
responses as they are dealt with by the fetching
algorithm.
Product: WebAppsWG
Version: unspecified
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10128
Summary: Step 4 of the EventSource algorithm should reference
the fail the connection algorithm.
Product: WebAppsWG
Version: unspecified
Platform: Other
URL:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10129
Summary: The end of this WebSocket section links to EventSource
with fail the connection. It should link to the
WebSocket fail the connection instead.
Product: WebAppsWG
Hello,
I'm not very familiar with how everything works here at w3 but I
believe there are bugs in the final example script in both levels of
selectors-api, including the latest drafts of each. The variable
elms is being referenced but is not defined. Instead the variable
list is declared which
On Fri, Jul 9, 2010 at 12:50 PM, Nikunj Mehta nik...@o-micron.com wrote:
On Jul 10, 2010, at 12:29 AM, Jonas Sicking wrote:
On Fri, Jul 9, 2010 at 11:05 AM, Nikunj Mehta nik...@o-micron.com wrote:
We would not make dynamic transactions be the default since they would
produce more concurrency
Hi, Robert-
Nice to have worked with you. Good luck in your future endeavors.
Regards-
-Doug
Ennals, Robert wrote (on 7/8/10 5:02 PM):
Hi Guys,
I have chosen to leave Intel and so will no longer be representing Intel
in the HTML or WebApps working groups. The other Intel reps in the HTML
WG
