On Wed, 21 Sep 2011 20:12:17 +0200, Glenn Maynard wrote:
Yuck. I agree that's not a good thing to mimic for the sake of
consistency. Anne, is this intentional, or just something XHR is just
stuck with for compatibility? It looks like a new problem in XHR2--this
couldn't happen in XHR1, be
On Thu, 22 Sep 2011 04:01:40 +0200, Glenn Maynard wrote:
To my reading, a substep is a type of step. The "after finishing..."
sounds like it's saying not to terminate the currently-executing step;
that is, the event dispatch isn't stopped in the middle. Maybe "steps"
vs. "substeps"
are pr
On 9/19/11 1:56 PM, ext Aryeh Gregor wrote:
On Mon, Sep 19, 2011 at 12:48 PM, Arthur Barstow wrote:
Since you are the Chair of the HTML Editing APIs CG [CG], would you please
explain what you see as the relationship between the CG and WebApps
vis-à-vis the Editing spec? In particular, what role
On Tue, Sep 20, 2011 at 6:53 AM, Ian Hickson wrote:
> Why not just improve both navigator.registerContentHandler and
> navigator.registerProtocolHandler?
>
> In particular, why are intents registered via a new HTML element rather
> than an API?
Web Activities addresses this problem space without
http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#document-response-entity-body
says:
"If final MIME type is text/html let document be Document object that
represents the response entity body parsed following the rules set
forth in the HTML specification for an HTML parser with scripting
disabled. [H
On Thu, Sep 22, 2011 at 5:19 AM, Anne van Kesteren wrote:
> I just tried this in FF6, and the behavior is inconsistent. If the TCP
>> connection has been established, then it follows your interpretation, and
>> you get onloadstart, onabort, onloadstart, onloadend, onloadend [1][3].
>> If the T
On 9/20/2011 10:27 AM, Marcos Caceres wrote:
On Tuesday, September 20, 2011 at 7:17 PM, Ian Fette (イアンフェッティ) wrote:
While issuing a ton of patent exclusions for something like this would be
rather poor, I would frankly rather have that then a spec that doesn't get any
attention from a party th
On Thu, Sep 22, 2011 at 7:33 AM, Arthur Barstow wrote:
> It seems to me, that by virtue of using public-webapps, it does give WebApps
> WG a role e.g. to at least comment on the CG's editing spec. [Whether such a
> role is "official" or not is probably just "splitting hairs".]
I absolutely would
I've snipped the transcript to parts relevant to my top-posted discussion.
We already have web components; there are two shimmering examples on the
net right now.
1.
First, there's Canvas. Canvas has a subtree, and at some point earlier
on, it was referred to as the Canvas shadow dom.
In IE
On 9/22/2011 9:43 AM, Aryeh Gregor wrote:
On Thu, Sep 22, 2011 at 7:33 AM, Arthur Barstow wrote:
Is there consensus within the CG to not move the spec to the REC track?
The spec is in the public domain and anyone can theoretically submit
it to the REC track, so consensus isn't an issue either
I just read Anne's update (http://blog.whatwg.org/weekly-xbl-intents)
and realized that while Dominic shared the notes
(http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1513.html),
there wasn't a nice short summary of the discussion published
alongside. I should totally correct that.
There has been discussion in this group now and again about the need for stream
support as part of the File APIs including recently in the threads about
Streaming
Blobs [1] and XHR streaming [2]. I've also had several private conversations
with
members of the WG about the need we see for this kin
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14247
Summary: Add manual conformance tests
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Comp
Thanks for your clarifications Aryeh. One follow-up below re
"contributions" to the Editing spec ...
On 9/22/11 12:43 PM, ext Aryeh Gregor wrote:
On Thu, Sep 22, 2011 at 7:33 AM, Arthur Barstow wrote:
It seems to me, that by virtue of using public-webapps, it does give WebApps
WG a role e.g.
Hi, folks-
In case you don't know, TPAC ("Technical Plenary and Advisory Committee
meeting) is W3C's yearly plenary meeting, where all the different
working groups have a chance to come together, to schedule joint
meetings, to collaborate in person, and to meet as groups. It's a
really produ
On Thu, Sep 22, 2011 at 1:04 PM, Charles Pritchard wrote:
> Does it have to be an either-or situation? Given that there are pressures to
> publish in REC, to have a version which follows various procedures, it seems
> plausible that the two can coexist.
That's true, but there's no rush to create
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14248
Summary: Merge selection spec into editing spec
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14249
Summary: Define some type of selection normalization
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14250
Summary: Conformance tests need to test that the selection is
correct
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
S
On Thu, Sep 22, 2011 at 6:33 AM, Henri Sivonen wrote:
> http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#document-response-entity-body
> says:
> "If final MIME type is text/html let document be Document object that
> represents the response entity body parsed following the rules set
> forth in the
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14251
Summary: Stop allowing non-numeric values for fontSize
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14252
Summary: Put DOM Range to rest
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=14119
Aryeh Gregor changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14251
Aryeh Gregor changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14253
Summary: Add new fontSize variant that accepts pt/px/etc.
instead of legacy values
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NE
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14254
Summary: insertText has to handle things like \r, \0, etc.
sanely
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Sever
On Wed, 21 Sep 2011, Paul Kinlan wrote:
> > On Tue, 20 Sep 2011, Paul Kinlan wrote:
> > >
> > > Q: Why are the verbs URLs?
> > >
> > > Verbs don't have to be URL's but a URL will allow us a point of
> > > reference to documentation, versioning and namespacing allowing
> > > verbs with similar nam
On Thu, Sep 22, 2011 at 2:44 PM, Arthur Barstow wrote:
> It appears you are intentionally using "comments" here to differentiate
> "contributions". Is that right?
Right.
> I ask because, as I understand the CG process: before a person can make a
> contribution to a CG spec, they must agree to a
Hey Ian, comments in-line.
On Thu, Sep 22, 2011 at 2:36 PM, Ian Hickson wrote:
> On Wed, 21 Sep 2011, Paul Kinlan wrote:
> > > On Tue, 20 Sep 2011, Paul Kinlan wrote:
> > > >
> > > > Q: Why are the verbs URLs?
> > > >
> > > > Verbs don't have to be URL's but a URL will allow us a point of
> > >
Jonas,
This is our understanding on how the spec needs to change to support the new
WebIDL exception handling model. We would start by removing all of the
constants from IDBDatabaseException. After that, the only thing left would be
message. Do we still need to have this class definition? I
I've updated the Widget URI scheme spec, and it's now ready for publication as
a new WD.
What's new? I completely rewrote it. Now defines a dereferencing model that
fakes HTTP responses (so hopefully now will work with JQuery mobile + XHR).
New abstract:
The widget URI scheme spec defines th
BlobBuilder.append(text) says:
> Appends the supplied text to the current contents of the BlobBuilder,
writing it as UTF-8, converting newlines as specified in endings.
It doesn't elaborate any further. The conversion from UTF-16 to UTF-8 needs
to be defined, in particular for the edge case of i
On Thu, Sep 22, 2011 at 3:28 PM, James Hawkins wrote:
> When designing the format of the Web Intents action string, we got a lot of
> feedback that the java namespacing is not native to the web and that URLS
> would be a better namespacing scheme. This gave us the added benefit that,
> by setting
> "native" Newlines must be transformed to the default line-ending
representation of the underlying host filesystem. For example, if the
underlying filesystem is FAT32, newlines would be transformed into \r\n
pairs as the text was appended to the state of the BlobBuilder.
This is a bit odd: most p
On 9/22/2011 2:36 PM, Ian Hickson wrote:
On Wed, 21 Sep 2011, Paul Kinlan wrote:
On Tue, 20 Sep 2011, Paul Kinlan wrote:
Q: Why are the verbs URLs?
Verbs don't have to be URL's but a URL will allow us a point of
reference to documentation, versioning and namespacing allowing
verbs with similar
On Thu, Sep 22, 2011 at 5:22 PM, Charles Pritchard wrote:
>> I don't see why. Just have a wiki page that people can list their verbs on
>> and then point to their documentation.
>
> I agree here. The "standard" is sufficient for stewardship.
Why won't I create a bot that fills with wiki with a di
36 matches
Mail list logo
