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

On Wed, Jan 6, 2016 at 7:00 PM, Ryosuke Niwa <rn...@apple.com> wrote: > > > On Jan 6, 2016, at 12:05 AM, Takayoshi Kochi (河内 隆仁) <ko...@google.com> > wrote: > > > > Is there any option to attend this remotely (telcon or video conference)? > > > > 2

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

Is there any option to attend this remotely (telcon or video conference)? 2015年12月9日(水) 10:26 Ryosuke Niwa : > > > On Dec 8, 2015, at 2:55 AM, Chaals McCathie Nevile < > cha...@yandex-team.ru> wrote: > > > > On Mon, 07 Dec 2015 13:39:25 +1000, Chaals McCathie Nevile < >

Re: [Web Components] proposing a f2f...

On Thu, Oct 29, 2015 at 3:04 PM, Ryosuke Niwa wrote: > > > > On Oct 29, 2015, at 9:47 AM, Chris Wilson wrote: > > > > Or host in Seattle. :) > > > > On Thu, Oct 29, 2015 at 9:20 AM, Travis Leithead < > travis.leith...@microsoft.com> wrote: > >> I would

Re: Tests for new shadow DOM API

Hi, Thanks Ryosuke for starting contributing tests to shadow-dom/ and moving the old ones under untriaged/. I would like to continue triaging old tests in untriaged/ directory. The general rule of thumb (for me) for working on them are: - Remove tests that test out-of-date features (e.g.

Re: [shadow-dom] ::before/after on shadow hosts

Oops, found that you were already there :) https://code.google.com/p/chromium/issues/detail?id=393490#c15 On Fri, Jul 3, 2015 at 2:49 PM, Takayoshi Kochi (河内 隆仁) ko...@google.com wrote: Sorry for coming late, but - crbug.com/393490 Before and After pseudo elements don't work in ShadowRoots

Re: Better focus support for Shadow DOM

