On Tue, Jul 1, 2014 at 1:19 AM, Ryosuke Niwa wrote:
>
> On Jun 24, 2014, at 3:44 AM, Robin Berjon wrote:
>
>
> Second, it doesn't address the point made below about native UI exposing a
> likely non-natural subset of the commands I wish to support.
>
>
> That presumes an opt-out mechanism to ena
On Jun 30, 2014, at 4:19 PM, Ryosuke Niwa wrote:
>
> On Jun 24, 2014, at 3:44 AM, Robin Berjon wrote:
>
>> On 24/06/2014 00:38 , Ben Peters wrote:
Also, if the browser includes a "bold" command by default and I
don't support bolding and therefore cancel the event, the user who
On Jun 24, 2014, at 3:44 AM, Robin Berjon wrote:
> On 24/06/2014 00:38 , Ben Peters wrote:
>>> Also, if the browser includes a "bold" command by default and I
>>> don't support bolding and therefore cancel the event, the user who
>>> has been relying on the native UI is getting the worst possibl
On 24/06/2014 00:38 , Ben Peters wrote:
Also, if the browser includes a "bold" command by default and I
don't support bolding and therefore cancel the event, the user who
has been relying on the native UI is getting the worst possible
experience: native controls that do nothing at all.
>
This d
> From: Robin Berjon [mailto:ro...@w3.org]
>
> On 06/06/2014 18:39 , Ryosuke Niwa wrote:
> > On Jun 6, 2014, at 4:29 AM, Piotr Koszuliński
> > wrote:
> >> 1. That we need any native UI related to cE at all. We don't. We can
> >> display our own toolbars, with our own buttons, with our own icons
>
