[Bug 23422] New: Adding a method to deliver editing-related events to a DOM element
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23422 Bug ID: 23422 Summary: Adding a method to deliver editing-related events to a DOM element Product: WebAppsWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: IME API Assignee: ko...@google.com Reporter: ko...@google.com QA Contact: public-webapps-bugzi...@w3.org CC: m...@w3.org, public-webapps@w3.org In the current IME API WD (http://www.w3.org/TR/2013/WD-ime-api-20130815/ , section 8.2) using HTML5 'inputmode' attribute to specify that an element wants editing related events (such as input, beforeinput, composition events) but it sounded somewhat weird way to tell the hosting user agent in this way. Instead, we propose to add a method to InputMethodContext, as bool requestEventDelivery(); to tell the target element wanting editing events delivered when it gets focus, if the target element is a non-editable one (i.e. not input, textarea, or contenteditable). By using this a developer can turn a DOM element to behave like an editing element, to construct a DOM-based text editor. If the user agent cannot fulfill the request, it can return false to indicate that the request is failed. We also might want to introduce another interface to undo the request: void refuseEventDelivery(); which should always succeed (as not delivering events is the default). -- You are receiving this mail because: You are on the CC list for the bug.
Re: blob URIs and the query string
On Tue, Oct 1, 2013 at 9:33 PM, Kyle Huey m...@kylehuey.com wrote: The File API specifies how to deal with fragment identifiers. It should also specify what to do with the query string. Presumably it should be ignored when looking up blob URIs. This is also what http://fetch.spec.whatwg.org/#basic-fetch suggests we converge on for about URLs. For data URLs we concatenate URL's scheme data and URL's query together (separated by ?'). Matching about URLs here makes the most sense to me. -- http://annevankesteren.nl/
Re: [webcomponents]: Shadow trees styling issue
04.09.2013, 22:19, Dimitri Glazkov dglaz...@chromium.org: On Sun, Sep 1, 2013 at 9:42 AM, Alexey Kuzmin ale...@alexeykuzmin.com wrote: Hello! As I understand current spec [1] there is only two ways to provide styles for DOM elements in shadow trees: 1) add styles to document and set apply-author-styles flag for shadow tree or 2) use inline styles for elements under the shadow root. But both of them look not very useful for Custom Elements [2] creation. The first option clearly is not the best pick since the apply-author-styles flag will cause document styles to affect shadow tree elements and it might lead to undesired results. The second one is more suitable but also has some disadvantages. The main one is that CSP of the page might forbid inline styling, styles will not be applied to shadow tree elements and the whole custom element might become unusable. My question is – is there the way to avoid these issues with current spec? And if not, will it make sense to allow link[rel=stylesheet] element to be shadow root child? Could we maybe we relax CSP to allow style in shadow trees? :DG Have you had a chance to look into this issue? Allowing style element in shadow trees would really help. -- Alexey
[admin] Spec status and plans ...
Hi All, During WebApps' f2f meetings, we typically review each spec in [PubStatus] to determine if the specs' data is accurate, as well as to identify any general issues about each spec. I think this has been useful to help get us on the same page as well as to help set expectations such as providing accurate information for each spec's Plans. Since the registrant list for the November 11-12 meeting is relatively low and several spec Editors are not registered, I am going to use e-mail to `simulate` this review. I'll send separate e-mails for the specs and group them if/when it makes sense (f.ex. Web Components). A few specs have a relatively clear status (f.ex. File API is now in LC, CORS is on track for PR, Web IDL tests are being reviewed) so I will not request information for those specs. Although WebApps does not enforce the so-called heartbeat publication of Working Drafts, if your spec has not been published recently (say in 2013), it probably should be published, especially if the spec has changed, is now feature complete, is getting implemented, etc. Editors - I would appreciate it if you would please reply to your spec's specific request for status and plans and I apologize in advance if that data is already clear or `well known`. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[websockets] Seeking Interop Test Suite status and plans
Hi Kris, Adrian, Ken, If any of the testing-related data for the Web Sockets spec in [PubStatus] is not accurate, please provide corrections. Also, please provide a short update re plans for CR interop testing (Draft implementation report is http://www.w3.org/wiki/Webapps/Interop/WebSockets). -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[streams-api] Seeking status and plans
Hi Feras, If any of the data for the Streams API spec in [PubStatus] is not accurate, please provide corrections. Also, please see the following thread and let us know your plan for this spec http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0599.html. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[webmessaging] Seeking Interop Test Suite status and plans
Hi Alex, Kris, Adrian, If any of the testing-related data for the Web Messaging spec in [PubStatus] is not accurate, please provide corrections. Also, please provide a short update re plans for CR interop testing (Draft implementation report is http://www.w3.org/wiki/Webapps/Interop/WebMessaging). -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[D3E] Seeking status and plan
Hi Travis and Gary, If any of the data for D3E in [PubStatus] is not accurate, please provide corrections. Also, please provide a short update re the plan and time-frame to publish a new LCWD. [Hint: it would be really nice to get a new LCWD of D3E published as soon as possible ;-)] -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[pointerlock] Seeking status and plans
Hi Vincent, If any of the data for the Pointer Lock spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 29-May-2012 - or the spec's status with respect to being feature complete, implementation status, etc. please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[selectors-api2] Seeking status and plans
Hi Lachlan, If any of the data for the Selectors API v2 spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 28-June-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[ime-api] Seeking status and plans
Hi Takayoshi and Kenji, If any of the data for the IME spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec, or the spec's status with respect to being feature complete, implementation status, etc. please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[uievents] Seeking status and plans
Hi Gary, Travis, If any of the data for the UI Events spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 25-July-2013 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[progress-events] Seeking Interop Test Suite status and plans
Hi Jungkee, If any of the testing-related data for Progress Events in [PubStatus] is not accurate, please provide corrections. Also, I would appreciate it, if you would please provide a short update re the status and plan for CR Implementation Report http://www.w3.org/wiki/Webapps/Interop/ProgressEvents. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[fullscreen] Seeking status and plans
Hi Tantek, If any of the data for Fullscreen in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 6-July-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[quota-api] Seeking status and plans
Hi Kinuko, If any of the data for the Quota Management API spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 03-July-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[push-api] Seeking status and plans
Hi Bryan, Eduardo, If any of the data for the Push API spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec, the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[screen-orientation] Seeking status and plans
Hi Mounir, If any of the data for the Screen Orientation API in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 06-Dec-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[eventsource] Seeking Interop Test Suite status and plans
Hi Tina, If any of the test-related data for the Server-Sent Events spec in [PubStatus] is not accurate, please provide corrections. Also, I would appreciate it, if you would please provide a short update re the status and plans for the CR Implementation Report http://www.w3.org/wiki/Webapps/Interop/ServerSentEvents. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[webcomponents] Seeking status and plans
Hi Dimitri, If any of the data for the four Web Components documents (including the `Explainer`) in [PubStatus] is not accurate, please provide corrections. Also, for each of these documents, please provide a short summary re your plans for the spec, f.ex. the spec's status with respect to being feature complete, implementation status, etc. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[IndexedDB] Seeking Interop Test Suite status and plans
Hi Jonas, Joshua, Eliot and Alex, If any of the test-related data for Indexed Database API in [PubStatus] is not accurate, please provide corrections. Also, what is the plan - f.ex. Who is going to do What and by When - for: 1) reviewing test submissions; 2) completing the test suite; and 3) doing interop testing? -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[workers] Seeking Interop Test Suite status and plans
Hi Simon, Odin, If any of the testing-related data for the Web Workers spec in [PubStatus] is not accurate, please provide corrections. Also, please provide a short update re plans for CR interop testing. As I understand it, several workers tests have been reviewed and approved [Tests] but there might be some gaps so any info you have re the gaps would be helpful. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus [Tests] http://w3c-test.org/web-platform-tests/master/workers/
[file-{writer,system}-api] Seeking status and plans
Hi Eric, If any of the data for your two File APIs in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for these specs (last published 17-Apr-2012), or the specs' status with respect to being feature complete, please let us know. All - besides Chrome, if there are other implementations of these specs, please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[gamepad] Seeking status and plans
Hi Ted, Scott, If any of the data for the Gamepad spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 29-May-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[clipboard-apis] Seeking status and plans
Hi Hallvord, If any of the data for Clipboard APIs and Events in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec, the spec's status with respect to being feature complete, implementation status, please let us know. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
[xhr] Seeking status and plans
Hi Hallvord, Julian and Jungkee, If any of the data for the XHR spec in [PubStatus] is not accurate, please provide corrections. I am also interested in the status and plans for both the version of XHR that is supposed to move to LC-CR-REC in 2013 and the XHR-Bleeding-Edge version. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus
Re: [fullscreen] Seeking status and plans
On Wed, Oct 2, 2013 at 12:29 PM, Arthur Barstow art.bars...@nokia.com wrote: If any of the data for Fullscreen in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 6-July-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus I wrote all the text in http://fullscreen.spec.whatwg.org/ on which http://www.w3.org/TR/fullscreen/ appears to be based (although woefully out of date). Given the W3C's explicit stance on forking, I think would be hypocritical for your group to continue publishing this fork. -- http://annevankesteren.nl/
Re: [xhr] Seeking status and plans
On Wed, Oct 2, 2013 at 12:39 PM, Arthur Barstow art.bars...@nokia.com wrote: If any of the data for the XHR spec in [PubStatus] is not accurate, please provide corrections. I am also interested in the status and plans for both the version of XHR that is supposed to move to LC-CR-REC in 2013 and the XHR-Bleeding-Edge version. [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus I have the same concerns here as with Fullscreen. Given the W3C's stance on forking, it makes no sense to continue to publish this. -- http://annevankesteren.nl/
Re: [XHR] Content-Length header for data: URLs
On Fri, Sep 20, 2013 at 5:09 AM, Simon Pieters sim...@opera.com wrote: On Fri, 20 Sep 2013 05:24:26 +0200, Jonas Sicking jo...@sicking.cc wrote: I would hardly call taking the length subtracting any characters before the , and applying a multiplier parsing. You don't have to look at any characters after the , at all. Just applying a multiplying doesn't take percent-escaping into account, though. Right. I guess you can still count that relatively easily, but it's not super straightforward and it's not clear what the benefit of exposing Content-Length is. -- http://annevankesteren.nl/
Re: [webcomponents] Seeking status and plans
Sure thing, Art! * Introduction to Web Components (http://www.w3.org/TR/components-intro/) status should be WD, next working draft coming out shortly, adjusting for changes in the underlying specs. Dominic Cooney (domin...@chromium.org) is the primary editor of this document. * Custom Elements (http://www.w3.org/TR/custom-elements/) is getting pretty close to pre-LC soliciting public review. There's been work on tests, but nothing to show for yet. We've been focusing on getting the basics right. * Shadow DOM (http://www.w3.org/TR/shadow-dom/) is undergoing heavy refactoring to align closer to DOM Core terminology and straighten up concepts, learning from experience. Hayato Ito (hay...@chromium.org) has been driving this work and is now the spec's primary editor. I would like to suggest Yuta Kitamura (yu...@chromium.org) as test facilitator, since he's the one who spent most of the time reviewing and improving the existing test suite. The ETA of the next WD is end of year. * HTML Imports (http://www.w3.org/TR/html-imports/) is getting close to the next WD. Hajime Morrita has been working on that spec, and I would like to put him down as the primary editor. At some point, we need to look at these specs and consider whether they should remain independent normative dcuments or be incorporated into existing ones like HTML or DOM. For example, HTML Imports is mostly a monkeypatch for HTML spec. But this discussion hasn't started yet. :DG On Wed, Oct 2, 2013 at 9:34 AM, Arthur Barstow art.bars...@nokia.comwrote: Hi Dimitri, If any of the data for the four Web Components documents (including the `Explainer`) in [PubStatus] is not accurate, please provide corrections. Also, for each of these documents, please provide a short summary re your plans for the spec, f.ex. the spec's status with respect to being feature complete, implementation status, etc. -Thanks, ArtB [PubStatus] http://www.w3.org/2008/**webapps/wiki/PubStatushttp://www.w3.org/2008/webapps/wiki/PubStatus
Re: [file-{writer,system}-api] Seeking status and plans
On Oct 2, 2013, at 12:29 PM, Arthur Barstow wrote: Hi Eric, If any of the data for your two File APIs in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for these specs (last published 17-Apr-2012), or the specs' status with respect to being feature complete, please let us know. All - besides Chrome, if there are other implementations of these specs, please let us know. -Thanks, ArtB I've created a draft of the FileSystem API in GitHub, based on discussions with w3-staff: https://github.com/w3c/filesystem-api This API is different than the Google FileSystem API proposal, athough it will refine the concept of the filesystem: scheme, initially proposed by Google. -- A*
Re: [selectors-api2] Seeking status and plans
On 2013-10-02 18:31, Arthur Barstow wrote: If any of the data for the Selectors API v2 spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 28-June-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. The features from selectors API 2 are being integrated into DOM, with some design changes from the last selectors api spec. I don't forsee any future edits to the selectors api 2 specification itself. If you like, we can re-publish it as a NOTE, and get a draft of DOM that includes selectors api features published. -- Lachlan Hunt http://lachy.id.au/
Re: [webcomponents] Seeking status and plans
Thanks for the update Dimitri! On 10/2/13 1:58 PM, ext Dimitri Glazkov wrote: * HTML Imports (http://www.w3.org/TR/html-imports/) is getting close to the next WD. Hajime Morrita has been working on that spec, and I would like to put him down as the primary editor. That's fine with me. Thanks Hajime and please update the ED (and PubStatus) accordingly. At some point, we need to look at these specs and consider whether they should remain independent normative dcuments or be incorporated into existing ones like HTML or DOM. For example, HTML Imports is mostly a monkeypatch for HTML spec. But this discussion hasn't started yet. OK, thanks for the heads-up. (I added a note about this to the Plans data for HTML Imports.) -AB
Reminder of WebApps' off-list topic policy [Was: ...]
On 10/2/13 12:51 PM, ext Anne van Kesteren wrote: On Wed, Oct 2, 2013 at 12:29 PM, Arthur Barstow art.bars...@nokia.com wrote: If any of the data for Fullscreen in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 6-July-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. [PubStatus] http://www.w3.org/2008/webapps/wiki/PubStatus I wrote all the text in http://fullscreen.spec.whatwg.org/ on which http://www.w3.org/TR/fullscreen/ appears to be based (although woefully out of date). Given the W3C's explicit stance on forking, I think would be hypocritical for your group to continue publishing this fork. Hi Anne, I appreciate you technical input on WebApps' specs and I would like that to continue. I would also be delighted if/when you and the W3C work out a mutually agreeable copyright policy for Working Group specs. WebApps' charter has a clear set of deliverables and a clear document license for these specs. Until there is consensus within the group to stop work on a spec or the charter is changed (e.g. to a different set of deliverables, different document license, etc.), the expectation is the group will continue to work on XHR, Fullscreen, and every other spec in our charter using W3C Document License. WebApps also has an off-topic policy [Off-Topic] I think you violate when you continue to discuss W3C's document license on WebApps' mail list. Please respect this policy and move all discussions related to W3C document license to the Revising W3C Process Community Group [w3process]. -Thanks, ArtB [Off-topic] http://www.w3.org/2008/webapps/wiki/WorkMode#Off-Topic_Discussion_Policy [w3process] http://www.w3.org/community/w3process/
Re: [quota-api] Seeking status and plans
Hi Arthur, On Thu, Oct 3, 2013 at 1:30 AM, Arthur Barstow art.bars...@nokia.comwrote: Hi Kinuko, If any of the data for the Quota Management API spec in [PubStatus] is not accurate, please provide corrections. Also, if you have any new information re your plans for the spec - last published 03-July-2012 - or the spec's status with respect to being feature complete, implementation status, etc., please let us know. I'm planning to update the FPWD to use some new syntax like Promises, and Mozilla is showing agreement and interest to implement the new draft per discussion on public-webapps ( http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0368.html). The new draft can be found on my github, and am planning to update the WD on w3c site before TPAC. https://github.com/kinu/quota-api/blob/master/draft.md -Thanks, ArtB [PubStatus] http://www.w3.org/2008/**webapps/wiki/PubStatushttp://www.w3.org/2008/webapps/wiki/PubStatus
Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse
Sorry for the delay. On Tue, Sep 3, 2013 at 9:00 PM, Anne van Kesteren ann...@annevk.nl wrote: On Tue, Sep 3, 2013 at 9:18 AM, Takeshi Yoshino tyosh...@google.com wrote: In the spec, we have three cancels - cancel an instance of fetch algorithm - cancel network activity These are the same. Attempted to clarify. Verified that the order of events are the same for abort() and abort error. Thanks for factoring out termination algorithm. It's clearer now. - cancel a request This is the end user terminate, correct? Yes. So, this includes any kind of event resulting in termination of fetch algorithm (network, termination by some user's instruction to UA)? Would you like to be acknowledged as Takeshi Yoshino? If you can give me your name in kanji I can include that too. See e.g. http://encoding.spec.whatwg.org/#acknowledgments for some examples. Thank you. Just alphabetical name is fine. See http://xhr.spec.whatwg.org/ for the updated text. And https://github.com/whatwg/xhr/commits for an overview of the changes.
