On Feb 14, 2008, at 1:46 PM, Ian Hickson wrote:
This problem exists today with postMessage() too. Do people think we
should go fully asynchronous?
No objections from me...
-Henry
On Feb 14, 2008, at 11:18 AM, Anne van Kesteren wrote:
Given that everyone is now updating their postMessage() code
anyway, I wonder if it's possible to quickly make another minor
tweak. The proposal is to remove the source attribute from
MessageEvent and replace it with a reply() method. T
There's recently been some talk about completely removing HTML 5
section 6.2, "Server-sent DOM events". I propose that rather than
remove, we revise.
The major concerns I've heard about section 6.2 include:
- Unnecessary dependency on DOM Events
- Redundancy with already existing techniques,
On Dec 29, 2007, at 12:01 PM, Philip Parker wrote:
The removal of ogg as a baseline for audio/video implementation
strikes me as ridiculous. Theres nothing stopping other formats from
being used after all
If the specification included the Ogg baseline and few web browsers
actually supported
On Dec 11, 2007, at 1:21 PM, Manuel Amador (Rudd-O) wrote:
I actually think this Slashdot comment summarizes the sentiment
perfectly:
"Methinks you are being a bit myopic here. Where would we be today
if the HTML
spec didn't specify jpg, gif, and png as baseline standards for the
image
Hey all-
I've been working on an implementation of Server-Sent DOM Events. I
ran into a small inconsistency in the specifications as they stand.
Under section 6.2.4's "Class field" part:
If the Namespace is null and the Event field is message (including
if it was not specified expli
