[Bug 28841] Incorporate changes suggested by Mixed Content

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28841 Domenic Denicola changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506 Anne changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506 sworddrag...@aol.com changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 29506] Support for a system-wide configuration file to specify permissions for web-applications

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506 Anne changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 29506] New: Support for a system-wide configuration file to specify permissions for web-applications

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29506 Bug ID: 29506 Summary: Support for a system-wide configuration file to specify permissions for web-applications Product: WebAppsWG Version: unspecified Hardware: All

Re: [custom-elements] Invoking lifecycle callbacks before invoking author scripts

Can you give a code example of how this happens? On Feb 24, 2016 8:30 PM, "Ryosuke Niwa" wrote: > > > On Feb 23, 2016, at 1:16 AM, Anne van Kesteren wrote: > > > > On Tue, Feb 23, 2016 at 5:26 AM, Ryosuke Niwa wrote: > >> Hi, > >> > >> We

Re: [custom-elements] Invoking lifecycle callbacks before invoking author scripts

> On Feb 23, 2016, at 1:16 AM, Anne van Kesteren wrote: > > On Tue, Feb 23, 2016 at 5:26 AM, Ryosuke Niwa wrote: >> Hi, >> >> We propose to change the lifecycle callback to be fired both before invoking >> author scripts (e.g. for dispatching events) and

Re: John Schulz introduction

Hi John, John Schulz , 2016-02-23 11:04 -0800: > Archived-At: > > > Hello WP, > > My name is John Schulz and I recently joined the Web Platform Working Group. > > I'm a software

Re: File API - where are the missing parts?

On Tue, Feb 23, 2016 at 10:06 AM, Joshua Bell wrote: > I'm also very interested in hearing from other browser implementers; Chrome > is in the odd position of having made investments in related areas > (FileSystem API and FileWriter API) that did not see adoption in other >

Re: File API - where are the missing parts?

> > * Should permissions persist? If you're working in an editor and reload the > > tab, being hit with a flurry of permission prompts is less than ideal. But > > if you visit it again in a day or a year? And, similar to the "template" > > case above, what if you use a web-based editor to

Re: File API - where are the missing parts?

On Tue, Feb 23, 2016 at 7:06 PM, Joshua Bell wrote: > On Tue, Feb 23, 2016 at 7:12 AM, Florian Bösch wrote: > >> On Tue, Feb 23, 2016 at 2:48 AM, Jonas Sicking wrote: >> >>> Is the last bullet here really accurate? How can you use existing

Re: File API - where are the missing parts?

On Tue, Feb 23, 2016 at 7:12 AM, Florian Bösch wrote: > On Tue, Feb 23, 2016 at 2:48 AM, Jonas Sicking wrote: >> >> Is the last bullet here really accurate? How can you use existing APIs to >> listen to file modifications? > > I have not tested this on all

Re: File API - where are the missing parts?

Thanks for starting this thread, Florian. I'm in broad agreement. On Tue, Feb 23, 2016 at 7:12 AM, Florian Bösch wrote: > On Tue, Feb 23, 2016 at 2:48 AM, Jonas Sicking wrote: > >> Is the last bullet here really accurate? How can you use existing APIs to >>

Re: File API - where are the missing parts?

On Tue, Feb 23, 2016 at 2:48 AM, Jonas Sicking wrote: > Is the last bullet here really accurate? How can you use existing APIs to > listen to file modifications? > I have not tested this on all UAs, but in Google Chrome what you can do is to set an interval to check a

Re: [custom-elements] Invoking lifecycle callbacks before invoking author scripts

On Tue, Feb 23, 2016 at 5:26 AM, Ryosuke Niwa wrote: > Hi, > > We propose to change the lifecycle callback to be fired both before invoking > author scripts (e.g. for dispatching events) and before returning to author > scripts. > > Without this change, event listeners that

Re: [custom-elements] Steps inside HTMLElement's constructor

> On Feb 22, 2016, at 10:46 PM, Ryosuke Niwa wrote: > > Here are steps to construct a custom element as agreed during Jan F2F as I > promised to write down [1] [2]: There's a very appealing alternative to this, which doesn't involve having a element construction stack per

