http://www.w3.org/Bugs/Public/show_bug.cgi?id=13949
Anne ann...@opera.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
On Mon, Aug 29, 2011 at 9:40 AM, Aryeh Gregor a...@aryeh.name wrote:
On Thu, Aug 25, 2011 at 7:17 PM, Jonas Sicking jo...@sicking.cc 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.
. . .
On Aug 29, 2011, at 23:29 , Dimitri Glazkov wrote:
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
On Aug 30, 2011, at 10:33 AM, Jonas Sicking wrote:
My point was that it was a mistake for querySelectorAll to return a
NodeList. It should have returned an Array. Sounds like people agree
with that then?
I think it’s better to return an immutable object (mutable objects are source
of
On Wed, 24 Aug 2011 21:57:59 +0200, Charles Pritchard ch...@jumis.com
wrote:
On 8/24/2011 1:33 AM, Anne van Kesteren wrote:
Examples of such services would be useful here. (That would still
accept urlencoded files.)
A URL encoded post; that it would use a blob as the source of one of the
On Tue, Aug 30, 2011 at 2:32 AM, Julien Richard-Foy
jul...@richard-foy.fr wrote:
On Aug 30, 2011, at 10:33 AM, Jonas Sicking wrote:
My point was that it was a mistake for querySelectorAll to return a
NodeList. It should have returned an Array. Sounds like people agree
with that then?
I think
On Sat, Aug 27, 2011 at 1:00 AM, Israel Hilerio isra...@microsoft.com wrote:
We looked at the spec to see what it would take to be able to support
multi-column keys on primary keys indexes and we found some inconsistencies
that need to be addressed. Below is our proposal/assumptions on how
On Sat, Aug 27, 2011 at 3:35 AM, Jonas Sicking jo...@sicking.cc wrote:
1. Treat this the same way as inserting the number 2^64-1 into the
object store. I.e. make it impossible to generate more numbers. The
object store will have to be removed and recreated without recreating
the high-valued
I filed a bug against DOM Core:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13971
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13972
Summary: var bgPage = chrome.extension.getBackgroundPage();
function saveTabData(tab, data) { if (tab.incognito) {
bgPage[tab.url] = data; // Persist data ONLY in memory
}
On 30 août 2011, at 18:07, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Aug 30, 2011 at 2:32 AM, Julien Richard-Foy
jul...@richard-foy.fr wrote:
I think it’s better to return an immutable object (mutable objects are
source of programming errors). But this immutable object should have
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13973
Summary: Refactor delete stuff
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13830
Aryeh Gregor a...@aryeh.name changed:
What|Removed |Added
Status|NEW |RESOLVED
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13974
Summary: Allow Selections to be cloned, saved, etc.
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13975
Summary: Get rid of multi-Range Selections
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13976
Summary: Backspacing in between two lists should merge them
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Thanks for the feedback. Answers inline.
Israel
On Tuesday, August 30, 2011 9:10 AM, Hans Wennborg wrote:
On Sat, Aug 27, 2011 at 1:00 AM, Israel Hilerio isra...@microsoft.com
wrote:
We looked at the spec to see what it would take to be able to support
multi-column keys on primary keys
Le 29 août 2011 à 14:57, Aryeh Gregor a écrit :
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 h1. Unbolding b id=foo should
produce span id=foo.
Does that also mean that
On Tue, Aug 30, 2011 at 4:33 AM, Jonas Sicking jo...@sicking.cc wrote:
My point was that it was a mistake for querySelectorAll to return a
NodeList. It should have returned an Array. Sounds like people agree
with that then?
I don't have a problem with that, if it can be changed safely.
On Tue, Aug 30, 2011 at 4:44 PM, Karl Dubost ka...@opera.com wrote:
Le 29 août 2011 à 14:57, Aryeh Gregor a écrit :
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 h1.
On 8/24/2011 11:56 PM, Charles Pritchard wrote:
On 8/24/11 11:36 PM, Jonas Sicking wrote:
On Wed, Aug 24, 2011 at 12:57 PM, Charles Pritchardch...@jumis.com
wrote:
Prpoposed:
FormData output with the x-www-form-urlencoded mime type:
formData.toUrlEncodedBlob(xhr.send)
[Supplemental]
Greetings all,
During the very constructive meeting in
Torontohttp://ehsanakhgari.org/blog/2011-08-31/future-editing-web,
we came to a conclusion that we want events that fire before after user
editing action and execCommand take place. Let us call these events
beforeEditAction and
On Tue, Aug 30, 2011 at 4:08 PM, Darin Adler da...@apple.com wrote:
How would this work with undo?
That's a debatable point. Presumably, we'll be adding undo/redo events as
well so we could not fire before/after edit action events for
execCommand('undo') and execCommand('redo'). I know it's
On Tue, Aug 30, 2011 at 2:25 PM, Aryeh Gregor a...@aryeh.name wrote:
On Tue, Aug 30, 2011 at 4:33 AM, Jonas Sicking jo...@sicking.cc wrote:
My point was that it was a mistake for querySelectorAll to return a
NodeList. It should have returned an Array. Sounds like people agree
with that then?
On Aug 30, 2011, at 4:13 PM, Ryosuke Niwa wrote:
On Tue, Aug 30, 2011 at 4:08 PM, Darin Adler da...@apple.com wrote:
How would this work with undo?
That's a debatable point. Presumably, we'll be adding undo/redo events as
well so we could not fire before/after edit action events for
On Tue, Aug 30, 2011 at 4:34 PM, Darin Adler da...@apple.com wrote:
My question was not about the undo command. I meant that if I implemented a
handler for the aftereditaction event that changed b tags to strong tags,
how would the undo machinery undo what I had done?
Ah, I see. So UA won't
On Tue, Aug 30, 2011 at 3:26 PM, Charles Pritchard ch...@jumis.com wrote:
On 8/24/2011 11:56 PM, Charles Pritchard wrote:
On 8/24/11 11:36 PM, Jonas Sicking wrote:
On Wed, Aug 24, 2011 at 12:57 PM, Charles Pritchardch...@jumis.com
wrote:
Prpoposed:
FormData output with the
On 8/30/11 5:52 PM, Jonas Sicking wrote:
On Tue, Aug 30, 2011 at 3:26 PM, Charles Pritchardch...@jumis.com wrote:
On 8/24/2011 11:56 PM, Charles Pritchard wrote:
On 8/24/11 11:36 PM, Jonas Sicking wrote:
On Wed, Aug 24, 2011 at 12:57 PM, Charles Pritchardch...@jumis.com
On Tue, Aug 30, 2011 at 5:07 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Tue, Aug 30, 2011 at 4:34 PM, Darin Adler da...@apple.com wrote:
My question was not about the undo command. I meant that if I implemented
a handler for the aftereditaction event that changed b tags to strong tags,
how
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8241
Cameron McCormack c...@mcc.id.au changed:
What|Removed |Added
Status|REOPENED|RESOLVED
On 8/14/11 5:36 AM, Anne van Kesteren wrote:
FileList does not follow the requirements from Web IDL:
http://dev.w3.org/2006/webapi/WebIDL/#idl-indexed-properties
Specifically you mean:
1. FileList's WebID definition should show that the getter returns a
nullable type AND
2. Supported
On 8/14/11 5:42 AM, Anne van Kesteren wrote:
Why does the slice() method use [TreatUndefinedAs=EmptyString]? Can it
not just use the normal default handling? Also, if you do indeed want
to use that saying If the contentType parameter is undefined, let
relativeContentType be set to the empty
On 8/14/11 5:45 AM, Anne van Kesteren wrote:
I think we should add a warning to the document that the exceptions
will change. How they change depends on the outcome of the web
platform exceptions discussions.
Done.
http://dev.w3.org/2006/webapi/FileAPI/#ErrorAndException
-- A*
On 8/14/11 5:46 AM, Anne van Kesteren wrote:
Is it too late to change the constants to simple string values?
I think the implementation bird has flown here :(
-- A*
On 8/14/11 5:51 AM, Anne van Kesteren wrote:
The first step says SHOULD but the whole algorithm is a MUST. That
does not work. I also do not see why it is a SHOULD.
The algorithm and the preceding paragraph also seem to have a circular
dependency. Please turn it into a single algorithm
On 8/14/11 5:53 AM, Anne van Kesteren wrote:
It is not clear from the specification when the asynchronous methods
return. This should be stated.
Done.
http://dev.w3.org/2006/webapi/FileAPI/#reading-a-file (and see each read
method definition).
-- A*
On 8/14/11 5:58 AM, Anne van Kesteren wrote:
For the HTML dependency it seems this specification depends on event
handler attributes as well.
The Typed Arrays specification should either become a normal
dependency or you need to introduce different conformance classes.
Currently it is
On 8/14/11 6:00 AM, Anne van Kesteren wrote:
Why can you not use characters legally allowed in IRIs?
You can; they have to be escaped.
The bit on UUID should be turned into a note if it is non-normative
instead of saying it is non-normative.
Done (with an Appendix).
-- A*
Components (see
http://wiki.whatwg.org/wiki/Component_Model_Use_Cases for examples of
what I mean) need to present an API to script. For example, a
contacts component might want to expose a refresh() method that
pulls new contacts from the server. Components also need to hook up
internal behavior
39 matches
Mail list logo