to comment here, or at github issue tracker. (The full version of the doc also moved to markdown format, at https://github.com/TakayoshiKochi/tabindex-focus-navigation-explainer/blob/master/TabindexFocusNavigationExplainer.md ) On Wed, Jun 3, 2015 at 4:47 PM, Takayoshi Kochi (河内 隆仁) ko...@google.com

Re: [shadow-dom] ::before/after on shadow hosts

Sorry for coming late, but - crbug.com/393490 Before and After pseudo elements don't work in ShadowRoots (with :host styles) - crbug.com/393509 :host()::before or :host()::after should work have the relevant discussion about the current implementation in Blink (#2). On Thu, Jul 2, 2015 at 1:16

Re: Better focus support for Shadow DOM

with the same focus capabilities as native elements, including both the simple cases (like custom-a) and the more complicated ones with a shadow DOM (like custom-input type=date). Very exciting stuff! I hope others are as enthused as I am :) *From:* Takayoshi Kochi (河内 隆仁) [mailto:ko...@google.com

Re: Better focus support for Shadow DOM

keyboard access issues (in what might yet be a vain attempt to really improve the situation which is overall pretty dismal still): https://www.w3.org/WAI/PF/HTML/wiki/Keyboard 19.02.2015, 04:56, Takayoshi Kochi (河内 隆仁) ko...@google.com: [Shadow]: Shadow host with tabindex=-1, all descendent

Re: Better focus support for Shadow DOM

on shadow host should slide to its inner focusable node https://www.w3.org/Bugs/Public/show_bug.cgi?id=28054 On Wed, Jan 14, 2015 at 2:27 PM, Takayoshi Kochi (河内 隆仁) ko...@google.com wrote: Hi, For shadow DOMs which has multiple focusable fields under the host, the current behavior of tab

Re: Better focus support for Shadow DOM

/document/d/1k93Ez6yNSyWQDtGjdJJqTBPmljk9l2WS3JTe5OHHB50/edit?usp=sharing Any comments/suggestions welcome. On Wed, Jan 14, 2015 at 2:27 PM, Takayoshi Kochi (河内 隆仁) ko...@google.com wrote: Hi, For shadow DOMs which has multiple focusable fields under the host, the current behavior of tab

Re: Better focus support for Shadow DOM

. Once it finishes, I'll post the updates. On Wed, Jan 14, 2015 at 2:27 PM, Takayoshi Kochi (河内 隆仁) ko...@google.com wrote: Hi, For shadow DOMs which has multiple focusable fields under the host, the current behavior of tab navigation order gets somewhat weird when you want to specify

Re: Better focus support for Shadow DOM

the conversation, but for the moment it is on public-html-a...@w3.org and on their wiki - listed as accesskey for increasingly irrelevant historical reasons http://www.w3.org/WAI/PF/HTML/wiki/51wishlist cheers Chaals 14.01.2015, 08:30, Takayoshi Kochi (河内 隆仁) ko...@google.com: Hi, For shadow

Better focus support for Shadow DOM

Hi, For shadow DOMs which has multiple focusable fields under the host, the current behavior of tab navigation order gets somewhat weird when you want to specify tabindex explicitly. This is the doc to introduce a new attribute delegatesFocus to resolve the issue.

Re: [Custom]: Rename createdCallback to created

Hi Jarek, What I learned from people around me is that these names have Callback suffixes because - to indicate that it is for a callback function and not a callable API - it is low-level API and had to use non-trivial name So even it doesn't seem to add any information, the suffix has some

Re: Web Components: two questions

Ondrej, The short answer to whether input inside shadow root under a form will be sent or not is No. The node tree mentioned in Hayato's mail means that form and input belong to different trees. Only elements in the same tree as form will be considered for submission. So you don't have to worry

Re: [IME API]Some Insights from Chinese Input Methods

Hi, On Thu, Dec 19, 2013 at 7:23 PM, Takayoshi Kochi (河内 隆仁) ko...@google.comwrote: FYI, this is (still) being discussed at https://www.w3.org/Bugs/Public/show_bug.cgi?id=22018 And your suggestion is almost same as the reason Microsoft people proposed this. One of the issue blocking

Updating Input Method Editor API working draft

Hi all, Since the last working draft in August, IME API editor's draft has been changed significantly with the result of discussions at TPAC 2013. The biggest change is that I split the previous spec into 2 parts, streamlined main part and others, so the main part which has been mostly agreed on

Re: [ime-api] Seeking status and plans

Hi Arthur, Thanks for the coordination. The status of IME API in the PubStatus page is correct. I will make some modification to Editor's draft soon, taking some of what Microsoft proposed [1], and some clarification about event delivery. If possible, I hope we can get live feedback on the TPAC

Re: [ime-api] Re: FYI: new WD of Input Method Editor API published

Hi James, Thanks for the comment. Let me confirm I understand your comment. The suggestion list which is rendered in your comment, is not for custom rendering of suggestions from IME, but those from a web service (e.g. Google Suggest). So the intention of that example is a use of

Re: [editing] nested contenteditable

+Ryosuke - he is actively working on editing in WebKit. On Wed, May 29, 2013 at 2:27 AM, Travis Leithead travis.leith...@microsoft.com wrote: As far as I know, there is no actively maintained editing spec at the moment. Aryeh’s document is a great start but by no means should it be

Re: [IME] Preparing some feedback

Hi Travis, Before getting into details, is it appropriate to discuss CSS properties (ime-*) and HTML attribute (inputmode) here? At least, I think I should not incorporate CSS/HTML spec into the IME API spec, as they are already in the separate specs and duplication will make lots of issues.

Re: Proposal for a DOM L3 Events Telecon

If Masayuki-san is joining and the time is JST-friendly, I would also like to join, but feel free to ignore me if not. On Wed, May 1, 2013 at 6:30 PM, Wez w...@google.com wrote: Hi guys, mind if I tag along with Gary on the call? On 30 April 2013 13:46, Gary Kačmarčík (Кошмарчик)

Re: [IME] Preparing some feedback

Hi Travis, Thanks for the detailed spec and comments! I'll read it through and will post comments on them. On Thu, Apr 25, 2013 at 3:41 AM, Travis Leithead travis.leith...@microsoft.com wrote: Kenji, et al.: ** ** We appreciate the work you’ve put into this IME API spec so far and

Re: Feedback about W3C Input Method Editor API draft

Hi James, Thanks for the comments! My replies inlined. On Tue, Apr 23, 2013 at 5:35 PM, James Su su...@google.com wrote: Hi all, Please see below my initial feedback about * http://www.w3.org/TR/2013/WD-ime-api-20130404/.* * 5. The getInputContext() method partial interface

Re: Update of the IME API spec working draft [call for comments]

for it. On Tue, Mar 19, 2013 at 6:40 PM, Takayoshi Kochi (河内 隆仁) ko...@google.comwrote: Hi all, It's been a while since the last update for the IME API spec, but we restarted the work on this. I (Takayoshi Kochi) have taken over this authorship from the previous author (Hironori Bono) for updating

Update of the IME API spec working draft [call for comments]

Hi all, It's been a while since the last update for the IME API spec, but we restarted the work on this. I (Takayoshi Kochi) have taken over this authorship from the previous author (Hironori Bono) for updating the spec. If you are interested, please take a look at the current working draft: