- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Thu, 05 Jun 2014 21:10:00 -0700
- To: Ben Peters <Ben.Peters@microsoft.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Jun 5, 2014, at 10:42 AM, Ben Peters <Ben.Peters@microsoft.com> wrote: >> From: Ryosuke Niwa [mailto:rniwa@apple.com] >> >> Can this be an attribute on elements instead? Otherwise, browsers would >> have to repeatedly call these functions to update edit menu, etc... > > This may be an issue, I agree. But since it's dynamic and changes every time the selection/caret moves, would an attribute really help us save computation? Maybe we should be able to get the status of several commands at once with the event? Something like this (just thinking out loud here)? We should avoid running JS to update the browser UI since that will make the timing of events dispatch dependent on specific implementations. I'm fine with adding some interface objects that needs to be called upon selection change, etc... If keep updating the states is a concern, we can expose a list of states that UA care about somewhere so that the scripts can avoid updating other states - R. Niwa
Received on Friday, 6 June 2014 04:10:34 UTC