[custom-elements] Steps inside HTMLElement's constructor

Hi all, Here are steps to construct a custom element as agreed during Jan F2F as I promised to write down [1] [2]: Modify http://w3c.github.io/webcomponents/spec/custom/#dfn-element-definition as follows: The element definition describes a custom element and consists of: * custom element

Re: TPAC 2016 - meetings

I'd like to attend Web Perf WG's meeting so it would be ideal if any meetings held for Web Apps WG didn't overlap with those of Web Perf WG's. > On Feb 10, 2016, at 4:34 AM, Chaals McCathie Nevile > wrote: > > Dear all, > > as you probably know, the W3C will hold its

[custom-elements] Invoking lifecycle callbacks before invoking author scripts

Hi, We propose to change the lifecycle callback to be fired both before invoking author scripts (e.g. for dispatching events) and before returning to author scripts. Without this change, event listeners that call custom elements' methods would end up seeing inconsistent states during compound

Re: [ServiceWorker] Expose GeoLocation to workers (#745)

I found a very interesting, and inspiring quote today that I'd like to share with you: - https://twitter.com/jaffathecake Googler. "I want the web to do everything native can, and fast." So can anyone here explain to me how that precludes device/user tracking? Or how HTML5 Web Apps can not be

Re: File API - where are the missing parts?

On Sun, Feb 21, 2016 at 3:32 AM, Florian Bösch wrote: > > *What this covers* > >- Read one or many files in their entirety in one go (in python that >would be open('foobar').read()) >- Save a completed binary string in its entirety in one go to the >download

FW: New W3C publication requirements as of March 1

-Original Message- From: Philippe Le Hegaret [mailto:p...@w3.org] Sent: 18 February 2016 22:03 To: Chairs ; spec-prod Subject: New W3C publication requirements as of March 1 All, We adopted back in May 2015 [1] a project to update our style sheets

Re: [geolocation] New Working Group Technical Report - Background GPS

Addendum (Sorry) Other Options: - 4) When the device goes to sleep when a Web App is still watching GPS, or simply backgrounds or minimizes a device-tracker, it should make a sound and or vibrate as a non-visual cue that tracking is ongoing? 5) When a device is reawakened or a device-tracking app

[geolocation] New Working Group Technical Report - Background GPS

Hi, I have no experience with how a W3C standard gets off the ground, or an existing standard gets modified, but it would appear that a Working Group Technical Report is required. Either way, none of the browser manufacturers seem keen on implementing this functionality without W3C involvement so

Re: [WebIDL] T[] migration

On Thu, 07 Jan 2016 20:12:44 +0100, Boris Zbarsky wrote: On 12/18/15 3:53 AM, Simon Pieters wrote: Note that it requires liveness. Does that work for a frozen array? No. You'd have to create a new array object at the point when you want to update the set of values in

i18n-ISSUE-519: Table of contents does not display properly in Safari browser

The table of contents for the specification is not visible when using the Safari browser on Macintosh. Steven Atkin, Ph.D. STSM - Chief Globalization Architect IBM Globalization Center of Competency at...@us.ibm.com http://www-3.ibm.com/software/globalization/index.jsp

i18n-ISSUE-518: Need to explain name matching rules for cache names

5.5.2 has(cacheName), 5.5.3 open(cacheName), and 5.5.4 delete(cacheName) https://slightlyoff.github.io/ServiceWorker/spec/service_worker_1/#cache-storage-has https://slightlyoff.github.io/ServiceWorker/spec/service_worker_1/#cache-storage-open

