[Bug 12584] outerHTML should probably merge with adjacent text nodes if applicable. IE seems to do this to some extent, and WebKit just changed to do it: <https://bugs.webkit.org/show_bug.cgi?id=52686> This test shows behavior for outerText and outerHTML: <http://so
[Bug 13071] "Once the end of the file is reached, the user agent must dispatch the event one final time, as defined below" means an implementation may parse a partial (corrupt) event as a final event if the connection is interrupted. Spec should always require an exp
[Bug 13083] postMessage should have an optional parameter for a synchronous request. Cross-domain AJAX calls are enough of a problem that it merits a supported way of fixing it, and this could be it.
[Bug 13162] New: The notes really do need to be cleaned up to be made explicit. Like WTH does this actually say? "The fail the WebSocket connection algorithm invokes the close the WebSocket connection algorithm, which then establishes that the WebSocket connection is clo
[Bug 13162] The notes really do need to be cleaned up to be made explicit. Like WTH does this actually say? "The fail the WebSocket connection algorithm invokes the close the WebSocket connection algorithm, which then establishes that the WebSocket connection is clo
[Bug 13229] New: The following text from the "Security considerations" part of "11 IANA considerations" is wrong: "An event stream from an origin distinct from the origin of the content consuming the event stream can result in information leakage. To avoid this, user agen
[Bug 13229] The following text from the "Security considerations" part of "11 IANA considerations" is wrong: "An event stream from an origin distinct from the origin of the content consuming the event stream can result in information leakage. To avoid this, user agen
[Bug 13232] I think the section on DedicatedWorkerScope should include information about the kinds of data that postMessage can send to a worker, and the kinds of data that a worker can send back. http://dev.w3.org/html5/workers/#dedicated-workers-and-the-dedicatedwo
[Bug 13232] New: I think the section on DedicatedWorkerScope should include information about the kinds of data that postMessage can send to a worker, and the kinds of data that a worker can send back. http://dev.w3.org/html5/workers/#dedicated-workers-and-the-dedicatedwo
[Bug 13255] New: When I use importScripts in my worker to load a separate "library" file, it works, but I get the error: ReferenceError: Can't find variable: importScripts (Safari) Uncaught ReferenceError: importScripts is not defined So it's throwing an error, but that
[Bug 13255] When I use importScripts in my worker to load a separate "library" file, it works, but I get the error: ReferenceError: Can't find variable: importScripts (Safari) Uncaught ReferenceError: importScripts is not defined So it's throwing an error, but that
[Bug 13280] New: Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about Mess
[Bug 13280] Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about Mess
[Bug 13426] "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
[Bug 13426] New: "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
[Bug 13427] "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
[Bug 13427] New: "Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" â this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
[Bug 13526] "One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if
[Bug 13526] New: "One distinction we have decided to draw is to prevent downgrading mixed content with websockets (i.e. you cannot connect to a ws:// url from a https:// based context)." -- http://www.ietf.org/mail-archive/web/hybi/current/msg08017.html - specify this if
[Bug 13690] method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
[Bug 13690] New: method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
[Bug 13691] method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
[Bug 13691] New: method setItem(key, value) Why don't you fix a third optional parameter to set the "duration" of the key/value pair. If it is not set the key/value pair will not expire otherwise it will expire as it is set in the 'duration' parameter.
[Bug 13717] New: Clarify that a MessagePort clone, when created, hasn't been transfered, even if it was created as a result of another being transfered. ("If any object is listed in transfer more than once, or any of the Transferable objects listed in transfer have alread
[Bug 13761] New: Now that event data can be discarded (if there is no newline before eof), the last id field value received should be stored in a buffer and set as the EventSource's lastEventId only when the event is actually dispatched. That way the id associated with th
[Bug 13763] New: The WebSocket API should provide a polling mechanism too. Only event based capture messages is not good because if a method in a JS-Class send a message the reply arrive in the event handler. The event handler has no access (if no global var exists) to th
[Bug 13763] The WebSocket API should provide a polling mechanism too. Only event based capture messages is not good because if a method in a JS-Class send a message the reply arrive in the event handler. The event handler has no access (if no global var exists) to th
[Bug 13772] New: Example code should contain a comma instead of semicolon: worker.port.postMessage({ foo: 'structured', bar: ['data', 'also', 'possible']});
[Bug 13777] New: The WebSocket protocol draft (hybi-10) restricts the value of subprotocols as follows: The elements that comprise this value MUST be non- empty strings with characters in the range U+0021 to U+007E not including separator characters as defined
[Bug 13777] The WebSocket protocol draft (hybi-10) restricts the value of subprotocols as follows: The elements that comprise this value MUST be non- empty strings with characters in the range U+0021 to U+007E not including separator characters as defined
[Bug 13786] Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter.
[Bug 13786] New: Drop the charset parameter or made it non-conforming. Other MIME types introduced by this specification do not allow the charset parameter.
[Bug 13792] New: Remove all notes about sharing the connection. It can't work since what's received may depend on the request. It's also not reasonable to buffer every event in case they have to be dispatched again.
[Bug 13792] Remove all notes about sharing the connection. It can't work since what's received may depend on the request. It's also not reasonable to buffer every event in case they have to be dispatched again.
[Bug 13794] New: I think length-prefixed messages would be a lot more useful than line-delimited messages. Sentinel terminators, especially newlines, are more error prone to generate and parse than a few bytes of length prefix followed by a message, repeat. In addition, t
[Bug 13812] New: The EventSource garbage collection does not mention open/error events. It also does not seem to match the language entirely of WebSocket garbage collection.
[Bug 13842] New: One issue that I have noticed is that there is no way to create an EventSource and attach event listeners to it before it connects to the server. This means that there is no way to ensure that no messages are missed between the creation of the EventSourc
[Bug 13842] One issue that I have noticed is that there is no way to create an EventSource and attach event listeners to it before it connects to the server. This means that there is no way to ensure that no messages are missed between the creation of the EventSourc
[Bug 13856] New: I am not sure whether it is due to the nature of this documentation but it would be very helpful to include an example of HTTP response and how it should react to HTTP 3xx and 4xx.
[Bug 13972] New: var bgPage = chrome.extension.getBackgroundPage(); function saveTabData(tab, data) { if (tab.incognito) { bgPage[tab.url] = data; // Persist data ONLY in memory } else { localStorage[tab.url] = data; // OK to store data }
[Bug 14057] In section "The WebSocket interface" when describing the operation of the WebSocket constructor, the following statement is made: "Return a new WebSocket object, and continue these steps in the background (without blocking scripts). ... Establish a WebSoc
[Bug 14057] New: In section "The WebSocket interface" when describing the operation of the WebSocket constructor, the following statement is made: "Return a new WebSocket object, and continue these steps in the background (without blocking scripts). ... Establish a WebSoc
[Bug 14084] New: Hi! Returning a null from getItem() if the key does not exist is downright semantically wrong. null is a full-fledged value which can be serialized (JSONed), and is NOT the value we get if we do: var x = myObject.someUnknownProperty; In that case we get t
[Bug 14086] New: When performing AJAX type queries, they are already asynchronous and already occur in another thread. However, I have found that parsing the XML reply and converting that to a representation usable by the javascript application can result in freezes to t
[Bug 14093] Just to throw out an idea, to allow use of the XML parser, and alert() for debugging, one could implement web workers as simply another open page in the browser, with full access to the DOM, etc, with the ability to communicate to the 'parent' by posting
[Bug 14093] New: Just to throw out an idea, to allow use of the XML parser, and alert() for debugging, one could implement web workers as simply another open page in the browser, with full access to the DOM, etc, with the ability to communicate to the 'parent' by posting
[Bug 14094] New: add example where you listen for and use an event other than 'message'. see <http://www.w3.org/mid/CAA2gsfoQkK1WJu8u_Dm743p4cOPng1OfHM29T7c_1RrpuE95vA@mail.gmail.com>
[Bug 14116] New: Regarding a previous post, a browser could launch itself (CreateProcess() on Windows) again and pass say a port number, a URL, and a boolean flag to the spawned child process. The browser could then be modified to examine it's command line- if there are 3
[Bug 14116] Regarding a previous post, a browser could launch itself (CreateProcess() on Windows) again and pass say a port number, a URL, and a boolean flag to the spawned child process. The browser could then be modified to examine it's command line- if there are 3
[Bug 14120] Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' event dispatching and Opera doen't close it.
[Bug 14120] New: Current spec for EventSource close method doesn't defined behaviour when close called after 'onopen' or 'onmessage'. For example, Google Chrome, closes connection if 'close' called while 'open' method dispatching and Opera doen't close it.
[Bug 14137] Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory.
[Bug 14137] New: Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory.
[Bug 14138] Lastly, to make clear. I am not proposing web workers share the DOM with the main thread. I am proposing the each web worker has it's own INDEPENDENT DOM. (No sharing of memory or DOMs between workers/main thread).
[Bug 14138] New: Lastly, to make clear. I am not proposing web workers share the DOM with the main thread. I am proposing the each web worker has it's own INDEPENDENT DOM. (No sharing of memory or DOMs between workers/main thread).
[Bug 14220] In reply to comment #0) > Every browser that I know of can have two web pages open at once. Those 2 web > pages both have a DOM, they don't share a DOM. Some browsers implement this > as 2 different processes, some as 2 threads. This is where you're m
[Bug 14220] New: In reply to comment #0) > Every browser that I know of can have two web pages open at once. Those 2 web > pages both have a DOM, they don't share a DOM. Some browsers implement this > as 2 different processes, some as 2 threads. This is where you're m
[Bug 14323] New: This API could easily be used by XForms implementations if protocols such as "localstorage://" could also be specified. Thanks! Alain Couthures agenceXML Invited Expert in Forms Work Group
[Bug 14329] New: I believe the possible DoS attack "message flooding" should be addressed i.e. a rogue domain uses "postMessage" to crash an implementation, crash another window etc. Jean-Lou Dupont html5@jldupont.com