[ime-api] Fwd: [blink-dev] Removing IME API code from Blink

2015-05-27 Thread Arthur Barstow
Below is a proposal to remove the experimental IME API implementation from Blink. Is there sufficient interest from other implementers to keep this spec on the TR track or should we formally stop work on it and publish a WG Note? Travis, All, WDYT? -Thanks, ArtB Forwarded Message

RE: [ime-api] Fwd: [blink-dev] Removing IME API code from Blink

2015-05-27 Thread Travis Leithead
I believed the use-cases for avoiding UI clashes between site-driven auto-complete lists and IME auto-complete boxes is still a valid use case, and I think the spec is still valid to try to push to recommendation. However, I'd also like to follow up on usage of the ms- prefixed API so that I

Re: Shadow DOM spec bugs will be migrated into GitHub issues

2015-05-27 Thread Hayato Ito
I totally agree. I'm really sorry for spamming. I forgot that closing a bug would trigger sending a mail to public-webapps@. My bad. I thought that a closing bug would notify only people who opted-in to add themselves to a list of cc in each bug. That might be a good opportunity for them to keep

Re: [ime-api] [blink-dev] Removing IME API code from Blink

2015-05-27 Thread Ryosuke Niwa
On May 27, 2015, at 11:46 AM, Travis Leithead travis.leith...@microsoft.com wrote: I believed the use-cases for avoiding UI clashes between site-driven auto-complete lists and IME auto-complete boxes is still a valid use case, and I think the spec is still valid to try to push to

Re: Shadow DOM spec bugs will be migrated into GitHub issues

2015-05-27 Thread Tab Atkins Jr.
Note for the future (to you and editors of other specs in WebApps): Before doing this kind of mass bug editting, please turn off the automatic email to public-webapps. If you can't do that yourself, Mike Smith can (at least, he's done it in the past). That prevents the mass flood of bugspam