- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Sat, 20 Dec 2014 09:15:54 -0500
- To: Johannes Wilm <johannes@fiduswriter.org>, Ben Peters <Ben.Peters@microsoft.com>
- CC: public-editing-tf <public-editing-tf@w3.org>
On 12/18/14 1:13 PM, Johannes Wilm wrote: > On Thu, Dec 18, 2014 at 7:01 PM, Ben Peters <Ben.Peters@microsoft.com > <mailto:Ben.Peters@microsoft.com>> wrote: > > On Thu, Dec 18, 2014 at 9:54 AM, Johannes Wilm > <johannes@fiduswriter.org <mailto:johannes@fiduswriter.org>> wrote: > > > > Then Javascript would need to need to be used to do everything > else: draw > > red lines under corresponding words, create selection menus, > etc. .It seems > > though that this would be something that should be specified > somewhere else > > than in contenteditable. > > This is an interesting idea. I think it seems like something we > should consider later, but in order to maintain momentum on > contentEditable=typing, beforeinput, and beforeselectionchange, I > think we should try to concentrate our efforts there. > > > Absolutely. It really doesn't need to have anything to do with > contenteditable at all. Lets get back to that at some later stage. Agree on the priorities, however, perhaps this should be captured in a new Issue (tagged appropriately f.ex. "Enhancement"). (Another option some specs use is to create a separate document for feature requests (that won't be part of the initial spec.)). -AB
Received on Saturday, 20 December 2014 14:16:23 UTC