Re: [ServiceWorker] Expose GeoLocation to workers (#745)

Look I %100 acknowledge the problem(s) @martinthomson highlights, and the need to prevent abuse from the black hats. All I’m saying is let’s work the problem rather than simply rocking in the foetal position, or worse, concocting artificial and exaggerated speed-humps on the release path of much

New Service Worker Event from GeoLocation

WRT the Service Worker specification can I please request the inclusion of a new event? onTravel/Move/Position/Location/WhateverIsAppropriate. The positionManager subscription should allow one to specify min distance and/or time between GPS updates but the firing of this event must be capable of

TPAC 2016 - meetings

Dear all, as you probably know, the W3C will hold its Technical Plenary meeting this year in Lisbon, September 19-23. Rather than meet for several days in plenary, with an hour or two for any given topic we are considering an approach that gives more focused time to a few important areas

Re: [ServiceWorker] Expose GeoLocation to workers (#745)

@martinthomson I hate to make this a point of jurisdiction, but I think that this is a discussion that needs to be had in the geolocation working group. I've been careful to avoid any demarcation issues by always involving the Service Worker AND GeoLocation

Re: [clipboard] Sanitizing HTML content for security/privacy on copy or paste?

On Tue, 09 Feb 2016 12:39:33 +0100, Hallvord Reiar Michaelsen Steen wrote: Hi, some discussion of how browsers can try to safeguard security/privacy while copying/pasting HTML got tangled into the "remove dangerous formats from mandatory data types" thread [1]. I think it

[service worker] f2f meeting notes, next meeting details

Hi folks, for those who are wondering, the last face to face meeting created an agenda, as a github issue: https://github.com/slightlyoff/ServiceWorker/issues/806 and then just updated issues as they went. The relevant sisues are linked from teh agenda, so you can look for updates from

[clipboard] Sanitizing HTML content for security/privacy on copy or paste?

Hi, some discussion of how browsers can try to safeguard security/privacy while copying/pasting HTML got tangled into the "remove dangerous formats from mandatory data types" thread [1]. I think it will be easier to follow with a separate thread. Context: we're talking copy from any normal public

Re: Clipboard API: remove dangerous formats from mandatory data types

> But copying a fragment of HTML in the wild without reformulating it will > lead to privacy breach: it would copy references to external content. I > believe all browsers have an "inlining" method to solve that problem I'm trying to handle this question on another E-mail thread so please follow

RE: [service worker] f2f meeting notes, next meeting details

Here are notes I captured during the meeting: Service Workers Face-to-Face Meeting Notes Date: January 26, 2016 Place: Mozilla's San Francisco office Attendees -- * Microsoft - Ali Alabbas, Jatinder Mann * Google - Jake Archibald, Alex Russell, Ilya Grigorik, Marijn Kruisselbrink

Re: Clipboard API: remove dangerous formats from mandatory data types

Hallvord, IIUC the issue is that while transcoding complex formats via formats that can be easily sanity-checked by the browser takes care of letting content set complex formats like JPEG, GIF while protecting local content, but it loses the ability for content to pass that content to other local

Re: Clipboard API: remove dangerous formats from mandatory data types

On Mon, Feb 8, 2016 at 7:45 PM, Wez wrote: > Hallvord, > > IIUC the issue is that while transcoding complex formats via formats that > can be easily sanity-checked by the browser takes care of letting content > set complex formats like JPEG, GIF while protecting local content,

Re: Clipboard API: remove dangerous formats from mandatory data types

(Finally found some time to resume this old discussion - if you've all forgotten the details by now the thread started here: https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0819.html ) cool! >> But copying a fragment of HTML in the wild without reformulating it will >> lead to

Re: Clipboard API: remove dangerous formats from mandatory data types

BTW, we have a slightly related and interesting discussion regarding custom data types going on here: https://bugzilla.mozilla.org/show_bug.cgi?id=860857 I should try to sum up some of the arguments and proposals and present them on this list but if anyone wants to chime in, I'd appreciate more

Re: [clipboard] kill onbefore* events?

On Thu, Feb 4, 2016 at 2:43 AM, Grisha Lyukshin wrote: > > Killing them doesn't sound like the right course of action. We would have to > come up > with another API so we can have an alternative to what before cut/copy/paste > do. True, it's a use case we should handle.

Re: Clipboard API: remove dangerous formats from mandatory data types

(Finally found some time to resume this old discussion - if you've all forgotten the details by now the thread started here: https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0819.html ) On Sat, Aug 29, 2015 at 3:16 PM, Paul Libbrecht wrote: > But copying a

Re: [clipboard] kill onbefore* events?

The use case these events were meant to fulfil is described here: https://w3c.github.io/clipboard-apis/#determining-ui-state In short: they allow you to tell the UA to enable copy/cut/paste commands even when they would normally be disabled. On Tue, Feb 2, 2016 at 11:48 PM, Gary Kacmarcik

Re: [clipboard] kill onbefore* events?

Killing them doesn't sound like the right course of action. We would have to come up with another API so we can have an alternative to what before cut/copy/paste do. Why can't we fire these events regardless of content editability and do actual editability check during the execution of the

[clipboard] kill onbefore* events?

Hi, there's some scepticism about implementing onbeforecut/onbeforepaste/onbeforecopy in Gecko [1], IE's implementation seems considerably more limited than I expected (maybe because of bugs?), and it doesn't really seem like an elegant solution to the use case it is meant to solve. Would anybody

Re: [clipboard] kill onbefore* events?

I'm not very familiar with onbefore{cut|paste|copy}, but they sound like very specialized versions of the beforeinput event. What do these events provide that you don't get from handling beforeinput? (well, other than the upcoming context "I'm about to do a cut/paste/copy") On Tue, Feb 2, 2016

Re: Art steps down - thank you for everything

Thank you Art! Takeshi On Mon, Feb 1, 2016 at 12:39 AM, Tobie Langel wrote: > So long, Art, and thanks for all the fish. > > --tobie > > On Thu, 28 Jan 2016, at 16:45, Chaals McCathie Nevile wrote: > > Hi folks, > > > > as you may have noticed, Art has resigned as a

Re: Art steps down - thank you for everything

It has been a pleasure working with you Art. Your expertise, leadership and diplomacy will be missed. I wish you the best for your future endeavours! -- Mounir On Sat, 30 Jan 2016, at 12:29, Jungkee Song wrote: > Thank you Art! It has been a great experience and joy working with you. > Your calm

Re: Art steps down - thank you for everything

So long, Art, and thanks for all the fish. --tobie On Thu, 28 Jan 2016, at 16:45, Chaals McCathie Nevile wrote: > Hi folks, > > as you may have noticed, Art has resigned as a co-chair of the Web > Platform group. He began chairing the Web Application Formats group about > a decade ago,

Re: Art steps down - thank you for everything

Thank you Art! It has been a great experience and joy working with you. Your calm leadership and warm support will be missed. On Sat, Jan 30, 2016 at 4:18 AM, Alex Russell wrote: > Sorry to hear you're leaving us, Art. Your skills and humor will be missed. > > On Fri,

Thanks Art Barstow, for more than 15 years of contributions

Art, On behalf of W3C, I would like to thank you for outstanding service as co-chair of the Web Platform Working Group and chair of the Pointer Events Working Group. You have contributed to the W3C for many years, by being a W3C Fellow from 2000 to 2002, and through involvement with HP and

Re: Art steps down - thank you for everything

Thank you Art. You carried out this group and community over so many years. Your first email to the AC was entitled "Just say NO?" as a response to a proposal from W3C. It will take a while for me to realize you won't be standing and come to the microphone to challenge us as you used to do

Re: Art steps down - thank you for everything

Sorry to hear you're leaving us, Art. Your skills and humor will be missed. On Fri, Jan 29, 2016 at 7:51 AM, Philippe Le Hegaret wrote: > Thank you Art. > > You carried out this group and community over so many years. > > Your first email to the AC was entitled "Just say NO?" as a

Art steps down - thank you for everything

Hi folks, as you may have noticed, Art has resigned as a co-chair of the Web Platform group. He began chairing the Web Application Formats group about a decade ago, became the leading co-chair when it merged with Web APIs to become the Web Apps working group, and was instrumental in making

Service Workers meeting, 11-12 April in Seattle

Hi all, there will be a meeting to work on Service Workers, scheduled for 11-12 April. Microsoft have kindly agreed to host it in Seattle (or thereabouts). An initial webpage for the meeting is in our github repo: https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/11-12aprSW.md

Re: Art steps down - thank you for everything

> On Jan 29, 2016, at 00:45, Chaals McCathie Nevile > wrote: > > Hi folks, > > as you may have noticed, Art has resigned as a co-chair of the Web Platform > group. He began chairing the Web Application Formats group about a decade > ago, became the leading co-chair

Re: Art steps down - thank you for everything

On Thu, Jan 28, 2016 at 7:45 AM, Chaals McCathie Nevile wrote: > Thanks Art for everything you've done for the group for so long. Hi Art, Yes, thank you very much for chairing the WG for so long. This group has under your chairing been one of the W3C WGs that has moved

Re: Art steps down - thank you for everything

> On 28 Jan 2016, at 17:45, Chaals McCathie Nevile > wrote: > > Hi folks, > > as you may have noticed, Art has resigned as a co-chair of the Web Platform > group. He began chairing the Web Application Formats group about a decade > ago, became the leading co-chair when

RE: Art steps down - thank you for everything

On Thursday, January 28, 2016 7:46 AM, Chaals McCathie Nevile wrote: > Now we are three co-chairs, we will work between us to fill Art's shoes. > It won't be easy. > > Thanks Art for everything you've done for the group for so long. Thanks Art. You were there from the first day I showed up at

Re: Art steps down - thank you for everything

+1 :DG< On Thu, Jan 28, 2016 at 7:45 AM, Chaals McCathie Nevile < cha...@yandex-team.ru> wrote: > Hi folks, > > as you may have noticed, Art has resigned as a co-chair of the Web > Platform group. He began chairing the Web Application Formats group about a > decade ago, became the leading

Re: Art steps down - thank you for everything

On Jan 28, 2016 10:49 AM, "Chaals McCathie Nevile" wrote: > > Hi folks, > > as you may have noticed, Art has resigned as a co-chair of the Web Platform group. He began chairing the Web Application Formats group about a decade ago, became the leading co-chair when it merged

Re: Art steps down - thank you for everything

On 28/01/2016 15:45, Chaals McCathie Nevile wrote: Thanks Art for everything you've done for the group for so long. Good luck, and I hope to see you around. +1 P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ |

[Bug 29397] [imports]: Typo: s/altorighm/algorithm

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29397 Domenic Denicola changed: What|Removed |Added Status|NEW |RESOLVED

Re: Holding WP meetings

On 1/12/16 3:44 AM, Léonie Watson wrote: Léonie, Ade, Chaals and Art (WP co-chairs) I agree with everything Léonie said but, FTR, I resigned from this group a few weeks ago. -Best wishes, AB

Notes from Custom Elements meeting

Available at https://www.w3.org/2016/01/25-webapps-minutes.html Text version: Web Platform - Custom Elements 25 Jan 2016 See also: [2]IRC log [2] http://www.w3.org/2016/01/25-webapps-irc Attendees Present Domenic_Denicola, Takayoshi_Kochi,

Apple's feedback for custom elements

Hi all, Here's WebKit team's feedback for custom elements. == Constructor vs createdCallback == We would like to use constructor instead of created callback. https://github.com/w3c/webcomponents/issues/139 At the meeting, we should discuss what happens when a constructor throws during

Re: Apple's feedback for custom elements

Random comments inline (other people from Mozilla may have different opinions) On 01/24/2016 10:01 AM, Ryosuke Niwa wrote: Hi all, Here's WebKit team's feedback for custom elements. == Constructor vs createdCallback == We would like to use constructor instead of created callback. no

FW: HTML plan

-Original Message- From: Léonie Watson [mailto:t...@tink.uk] Sent: 19 January 2016 19:21 To: public-h...@w3.org Subject: HTML plan Dear all, We've put a new draft of the HTML specification into GitHub: http://github.com/w3c/html. You can read the editor's draft:

Re: Service worker F2F meeting - 26th Jan - San Francisco

FYI, it turns out I am going to have to attend virtually. This should not be a problem since the meeting is taking place in a mozilla conference room with our standard vidyo setup. I am planning to be on vidyo for the meeting all day. I'm sorry for the change here, but some personal events

Re: Apple will host Re: Custom Elements meeting will be 25th Jan (not 29th)

Hi Kochi, and all, The remote participation information of the 25th Jan Web Components meeting is available: https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/25janWC.md#logistics - VoIP: Join WebEx

Re: Web Push API intended scope

On 12 January 2016 at 20:38, Martin Thomson wrote: > The Push API is intended for infrequent messages I don't recall this being stated as a design goal or implicit requirement, though I may have missed it. What counts as *infrequent* in this context? Regards Ben

Remote participation Re: Apple will host Re: Custom Elements meeting will be 25th Jan (not 29th)

On Wed, 06 Jan 2016 11:59:55 +0100, Takayoshi Kochi (河内 隆仁) wrote: On Wed, Jan 6, 2016 at 7:00 PM, Ryosuke Niwa wrote: > On Jan 6, 2016, at 12:05 AM, Takayoshi Kochi (河内 隆仁) > > Is there any option to attend this remotely (telcon or

[CSSWG][css-cascade-4] CR of CSS Cascade L4

The CSS WG has published a Candidate Recommendation and invites implementations of the CSS Cascading and Inheritance Module Level 4 https://www.w3.org/TR/css-cascade-4/ This CSS module describes how to collate style rules and assign values to all properties on all elements by way of

Re: Web Push API intended scope

On 16 January 2016 at 08:06, Ben Last wrote: > I don't recall this being stated as a design goal or implicit requirement, > though I may have missed it. What counts as infrequent in this context? Maybe it wasn't express, but implied. There are a few simple drivers for this:

Re: Web Push API intended scope

Hi Martin, Thanks for the clarification. This makes sense to me. Perhaps I missed it - I'll read again closely but I wonder if that intent could be expressed in those clear terms in the draft text? I don't recall seeing "infrequent" messaging mentioned at all for example. Thanks again.

Re: Web Push API intended scope

Paul, just for you: https://github.com/w3c/push-api/issues/179 On 13 January 2016 at 19:17, Paul Banks wrote: > Hi Martin, > > Thanks for the clarification. This makes sense to me. > > Perhaps I missed it - I'll read again closely but I wonder if that intent > could be

Re: Web Push API intended scope

Nice thanks! > On 13 Jan 2016, at 10:15, Martin Thomson wrote: > > Paul, just for you: https://github.com/w3c/push-api/issues/179 > >> On 13 January 2016 at 19:17, Paul Banks wrote: >> Hi Martin, >> >> Thanks for the clarification. This makes sense

Re: Web Push API intended scope

Thanks for that Costin although I'm not sure if you are advocating for use of Web Push in this role or stating that there would be benefits if it was designed to support this workload better. The biggest case where is see a limit in specified functionality is for in-page updates like updating

Re: Web Push API intended scope

Hi Paul, The Push API is intended for infrequent messages. If you have a page open to site, it might still be suitable to rely on push for messages that are infrequent or unpredictable. However, if you are actively communicating with your site, it is best to use more direct means of sending

Holding WP meetings

Hello WP, Finding the balance between rapidity and process can be challenging. WP continues the work mode established by WebApps, where flexible and agile collaboration is encouraged, and the W3C process respected. Whenever people meet (formally or informally) to discuss a spec, there is a good

Web Push API intended scope

Hi all, I came across the Web Push draft spec recently while researching the current state of the art for pushing “real-time” updates to web applications. I’ve read the draft spec as it stands and I’m excited about the possibilities. But I’m a little unsure of the intended scope. Is the

Re: FileReader: rename onload to onsuccess

On 01/08/2016 07:06 PM, Juraj Maracky wrote: Hello, I propose to rename FileReader's load event to success. This way it is much easier to remember and mentally group FileReader's events: error - success; loadstart - loadend; progress - abort. Also, this would clarify potential confusion with

Re: [UIEvents] Keydown/keyup events during composition

Hello, sorry for the delay to reply due to national holiday of Japan. As far as I know, Gecko doesn't dispatch keydown nor keyup event for IME unaware applications because JS changes something at keydown or keyup event handler causes forcibly committing composition that may have caused IME

Re: [UIEvents] Keydown/keyup events during composition

On 2016/01/12 14:02, Ryosuke Niwa wrote: On Jan 11, 2016, at 8:26 PM, Masayuki Nakano wrote: As far as I know, Gecko doesn't dispatch keydown nor keyup event for IME unaware applications because JS changes something at keydown or keyup event handler causes forcibly

Re: [UIEvents] Keydown/keyup events during composition

> On Jan 11, 2016, at 8:26 PM, Masayuki Nakano wrote: > > As far as I know, Gecko doesn't dispatch keydown nor keyup event for IME > unaware applications because JS changes something at keydown or keyup event > handler causes forcibly committing composition that may

FileReader: rename onload to onsuccess

Hello,I propose to rename FileReader's load event to success. This way it is much easier to remember and mentally group FileReader's events:error - success; loadstart - loadend; progress - abort.Also, this would clarify potential confusion with loadend.Thanks,Juraj

Re: [Editing] [DOM] Adding static range API

On Sat, Jan 9, 2016 at 6:55 PM, Ryosuke Niwa wrote: > >> On Jan 9, 2016, at 6:25 PM, Olli Pettay wrote: >> >> Hard to judge this proposal before seeing an API using StaticRange objects. >> >> One thing though, if apps were to create an undo stack of their own,

Re: time at TPAC other than Wednesday?

> On Jan 9, 2016, at 11:49, Grisha Lyukshin wrote: > > Hello Johannes, > > I was the one to organize the meeting. To make things clear, this was an ad > hoc meeting with the intent for the browsers to resolve any ambiguities and > questions on beforeInput spec, which we

Re: time at TPAC other than Wednesday?

> On Jan 9, 2016, at 12:20 PM, Ryosuke Niwa wrote: > > >> On Jan 8, 2016, at 7:12 PM, Johannes Wilm wrote: >> >> On Sat, Jan 9, 2016 at 3:49 AM, Grisha Lyukshin wrote: >>> Hello Johannes, >>> >>> I was the one to organize the

Re: time at TPAC other than Wednesday?

> On Jan 9, 2016, at 6:18 AM, Florian Rivoal wrote: > >> On Jan 9, 2016, at 11:49, Grisha Lyukshin wrote: >> >> Hello Johannes, >> >> I was the one to organize the meeting. To make things clear, this was an ad >> hoc meeting with the intent for the

Re: time at TPAC other than Wednesday?

> On Jan 8, 2016, at 7:12 PM, Johannes Wilm wrote: > > On Sat, Jan 9, 2016 at 3:49 AM, Grisha Lyukshin wrote: >> Hello Johannes, >> >> I was the one to organize the meeting. To make things clear, this was an ad >> hoc meeting with the intent

Re: Proposal - Personal Identity API

בע"ה None of your mentioned techniques (WebID, FOAF+SSL, OAuth, navigator.id) seems covering my proposal. What I meant is simple JavaScript API to read browser/machine logged/synchronized/identification user profile data. For example return in Chrome { name: "Me", surname: "Surname",

[UIEvents] [Editing] Ordering of composition events and beforeinput

Hi, This is a feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. First off, we found out that there are behavior inconsistencies between browsers with respect to composition events. WebKit,

[UIEvents] Firing composition events for dead keys

Hi all, This is another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. We found out that all major browsers (Chrome, Firefox, and Safari) fire composition events for dead keys on Mac but

[UIEvents] [Editing] Moving input/beforeinput events into UI events

Hi all, This is another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. As we discussed various aspects of composition events and beforeinput/input events, it became apparent that we want

[UIEvents] Keydown/keyup events during composition

Hi all, This is another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. We've been informed that Gecko/Firefox does not fire keydown/keyup events during input method composition for each

[Editing] Adding `dataTransfer` to `InputEvent` interface

Hi, This is yet another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. It came to our attention that `beforeinput` event fired for paste would need to expose HTML (or images, etc...)

[Editing] [DOM] Adding static range API

Hi, This is yet another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. For editing APIs, it's desirable to have a variant of Range that is immutable. For example, if apps were to create

Re: [UIEvents] Keydown/keyup events during composition

On 01/10/2016 01:16 AM, Ryosuke Niwa wrote: Hi all, This is another feedback from multiple browser vendors (Apple, Google, Microsoft) that got together in Redmond last Thursday to discuss editing API and related events. We've been informed that Gecko/Firefox does not fire keydown/keyup

Re: [Editing] [DOM] Adding static range API

Hard to judge this proposal before seeing an API using StaticRange objects. One thing though, if apps were to create an undo stack of their own, they could easily have their own Range-like API implemented in JS. So if that is the only use case, probably not worth to add anything to make the

<    1   2   3   4   5   6   7   8   9   10   >