RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
Hi. Marcos. -Original Message- From: Marcos Caceres [mailto:w...@marcosc.com] Sent: Friday, November 01, 2013 12:24 AM To: Nilsson, Claes1 Cc: Arthur Barstow; public-webapps; public-sysa...@w3.org Subject: Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC? On Thursday, October 31, 2013 at 3:04 PM, Nilsson, Claes1 wrote: I want to say that we are interested in implementing the JSON manifest and also to discuss additions to the manifest. Content security policies have already been mentioned and we are looking at something similar to http://developer.chrome.com/extensions/contentSecurityPolicy.html, which allows inclusion of content security policies to support secure hosted apps by defining schemes (https:) that are allowed to use for whitelisting secure origins from which scripts should be accepted. This is orthogonal to the manifest, as web apps can already do this. Adding this to the manifest would only be sugar to allow developers to tighten the CSP. I would also like to better understand what a meta tag solution would mean. See: https://developer.apple.com/library/safari/documentation/AppleApplications /Reference/SafariHTMLRef/Articles/MetaTags.html And: https://developers.google.com/chrome/mobile/docs/installtohomescreen So, some standardized thing of the above (without the proprietary prefixes, of course). However, as the manifest specification editor Marcos unfortunately is not able to participate in TPAC I am not sure on the most efficient way to discuss the manifest, a joint SysApps-WebApps session with Marcos calling in or a mailing list discussion. I’m happy to dial in, but would like to know specially what people want to discuss about it. My main point is to stress our interest in the manifest specification and additions to it. I think it’s more important to understand the use cases, and then we can evaluate if the manifest is the appropriate place to address those. I think one of big benefit with manifest format is we can use hyperlink for that. User can install a web app with manifest format, no need to visit a site. So manifest can provide more smooth way of installation to user. They can install apps via links in blogs, twitter, facebook, extra. What do you think? Kr, Wonsuk.
[Bug 23697] New: KeyboardEventInit in UI Events doesn't include keyCode/charCode/which but in D3E, it includes them
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23697
Bug ID: 23697
Summary: KeyboardEventInit in UI Events doesn't include
keyCode/charCode/which but in D3E, it includes them
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: UI Events
Assignee: gary...@google.com
Reporter: masay...@d-toybox.com
QA Contact: public-webapps-bugzi...@w3.org
CC: m...@w3.org, public-webapps@w3.org
UI Event defines:
dictionary KeyboardEventInit : UIEventInit {
DOMString char = ;
DOMString key = ;
DOMString code = ;
unsigned long location = 0;
boolean ctrlKey = false;
boolean shiftKey = false;
boolean altKey = false;
boolean metaKey = false;
boolean repeat = false;
DOMString locale = ;
};
D3E defines:
dictionary KeyboardEventInit {
boolean bubbles = false;
boolean cancelable = false;
AbstractView? view = null;
long detail = 0;
DOMString key = ;
unsigned long location = 0;
boolean ctrlKey = false;
boolean shiftKey = false;
boolean altKey = false;
boolean metaKey = false;
boolean repeat = false;
DOMString locale = ;
unsigned long charCode = 0;
unsigned long keyCode = 0;
unsigned long which = 0;
};
UI Events' definition doesn't include charCode/keyCode/which. However, all
attributes which are legacy should be able to be initialized at constructing
events.
# UI Events still have char, so, I think that UI Events's definition is older
than D3E's.
--
You are receiving this mail because:
You are on the CC list for the bug.
Re: CfC: publish WD of Streams API; deadline Nov 3
EventSources are missing too On 29/10/13 10:22 PM, Aymeric Vitte wrote: I have suggested some additions/changes in my latest reply to the Overlap thread. The list of streams producers/consumers is not final but obviously WebSockets are missing. Who is coordinating each group that should get involved? MediaStream for example should be based on the Stream interface and all related streams proposals. Regards, Aymeric Le 28/10/2013 16:29, Arthur Barstow a écrit : Feras and Takeshi have begun merging their Streams proposal and this is a Call for Consensus to publish a new WD of Streams API using the updated ED as the basis: https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm Please note the Editors may update the ED before the TR is published (but they do not intend to make major changes during the CfC). Agreement to this proposal: a) indicates support for publishing a new WD; and b) does not necessarily indicate support of the contents of the WD. If you have any comments or concerns about this proposal, please reply to this e-mail by November 3 at the latest. Positive response to this CfC is preferred and encouraged and silence will be assumed to mean agreement with the proposal. -Thanks, ArtB
Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
On 10/31/13 8:51 AM, ext Arthur Barstow wrote: (I'm trying to get a sense if this meeting should be canceled or perhaps reduced to 30 mins.) Thanks for the feedback All. At the moment, it appears Manifest is the only topic of mutual interest and that further discussion within SysApps (e.g. UCs), investigation by Macros, discussion on the mail list, etc. is needed before it would be useful to have a joint meeting. As such, I am inclined to cancel the joint meeting. Wonsuk, Mounir - unless I hear otherwise from you, I will cancel the joint meeting (I already reduced the time slot for this topic to 16:00-16:30). -Thanks, ArtB
Re: CfC: publish WD of Streams API; deadline Nov 3
On 10/31/13 11:52 PM, ext Feras Moussa wrote: Agreed. Some of the points listed appear to be things already addressed. Takeshi and I have some feedback on the initial mail, but will wait and provide thoughts on the proposal instead. Looking forward to seeing it. From: tyosh...@google.com Date: Fri, 1 Nov 2013 12:18:47 +0900 To: ann...@annevk.nl CC: dome...@domenicdenicola.com; art.bars...@nokia.com; public-webapps@w3.org Subject: Re: publish WD of Streams API; deadline Nov 3 OK. There seems to be some disconnect, but I'm fine with waiting for Domenic's proposal first. Feras, Takeshi - for the sake of clarity, are you proposing this CfC be stopped? [FWIW, I don't feel strongly either way, although I suspect one could argue that getting some additional exposure and comments could be helpful.] Domenic - Mike Smith mentioned you have worked on a related spec. What is the URL? Also, are you interested and willing to work with Feras and Takeshi on a joint/converged spec in the context of WebApps? -Thanks, AB
[coord] IndieUI WG Request for Inter-Group Coordination at TPAC
On 11/1/13 8:32 AM, ext Arthur Barstow wrote: [ + public-webapps ] Hi Janina, All, I added a 30 minute slot on Monday November 11 from 13:30-14:00 (Shenzhen time). Unless I hear otherwise from you, I will assume this slot is OK and that we will meet in WebApps' meeting room. To help WebApps prepare for the discussion, I think it would be helpful if you would please provide some background information. For example, the URL of the IndieUI User Context specification, the proposal for a new way for user agents to restrict access to certain groups of media resources. -Thanks, Art On 10/31/13 3:39 PM, ext Janina Sajka wrote: Dear Colleagues: The Independent User Interface Working Group (IndieUI) requests approximately 30 minutes of time to meet with CSS and Web Apps (jointly or separately) at TPAC to acquaint your working groups with a new technical approach in IndieUI specifications. The IndieUI User Context specification is moving away from a reliance on a new accessor method for key/value pairs, and toward an extensive reliance on Media Queries (new media features, and matchMedia) as the more appropriate approach for specifying the features we need. To address privacy and fingerprinting concerns, we will also be proposing a new way for user agents to restrict access to certain groups of media features based on user preference. For example, if a site referenced a media feature related to video captions (via matchMedia or @media), the user agent may prompt the user to allow access for the domain. We expect that significant portions of our emerging User Context specification will overlap with work coordinated by the CSS or Web Apps Working Groups. Therefore, we are requesting time with your group at TPAC to acquaint you with our approach and to develop an understanding of how best we can move forward. If possible, we would prefer a morning meeting time in order to more conveniently teleconference our specification editor from North America. Thank you for your consideration. Janina Sajka, IndieUI Chair
Re: [coord] Re: Request for Inter-Group Coordination at TPAC
+ public-webapps On Nov 1, 2013, at 7:44 AM, James Craig jcr...@apple.com wrote: Hi Art. On Nov 1, 2013, at 5:32 AM, Arthur Barstow art.bars...@nokia.com wrote: To help WebApps prepare for the discussion, I think it would be helpful if you would please provide some background information. For example, the URL of the IndieUI User Context specification, the proposal for a new way for user agents to restrict access to certain groups of media resources. The new approach we’re hoping to discuss is pretty new, so these aren’t in spec form yet. I’m hoping to change that before TPAC. The current editor’s draft still has the old key/value pair approach (which we’d decided to scrap), and can be found here: https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html
[Bug 23564] IDL for open() doesn't match implementation reality
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23564 Anne ann...@annevk.nl changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Anne ann...@annevk.nl --- I filed bug 23701 on IDL to remove TreatAsUndefined entirely. I fixed this bug via overloading as suggested: https://github.com/whatwg/xhr/commit/76a4c653ffd0a65e04a52fe2daa9729dbcf64410 -- You are receiving this mail because: You are on the CC list for the bug.
RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
I observe that both the FFOS manifest (https://developer.mozilla.org/en-US/Apps/Developing/Manifest?redirectlocale=en-USredirectslug=Web%2FApps%2FManifest#csp) and the Chrome Extension apps manifest (http://developer.chrome.com/extensions/manifest.html) include CSP definition possibilities. I say +1 to Wonsuk's use cases. Claes -Original Message- From: Wonsuk Lee [mailto:wonsuk11@samsung.com] Sent: den 1 november 2013 07:25 To: 'Marcos Caceres' Cc: 'public-webapps'; public-sysa...@w3.org Subject: RE: [coord] Is there still a need for WebApps + SysApps meeting at TPAC? Hi. Marcos. -Original Message- From: Marcos Caceres [mailto:w...@marcosc.com] Sent: Friday, November 01, 2013 12:24 AM To: Nilsson, Claes1 Cc: Arthur Barstow; public-webapps; public-sysa...@w3.org Subject: Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC? On Thursday, October 31, 2013 at 3:04 PM, Nilsson, Claes1 wrote: I want to say that we are interested in implementing the JSON manifest and also to discuss additions to the manifest. Content security policies have already been mentioned and we are looking at something similar to http://developer.chrome.com/extensions/contentSecurityPolicy.html, which allows inclusion of content security policies to support secure hosted apps by defining schemes (https:) that are allowed to use for whitelisting secure origins from which scripts should be accepted. This is orthogonal to the manifest, as web apps can already do this. Adding this to the manifest would only be sugar to allow developers to tighten the CSP. I would also like to better understand what a meta tag solution would mean. See: https://developer.apple.com/library/safari/documentation/AppleApplicat ions /Reference/SafariHTMLRef/Articles/MetaTags.html And: https://developers.google.com/chrome/mobile/docs/installtohomescreen So, some standardized thing of the above (without the proprietary prefixes, of course). However, as the manifest specification editor Marcos unfortunately is not able to participate in TPAC I am not sure on the most efficient way to discuss the manifest, a joint SysApps-WebApps session with Marcos calling in or a mailing list discussion. I’m happy to dial in, but would like to know specially what people want to discuss about it. My main point is to stress our interest in the manifest specification and additions to it. I think it’s more important to understand the use cases, and then we can evaluate if the manifest is the appropriate place to address those. I think one of big benefit with manifest format is we can use hyperlink for that. User can install a web app with manifest format, no need to visit a site. So manifest can provide more smooth way of installation to user. They can install apps via links in blogs, twitter, facebook, extra. What do you think? Kr, Wonsuk.
[Bug 23704] New: Define username/password better
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23704 Bug ID: 23704 Summary: Define username/password better Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XHR Assignee: ann...@annevk.nl Reporter: ann...@annevk.nl QA Contact: public-webapps-bugzi...@w3.org CC: m...@w3.org, public-webapps@w3.org This requires adding hooks in the URL specification for setting username and password. Because just setting them on the URL directly is wrong. Aside from null we should also ignore the empty string. And ignore password if username is either null or the empty string. -- You are receiving this mail because: You are on the CC list for the bug.
Re: [coord] Re: Request for Inter-Group Coordination at TPAC
Hi Janina, Thanks, let's consider this joint meeting confirmed. WebApps will have Zakim available for its Shenzhen meeting and we will use the #webpps IRC channel. The PIN (9274# / WAPI) and logistics are included in our agenda page http://www.w3.org/wiki/Webapps/November2013Meeting#Meeting_Logistics. If Daniel and/or Peter (or other CSS people) want to join us, they are certainly welcome although it could be a little tight. -Thanks, Art On 11/1/13 11:34 AM, ext Janina Sajka wrote: Thanks, Art. That time will work. Are you able to teleconference in your room? I would like to have James Craig, and possibly also Rich Schwerdtfeger in on our conversation, and neither of them will be physically in Shenzhen. I'll leave it to James Craig to provide an example of what we propose to move toward in our User Context module over the next few days. As he notes in his separate email, this is new thinking for us, just approved this week. I'm certain, though, James can have something for us in time for our meeting. Janina Sajka, IndieUI Chair Arthur Barstow writes: [ + public-webapps ] Hi Janina, All, I added a 30 minute slot on Monday November 11 from 13:30-14:00 (Shenzhen time). Unless I hear otherwise from you, I will assume this slot is OK and that we will meet in WebApps' meeting room. To help WebApps prepare for the discussion, I think it would be helpful if you would please provide some background information. For example, the URL of the IndieUI User Context specification, the proposal for a new way for user agents to restrict access to certain groups of media resources. -Thanks, Art On 10/31/13 3:39 PM, ext Janina Sajka wrote: Dear Colleagues: The Independent User Interface Working Group (IndieUI) requests approximately 30 minutes of time to meet with CSS and Web Apps (jointly or separately) at TPAC to acquaint your working groups with a new technical approach in IndieUI specifications. The IndieUI User Context specification is moving away from a reliance on a new accessor method for key/value pairs, and toward an extensive reliance on Media Queries (new media features, and matchMedia) as the more appropriate approach for specifying the features we need. To address privacy and fingerprinting concerns, we will also be proposing a new way for user agents to restrict access to certain groups of media features based on user preference. For example, if a site referenced a media feature related to video captions (via matchMedia or @media), the user agent may prompt the user to allow access for the domain. We expect that significant portions of our emerging User Context specification will overlap with work coordinated by the CSS or Web Apps Working Groups. Therefore, we are requesting time with your group at TPAC to acquaint you with our approach and to develop an understanding of how best we can move forward. If possible, we would prefer a morning meeting time in order to more conveniently teleconference our specification editor from North America. Thank you for your consideration. Janina Sajka, IndieUI Chair
Re: UNS: Re: [coord] Re: Request for Inter-Group Coordination at TPAC
Thanks, Art. This covers things, I believe. I look forward to seeing you in person in China. Janina Arthur Barstow writes: Hi Janina, Thanks, let's consider this joint meeting confirmed. WebApps will have Zakim available for its Shenzhen meeting and we will use the #webpps IRC channel. The PIN (9274# / WAPI) and logistics are included in our agenda page http://www.w3.org/wiki/Webapps/November2013Meeting#Meeting_Logistics. If Daniel and/or Peter (or other CSS people) want to join us, they are certainly welcome although it could be a little tight. -Thanks, Art On 11/1/13 11:34 AM, ext Janina Sajka wrote: Thanks, Art. That time will work. Are you able to teleconference in your room? I would like to have James Craig, and possibly also Rich Schwerdtfeger in on our conversation, and neither of them will be physically in Shenzhen. I'll leave it to James Craig to provide an example of what we propose to move toward in our User Context module over the next few days. As he notes in his separate email, this is new thinking for us, just approved this week. I'm certain, though, James can have something for us in time for our meeting. Janina Sajka, IndieUI Chair Arthur Barstow writes: [ + public-webapps ] Hi Janina, All, I added a 30 minute slot on Monday November 11 from 13:30-14:00 (Shenzhen time). Unless I hear otherwise from you, I will assume this slot is OK and that we will meet in WebApps' meeting room. To help WebApps prepare for the discussion, I think it would be helpful if you would please provide some background information. For example, the URL of the IndieUI User Context specification, the proposal for a new way for user agents to restrict access to certain groups of media resources. -Thanks, Art On 10/31/13 3:39 PM, ext Janina Sajka wrote: Dear Colleagues: The Independent User Interface Working Group (IndieUI) requests approximately 30 minutes of time to meet with CSS and Web Apps (jointly or separately) at TPAC to acquaint your working groups with a new technical approach in IndieUI specifications. The IndieUI User Context specification is moving away from a reliance on a new accessor method for key/value pairs, and toward an extensive reliance on Media Queries (new media features, and matchMedia) as the more appropriate approach for specifying the features we need. To address privacy and fingerprinting concerns, we will also be proposing a new way for user agents to restrict access to certain groups of media features based on user preference. For example, if a site referenced a media feature related to video captions (via matchMedia or @media), the user agent may prompt the user to allow access for the domain. We expect that significant portions of our emerging User Context specification will overlap with work coordinated by the CSS or Web Apps Working Groups. Therefore, we are requesting time with your group at TPAC to acquaint you with our approach and to develop an understanding of how best we can move forward. If possible, we would prefer a morning meeting time in order to more conveniently teleconference our specification editor from North America. Thank you for your consideration. Janina Sajka, IndieUI Chair -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols Formats http://www.w3.org/wai/pf Indie UIhttp://www.w3.org/WAI/IndieUI/
[Bug 15418] sort out HTTP auth
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15418 Anne ann...@annevk.nl changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #25 from Anne ann...@annevk.nl --- I'm considering this fixed. Follow ups are bug 23704, bug 23706, and bug 21013 it seems. -- You are receiving this mail because: You are on the CC list for the bug.
[Manifest] use cases, was Re: [coord] Is there still a need for WebApps + SysApps meeting at TPAC?
On Friday, November 1, 2013 at 6:25 AM, Wonsuk Lee wrote: Hi. Marcos. I think one of big benefit with manifest format is we can use hyperlink for that. User can install a web app with manifest format, no need to visit a site. So manifest can provide more smooth way of installation to user. They can install apps via links in blogs, twitter, facebook, extra. What do you think? I think that use case is fine, but I think it might also be orthogonal to the manifest. You could also achieve the same thing by declaring in HTML that a link is to an installable application somehow (a@rel=“webapp” or some such). I want to be crystal clear - I’m not saying we don’t need the manifest, I just think that we need to better understand exactly what bits we need. I’m currently undertaking that research and will share it soon so more people can contribute to the discussion. Will likely do that as part of Web Mob [1]. [1] http://www.w3.org/Mobile/IG/
