Le lundi 04 août 2014 à 08:19 -0400, Arthur Barstow a écrit :
Marcos and Mounir, the Editors of WebApps' Screen Orientation API,
consider their spec feature complete with only a few minor [Bugs] open.
As such, we seek wide review on their pre-LC version:
On mar., 2014-02-04 at 17:16 +0900, Jungkee Song wrote:
The TR draft says that the URL of the editors draft is:
https://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html
I believe it is meant to be:
https://dvcs.w3.org/hg/xhr/raw-file/tip/xhr-1/Overview.html
That's right. It's a
Hi,
I've just released the latest iteration of the quarterly overview of W3C
technologies that increase the capabilities of Web apps with special
relevance on mobile:
http://www.w3.org/2014/01/mobile-web-app-state/
This new edition was developed in the Web and Mobile Interest Group,
using a
Hi,
The TR draft says that the URL of the editors draft is:
https://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html
I believe it is meant to be:
https://dvcs.w3.org/hg/xhr/raw-file/tip/xhr-1/Overview.html
It sounds like the group decided to re-use the title XHR Level 1,
while it covers the
Le mardi 08 octobre 2013 à 03:03 -0700, Hallvord R. M. Steen a écrit :
- Original Message -
From: Dominique Hazael-Massieux d...@hazael-massieux.fr
While parsing en-masse some of the IDLs in JavaScript APIs out there, I
stumbled upon an incorrect IDL in
http://dev.w3.org/2006
Hi,
I've just released the latest iteration of my quarterly overview of W3C
technologies that increase the capabilities of Web apps with special
relevance on mobile:
http://www.w3.org/2013/09/mobile-web-app-state/
It highlights in particular the changes over the past 3 months in the
Web platform
Hi,
While parsing en-masse some of the IDLs in JavaScript APIs out there, I
stumbled upon an incorrect IDL in
https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm#error-uris_for_streams
First, the stream API should not redefine the URL interface, but instead
define the additional method
Hi,
While parsing en-masse some of the IDLs in JavaScript APIs out there, I
stumbled upon an incorrect IDL in
http://dev.w3.org/2006/webapi/clipops/clipops.html#dictionary-clipboardeventinit-members
Dictionary members are not declared with the attribute keyword.
So
dictionary
Le mercredi 18 septembre 2013 à 09:53 -0400, Anne van Kesteren a écrit :
On Wed, Sep 18, 2013 at 4:52 AM, Dominique Hazael-Massieux d...@w3.org
wrote:
While parsing en-masse some of the IDLs in JavaScript APIs out there, I
stumbled upon an incorrect IDL in
https://dvcs.w3.org/hg/streams
Hi all,
I've just released another quarterly update to my overview of the
most mobile-relevant Web application technologies:
http://www.w3.org/2013/06/mobile-web-app-state/
In addition to integrating (hopefully) all the relevant changes to the
platform in the past 4 months, it also highlights
Hi all,
I've just released another quaterly update to my overview of the
most mobile-relevant Web application technologies:
http://www.w3.org/2013/02/mobile-web-app-state/
In addition to integrating (hopefully) all the relevant changes to the
platform in the past 3 months, it also highlights
Le mercredi 23 janvier 2013 à 17:31 +0100, Robin Berjon a écrit :
You can find the updated version of idlharness in this branch:
https://github.com/w3c/testharness.js/tree/webidl2
Having tested it out, and to make it easiers for others to do so, once
you have updated your resources
Hi all,
A few days late, but I have just published my quarterly overview of the
most mobile-relevant Web application technologies:
http://www.w3.org/2012/11/mobile-web-app-state/
As always feedback, and even better, contributions to the wiki version
at
Hi all,
The time of my quarterly release of “Standards for Web
Applications on Mobile” has come again; the
August 2012 edition of the document is now available at:
http://www.w3.org/2012/08/mobile-web-app-state/
I have also created a URI where the latest version of that document will
be
Hi,
I spotted a few bugs in the WebIDL fragments of the Input Method Editor
API draft [1]that I'm reporting below. I'm happy to bring the required
changes directly to the draft if that's preferred.
--
interface HTMLElement
…
Object getInputContext ();
};
should be
partial
Hi all,
The time of my quarterly release of “Standards for Web
Applications on Mobile” has come again; the
May 2012 edition of the document is now available at:
http://www.w3.org/2012/05/mobile-web-app-state/
It also incorporates all the changes that have taken place on the
various relevant
Hi,
Back in November, we had a workshop on offline Web applications [1]
which was the trigger for the creation of the Fixing AppCache
community group.
Unfortunately, the workshop Chairs have not been in a position to write
the workshop report; I've now been tasked to do so, and have produced a
Le lundi 19 mars 2012 à 06:58 -0400, Arthur Barstow a écrit :
Cameron has addressed the comments from Web IDL LC#3 [1] and the bug
list only contains two enhancement requests [2]. As such, this is a call
for consensus to publish a Candidate Recommendation of Web IDL using the
following ED
Hi all,
It's been 3 months already since the last update to “Standards for Web
Applications on Mobile”; given that Mobile World Congress is happening
next week, I thought I would release this update a few days ahead of
schedule so that we have a document ready for the congress. So, the
February
Le mercredi 15 février 2012 à 15:08 +0100, Anne van Kesteren a écrit :
On Wed, 15 Feb 2012 14:57:00 +0100, Harald Alvestrand
har...@alvestrand.no wrote:
*This is a call for help from the WEBRTC working group.
We are defining a new API
(http://dev.w3.org/2011/webrtc/editor/webrtc.html)
Le mercredi 07 décembre 2011 à 00:01 +, Marcos Caceres a écrit :
Although I think this document is quite informative, I again would
like to raise objections about lumping app cache and widgets together
for the same reasons I raised last time.
Your last message on the thread last time made
Hi all,
I've just released a new version of “Standards for Web Applications on
Mobile” that takes into account the latest changes in the open Web
platform:
http://www.w3.org/2011/11/mobile-web-app-state.html
Updates since August 2011 [1] includes:
* first drafts from Web RTC, of Geo API v2,
Le jeudi 10 novembre 2011 à 16:27 +0100, Rich Tibbett a écrit :
Hi
a.) to register a URL endpoint as an intent provider the user must visit
a web page (presumably hosted by the target device itself) and capture
the intent registration from that page before that intent provider can
be used
Le samedi 17 septembre 2011 à 10:30 +0100, Marcos Caceres a écrit :
shortcut: if you want to (incorrectly, IMO) continue to lump widgets
and app cache, then do so making it clear that this is just one of the
use cases for widgets and certainly NOT the primary use case…
My document focuses on
Hi Marcos,
Le samedi 03 septembre 2011 à 22:47 +0200, Marcos Caceres a écrit :
[sorry for the delay in responding]
Thank you for continuing to keep the document up to date. This document is
very helpful.
Thanks!
I have request: can you please ungroup Widgets and HTML's
ApplicationCache?
Le vendredi 16 septembre 2011 à 21:36 +0700, Marcos Caceres a écrit :
I think they are actually not so different, and share many use cases.
Ok, I strongly object in the strongest of terms to them being put together
and I'm more than happy to debate any argument you might have for lumping
Hi all,
I've just released a new version of “Standards for Web Applications on
Mobile” that takes into account the latest changes in the open Web
platform:
http://www.w3.org/2011/08/mobile-web-app-state.html
Updates since May 2011 [1] includes:
* Addition of a new section on technologies useful
Hello Andres,
The Battery Status API is deliverable of the Device APIs Working Group,
so I'm copying the group's list public-device-a...@w3.org.
(keeping public-webapps in BCC FYI)
Dom
Le dimanche 05 juin 2011 à 22:44 -0700, Andres Riofrio a écrit :
I have some comments on the Battery Status
Le lundi 06 juin 2011 à 08:55 -0400, Arthur Barstow a écrit :
The last publication of the File API spec [ED] was last October so it
would be good to publish a new Working Draft in w3.org/TR/.
Since Tracker shows 0 bugs for the spec [Tracker] and the ED does not
appear to identify any open
Hi,
There was discussion some time ago about specifying a URL interface,
based I think on the draft proposal at
https://docs.google.com/document/edit?id=1r_VTFKApVOaNIkocrg0z-t7lZgzisTuGTXkdzAk4gLUhl=enpli=1
Is this something that the Web Apps Working Group is planning to work
on? If not, does
Hi,
Back in February, I announced here a first release of a document
compiling all the technologies that I had identified as relevant to the
development of Web applications on mobile devices:
http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0650.html
I have just released an updated
Le vendredi 13 mai 2011 à 12:19 -0400, Arthur Barstow a écrit :
Thanks for creating this Dom (FYI, I made some edits and updates yesterday).
Thanks! As you may have seen, I've just released a new version of that
document which includes your updates
Le jeudi 24 février 2011 à 16:03 +0100, Dominique Hazael-Massieux a
écrit :
As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly relevant
Hi,
The WebIDL declaration under The WebSocket interface in
http://dev.w3.org/html5/websockets/ has a minor bug. It doesn't use the
proper syntax for extended attributes: it does [A][B] where the WebIDL
grammar is [A,B] in
[Constructor(in DOMString url, in optional DOMString protocols)]
Hi Charles,
Le mardi 08 mars 2011 à 21:14 -0800, Charles Pritchard a écrit :
InkML is a development relevant to mobile Web.
Tablets and other input-rich devices are gaining in acceptance (and
becoming easier to purchase).
InkML is one of the few specs to put forward both a stream-based and
Hi Ben,
Le vendredi 25 février 2011 à 14:04 +, Ben Laurie a écrit :
As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly relevant
(trimming CC)
Hi Somnath,
Le samedi 26 février 2011 à 12:45 +0530, Somnath Chandra a écrit :
This document is an excellent document. It gives present state-of-the
art and roadmap ahead for development of Mobile Web.
Implementation of Mobile Web with South Asian complex scripts is a
Hi Paul,
Le vendredi 25 février 2011 à 16:53 +0100, Paul Libbrecht a écrit :
I definitely agree this is a useful deliverable; I wish more EU
projects be as careful in their survey as that!
Thanks!
I was looking to see if MathML was mentioned (I think it should as a
future technology but it
(bcc to public-html and public-device-apis; please follow-up on
public-webapps)
Hi,
As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly
Hi Marcos,
Le mardi 15 février 2011 à 13:19 +0100, Marcos Caceres a écrit :
Can we please get a full rundown of the systems available on test
server. Can we also have all the details about getting access to the
server, etc.
Here is what I know off the top of my head:
* the content on
-a...@w3.org) or to the Chairs and Staff Contacts
(ro...@berjon.com, t...@w3.org, d...@w3.org, frederick.hir...@nokia.com).
Thanks,
Dominique Hazael-Massieux, Staff Contact of the Device APIs and Policy
Working Group
1. http://www.w3.org/2009/05/DeviceAPICharter
Hello WebApps WG,
The Device APIs and Policy Working Group has published a new draft
called HTML Media Capture on which we think we'll need to coordinate
with your group:
http://www.w3.org/TR/2010/WD-html-media-capture-20100720/
That document defines a mechanism to bind an input type=file with a
Le mercredi 02 juin 2010 à 13:40 +0200, Florian Stegmaier a écrit :
My overall question is, if you have any experience with WebIDL parser,
or perhaps could point me to a project, which is most up-to-date to
the current version of the WebIDL specification? I have also tried to
validate
Hi,
Glancing quickly at the editors draft of
http://dev.w3.org/2006/webapi/WebSimpleDB/ and with help from the WebIDL
checker, I've found the following problems:
* none of the interfaces/exceptions are marked with the extended
attribute [NoInterfaceObject] — I doubt they are all meant to be
Le lundi 12 avril 2010 à 17:47 +, Ian Hickson a écrit :
Server sent events doesn't require any change to the network, it's
compatible with almost any setup that uses HTTP today. Web Sockets
requires that intermediaries support full-duplex connections. Server sent
events is compatible
Hi,
Given the overlap I perceive between Server Sent Events and the Web
Sockets spec, I would be interested to know what role Server Sent Events
fills that Web Sockets doesn't.
I understand that Server Sent Events allow for unidirectional
communication with the server, while Web sockets is
Le jeudi 04 mars 2010 à 17:03 +0100, Robin Berjon a écrit :
Good suggestion, the latest ED reflects the above change plus another
reference where subdomains are defined.
Please let us know if that works for you!
It does, thanks!
Dom
Le jeudi 04 mars 2010 à 15:51 +0100, Robin Berjon a écrit :
On Dec 10, 2009, at 16:51 , Dominique Hazael-Massieux wrote:
A quick comment after re-reading WARP at the invitation of Robin to DAP
[1]: I don’t think the notion of subdomain is well-defined; is w3.org a
subdomain of .org? is co
Hi Art, Marcos,
Le jeudi 11 février 2010 à 13:00 -0500, Arthur Barstow a écrit :
During the 4-Feb-2010 widgets voice conference, we discussed how to
test WebApps' WARP spec [WARP] and Marcos raised concerns about how
to test the spec given it requires at least two domains to test
Le lundi 15 février 2010 à 12:46 +0100, Marcos Caceres a écrit :
During the 4-Feb-2010 widgets voice conference, we discussed how to
test WebApps' WARP spec [WARP] and Marcos raised concerns about
how
to test the spec given it requires at least two domains to test
against since the test
Hi,
http://www.w3.org/TR/2009/CR-widgets-apis-20091222/#the-widget-interface
currently declares the Widget interface without extended attributes.
I believe it is not the goal of the specification to expose the
interface itself in the global namespace, so I think it should be marked
with a
Le jeudi 19 novembre 2009 à 22:39 +1300, Robert O'Callahan a écrit :
The abstraction of the security concerns within a policy may
allow delegation of the security to some third parties.
There are usually no third parties to delegate to.
That’s true to a certain extent, but a
Hi,
My understanding is that the File Upload spec is now superseded by the
File API spec, but
http://www.w3.org/TR/file-upload/ doesn't redirect to
http://www.w3.org/TR/FileAPI/
I guess ideally the latter would have used the former has previous
version, but since it’s too late for that, I think
Le mardi 17 novembre 2009 à 12:01 -0500, Arthur Barstow a écrit :
And test suite files are now online [2].
[[ ++ MWTS WG ]]
[2] http://dev.w3.org/2006/waf/widgets-api/test-suite/
To be fair, that work only represents Marcos’s efforts so far — I did
contribute some test cases, but they
Le vendredi 13 novembre 2009 à 02:28 -0800, Arun Ranganathan a écrit :
Discussion about renaming shows that there isn't really consensus about
a name change [1][2], so I haven't proceeded with one. I'd rather
proceed without a name change for now, but work towards evolving file
write
Le mardi 10 novembre 2009 à 17:47 -0800, Maciej Stachowiak a écrit :
I would be concerned with leaving file writing to DAP, because a
widely held view in DAP seems to be that security can be ignored while
designing APIs and added back later with an external policy file
mechanism.
it.
Dom
Le mercredi 28 octobre 2009 à 22:43 +0100, Dominique Hazael-Massieux a
écrit :
Using wttjs [1], I have generated a bunch of low-level test cases for
the Widgets Interface spec, based on its WebIDL, and uploaded them to:
http://dev.w3.org/2006/waf/widgets-api/tests/idl-gen/
Since I
Le jeudi 12 novembre 2009 à 17:35 +0100, Marcos Caceres a écrit :
On the other hand, automated test generation can generate a large number
of test cases and is less prone to human errors. But, at the same time,
it cannot test some things that are written in the prose. For example, a
AU must
Le jeudi 12 novembre 2009 à 17:52 +0100, Marcos Caceres a écrit :
I complete agree that manual tests bring a lot of value, but I think it
would be unwise to refuse automated tests that express exactly what the
spec expresses — in particular, they can be extremely useful to detect
bugs in
Hi,
I alluded to this during the joint F2F meeting between WebApps and DAP
last week, but thought I would make the proposal more formally: given
that the current “File API” [1] really defines a FileReader interface,
and given that DAP is supposed to come up with a more generic
filesystems API
Le mardi 10 novembre 2009 à 02:27 -0800, Maciej Stachowiak a écrit :
At TPAC, I recall that we proposed drawing the line between file
reading/writing on the one hand (presumably to go in the current File
API spec) and filesystem access (including messing with directories,
mountpoints,
Le mardi 03 novembre 2009 à 21:27 -0800, Arthur Barstow a écrit :
This is a Call for Consensus (CfC) to publish the First Public
Working Draft (FPWD) of the File API spec, latest Editor's Draft at:
http://dev.w3.org/2006/webapi/FileAPI/
My understanding is that the FPWD would have a
Le lundi 09 novembre 2009 à 20:08 +, Ian Hickson a écrit :
Some use cases:
[…]
* Ability to write a Web-based photo management application that handles
the user's photos on the user's computer
* Ability to expose audio files to native media players
* Ability to write a Web-based media
Hi,
WARP requires normalization of IRI using ToASCII only for HTTP and HTTPS
uris — is there any reason for that?
Dom
Le lundi 26 octobre 2009 à 05:24 -0700, Arun Ranganathan a écrit :
The latest revision of the FileAPI editor's draft is available here:
http://dev.w3.org/2006/webapi/FileAPI/
The WebIDL checker identifies a couple of simple bugs in the draft:
Hi,
Using wttjs [1], I have generated a bunch of low-level test cases for
the Widgets Interface spec, based on its WebIDL, and uploaded them to:
http://dev.w3.org/2006/waf/widgets-api/tests/idl-gen/
Since I don’t have a widgets engine that would implement the spec, I
haven’t been able to check
(adding the Device APIs Working Group mailing list in CC:)
Hi John, Web Apps
Le lundi 19 octobre 2009 à 14:12 -0700, John Gregg a écrit :
Apologies for the delay, I've been spending the majority of my time
completing the initial implementation for Chrome, but I've posted a
draft version of a
Le jeudi 01 octobre 2009 à 06:41 -0400, Arthur Barstow a écrit :
Give the July CR says it will not end until November 1, it would seem
a bit strange if we published a new LC before then.
Actually, the end of CR period really means the document won't go to PR
before then - I don't think there
Hi Marcos,
As Kai alluded to in his report [1], we had a chance to look at Widgets
Digital Signature last week to see what would be required to create test
cases for that specification.
As part of that exploratory work, we started two documents similar to
the ones that were developed for PC:
*
Le mardi 29 septembre 2009 à 18:18 +0200, Marcos Caceres a écrit :
Given that the Widget test suite event did not create tests for
conformance checker (CC) related assertions, I have moved all
conformance checker assertions from the PC Test Suite edition to a
new document [1].
FWIW, we chose
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest renaming it in urlpattern or just pattern (unless there are
already many implementations that rely on that attribute name).
There may be lessons to be
Hello WebApps Working Group,
A growing number of groups is relying on WebIDL to define their APIs,
including the Device APIs and Policy Working Group (cc'd).
As some of the said specs are likely to reach PR in the upcoming months
(e.g. Geolocation?), their normative dependence on WebIDL risk to
Hi Marcos,
Le jeudi 20 août 2009 à 15:30 +0200, Marcos Caceres a écrit :
I've now moved (and updated) all the PC test suite documentation. It
can now be found here:
http://dev.w3.org/2006/waf/widgets/tests/
It would be great to get the MWTS blessing that we have prepared the
Le vendredi 31 juillet 2009 à 18:01 +0200, Marcos Caceres a écrit :
I've created the first draft of the test suite edition, it is
available here (it's ugly on purpose, I will remove the ugly
stylesheet soon):
http://dev.w3.org/2006/waf/widgets/Overview_TSE.html
Includes stable IDs on p's,
Hello all,
Le lundi 13 juillet 2009 à 11:57 +0200, Breitschwerdt, Christian,
VF-Group a écrit :
More information regarding registration, etc to follow shortly via W3C
staff/WG chairs.
If you are interested in attending that event, please register at:
Le mercredi 08 juillet 2009 à 15:20 +0200, Marcos Caceres a écrit :
I'm mostly satisfied, but see a few comments below.
I'm now satisfied, thanks.
Dom
Le mardi 07 juillet 2009 à 19:53 +0200, Marcos Caceres a écrit :
For the sake of the Disposition of Comments, please let us know if you
are satisfied with the fixes below (if possible, by the 9th of July).
I'm mostly satisfied, but see a few comments below.
On Fri, Jun 12, 2009 at 6:35 PM,
Le dimanche 05 juillet 2009 à 18:50 +0200, Marcin Hanclik a écrit :
Just FYI I created a tool to check the BONDI specs under:
http://bondi01.obe.access-company.com/
It automatically checks each new release of the BONDI specs directly from the
SVN repository.
Very nice! Would it be possible
Le mardi 07 juillet 2009 à 20:11 +0200, Marcos Caceres a écrit :
Responses inline...
As before, for the sake of the Disposition of Comments, please let us
know if you are satisfied with the responses below.
I'm satisfied, thanks.
Dom
Le mardi 30 juin 2009 à 06:26 +, Ian Hickson a écrit :
However, I do think it'd be nice to have tools to help us check the IDL..
Could we have a tool that just scans the textContent out of pre elements
with class=idl, or something? We could give it the URLs of all the specs
being
Hi,
Francois Daoust and I played with creating a widget checker tool that
implements some of the conformance checker requirements of the widgets
PC spec.
The said tool can be experimented with at:
http://qa-dev.w3.org:8001/widget/ (an uncool URI that is likely to break
in the future)
but please
Hi,
I wrote a simple XSLT to extract the conformance requirements from the
Widgets spec [1], with the following output:
http://www.w3.org/2005/08/online_xslt/xslt?xslfile=http%3A%2F%
2Fdev.w3.org%2F2006%2Fwaf%2Fwidgets%2Ftests%
2FextractTestAssertions.xslxmlfile=http%3A%2F%2Fcgi.w3.org%2Fcgi-bin%
Hi,
5.3 Zip Relative Paths has the following bugs:
* the ABNF for zip-rel-path uses localized-folder, but only
locale-folder is defined
* the third rule for the conformance checker should be:
A CC must inform the author of any Zip relative paths whose length
exceed 120 characters (rather than
Hi Art, Charles,
As was discussed during the WebApps WG F2F in Cannes, the Mobile Web
Test Suites Working Group (and in particular, Kai Hendry) has started to
work on developing test cases for the Widgets Packaging and
Configuration specification:
Applications Working Group
* Geolocation Working Group
* Ubiquitous Web Applications Working Group
* HTML Working Group
* Web Security Context Working Group
Should you have any question, please contact Dominique Hazael-Massieux
[EMAIL PROTECTED].
Regards,
Dom
Hello WebApps WG,
The Mobile Web Best Practices Working Group is interested to know
whether XmlHTTPRequest has any actual or planned support for compression
- I looked quickly in the specs and issues list, but didn't find
anything relevant.
Thanks,
Dom
Le mardi 09 septembre 2008 à 09:02 -0400, Boris Zbarsky a écrit :
HTTP has Content-Encoding and Transfer-Encoding, no? No special effort
on the part of XMLHttpRequest is needed to make use of those, as long as
the underlying HTTP implementation supports them.
Well, at least when an
Le mardi 09 septembre 2008 à 17:37 +0200, Anne van Kesteren a écrit :
On Tue, 09 Sep 2008 17:29:03 +0200, Dominique Hazael-Massieux [EMAIL
PROTECTED]
wrote:
I'm sure it could, but if one implementation does it and another
doesn't, this leads to interoperability problems - hence
88 matches
Mail list logo
