[Bug 13949] Fantastic geocities.com reference in the section on Cross-directory attacks!

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13949 Anne changed: What|Removed |Added Status|NEW |RESOLVED CC|

Re: [selectors-api] Return an Array instead of a static NodeList

On 30/08/11 4:40 AM, Aryeh Gregor wrote: Oh, right. I misunderstood you. Yes, obviously we wouldn't expose things like .push or .pop on NodeList, since they wouldn't make sense. But we should expose things like .forEach, etc. Any reason not to? I should point out that on platform array obj

[Bug 13967] New: Webkit implementation does not use the second argument 'targetOrigin',

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13967 Summary: Webkit implementation does not use the second argument 'targetOrigin', Product: WebAppsWG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs

Re: Reference to the HTML specification

On Tue, 2011-08-16 at 23:59 +0200, Anne van Kesteren wrote: > On Thu, 04 Aug 2011 17:47:53 +0200, Philippe Le Hegaret wrote: > > Several documents in the WebApps Working Group are linking to HTML, more > > specifically to the WHATWG HTML specification. An example of those is > > Progress Events. T

Re: Some way to change an element's name would be useful

Document.renameNode seems cool. Aside from the awkward user data event, it matches perfectly the needs of the Component Model (updated to reference it here: http://wiki.whatwg.org/wiki/Component_Model#Performance). I am curious why no one had implemented this. We should dust it off, add a normal e

Re: Some way to change an element's name would be useful

On 8/29/11 4:53 PM, Robin Berjon wrote: On Aug 29, 2011, at 21:40 , Boris Zbarsky wrote: On 8/29/11 3:33 PM, Robin Berjon wrote: For completeness, I'm guessing that namespaces would be supported as well? Element renameElement(DOMString newName); Element renameElement(DOMString newNS, DOMString

Re: Some way to change an element's name would be useful

On Aug 29, 2011, at 21:40 , Boris Zbarsky wrote: > On 8/29/11 3:33 PM, Robin Berjon wrote: >> For completeness, I'm guessing that namespaces would be supported as well? >> >> Element renameElement(DOMString newName); >> Element renameElement(DOMString newNS, DOMString newName); > > Shades of http

Re: Some way to change an element's name would be useful

On Mon, Aug 29, 2011 at 4:29 PM, Aryeh Gregor wrote: > On Mon, Aug 29, 2011 at 3:40 PM, Boris Zbarsky wrote: > > Shades of > > http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-renameNode > > That has some good catches I hadn't thought of -- it preserves event > handlers and custom JS at

Re: Some way to change an element's name would be useful

On Mon, Aug 29, 2011 at 3:40 PM, Boris Zbarsky wrote: > Shades of > http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-renameNode That has some good catches I hadn't thought of -- it preserves event handlers and custom JS attributes too.

Re: Some way to change an element's name would be useful

On 8/29/11 3:33 PM, Robin Berjon wrote: For completeness, I'm guessing that namespaces would be supported as well? Element renameElement(DOMString newName); Element renameElement(DOMString newNS, DOMString newName); Shades of http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-renameNod

Re: Some way to change an element's name would be useful

On Aug 29, 2011, at 20:57 , Aryeh Gregor wrote: > We can't actually change the tag name of the node in place, because > then it will have to implement a different interface in general. But > we could have a setTagName() method that creates a new Element with > the given tag name, moves the childre

Some way to change an element's name would be useful

In editing, it's common to want to change an element's name. For instance, document.execCommand("formatblock", false, "h1") will change the current line's wrapper to an . Unbolding should produce . My editing spec defines an algorithm for this

[Bug 13957] New: Remove special handling for WebKit class on blockquote

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13957 Summary: Remove special handling for WebKit class on blockquote Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal

[Bug 13956] New: Port tests to a form usable by browsers

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13956 Summary: Port tests to a form usable by browsers Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority:

[Bug 13955] New: Add more notes!

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13955 Summary: Add more notes! Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: H

[Bug 13954] New: Define DOM mutation operations that automatically check for editability

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13954 Summary: Define DOM mutation operations that automatically check for editability Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW

[Bug 13953] New: Investigate the user-modify CSS property

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13953 Summary: Investigate the user-modify CSS property Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority:

[Bug 13952] New: Specify selection change events

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13952 Summary: Specify selection change events Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2

[Bug 13951] New: Should be able to treat an image with caption as a unit

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13951 Summary: Should be able to treat an image with caption as a unit Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severi

[Bug 13950] New: Specify that links etc. aren't focusable/don't work in editable areas

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13950 Summary: Specify that links etc. aren't focusable/don't work in editable areas Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW

Re: Request for participation in W3C widgets standard

Hi Ronny - to formally participate in the Web Applications WG, your company must first join the W3C and information about that process can be found in [1]. Re W3C widgets, I consider the v1 specs functionally complete with the exception of the Widget Update specs. See [2] for the status of the

Re: how to organize the DOM specs [Was: CfC: publish new WD of DOM Core]

On Fri, Aug 26, 2011 at 12:48 AM, Jonas Sicking wrote: > The point is that if it's just a chapter in a larger spec, how do I > know that there isn't other important information in the larger spec > that I have to read in order to get a understanding of the full > feature. The same applies if it's

[Bug 13949] New: Fantastic geocities.com reference in the section on Cross-directory attacks!

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13949 Summary: Fantastic geocities.com reference in the section on Cross-directory attacks! Product: WebAppsWG Version: unspecified Platform: Other URL: http://www.whatwg.org

Re: [selectors-api] Return an Array instead of a static NodeList

On Thu, Aug 25, 2011 at 7:17 PM, Jonas Sicking wrote: > .push and .pop are generic and work on anything that looks like an > Array. However they don't work on NodeList because NodeList isn't > mutable. > > . . . > > None of these are *mutable* functions. Oh, right. I misunderstood you. Yes, obv

Re: HTTP, websockets, and redirects

Hi Brian, All - I just checked Bugzilla and besides the two editorial type bugs (12510 and 13700), bug 13777 was filed against the Web Sockets API on August 15: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13777 Currently, there have been no followup comments on 13777 and I think it should

Re: [whatwg] window.cipher HTML crypto API draft spec

Hi, all. I proposed *Web Crypto API community group* in http://www.w3.org/community/groups/proposed/ If you're interested in this issue, please join us and let's discuss together. I thinks there are various oppotunites around WebCrypto API[1] or DOMCryptAPI[2] etc. [1] http://html5.creation.net/

Reminder: RfC: LCWD of Progress Events; deadline September 1

On 8/9/11 1:34 PM, ext Arthur Barstow wrote: On August 9, WebApps published LCWD #2 of the Progress Events spec: http://www.w3.org/TR/2011/WD-progress-events-20110809/ The comment deadline is September 1. Please send all comments to: public-webapps@w3.org -AB

Re: CfC: publish LCWD of Server-sent Events spec; deadline August 17

Since this CfC was started, 6 new bugs have been filed against this spec [1]. As such, an LC will not be published until these bugs are addressed. [1] http://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&component=Server-Sent%20Events%20%28editor%3A%20Ian%20Hickson%29&resolution=--- On

Re: CfC: publish LCWD of Web Workers; deadline August 17

Bug 13772 was filed after the CfC started and since it appears to be an editorial bug, I will work towards a LC publication on September 1 with a 3-week review period. Bug 13373 had some discussion after the CfC ended. However, it is currently resolved as WONTFIX and as such will not block the

Re: CfC: publish LCWD of Web Storage; deadline August 17

Given no objections to this CfC and no subsequent bug activity, I will work towards a LC publication on September 1 with a 3-week review period. On 8/10/11 7:33 AM, ext Arthur Barstow wrote: Given Hixie's recent set of bug fixes, the Web Storage spec now has zero bugs. As such, it appears this