W3C home > Mailing lists > Public > public-editing-tf@w3.org > September 2016

Re: proposed agenda for Editing Taskforce meeting on September 22 at TPAC (Lisboa)

From: Johannes Wilm <johannes@fiduswriter.org>
Date: Wed, 14 Sep 2016 23:34:01 +0200
Message-ID: <CABkgm-SD3b_P8=msJayKgR5uA_4e5pRKQh8bt5YFLFw-m27b9w@mail.gmail.com>
To: "Theresa O'Connor" <eoconnor@apple.com>
Cc: "public-editing-tf@w3.org" <public-editing-tf@w3.org>
On Wed, Sep 14, 2016 at 8:02 PM, Theresa O'Connor <eoconnor@apple.com>
wrote:

> Hi Johannes,
>


Hey Theresa!


>
> You wrote:
>
> > Please let me know if you have any other issues you want to talk
> > about.
>
> We have a couple of things we'd like to talk about. Enrica's currently
> on vacation, so I apologize if my attempt to explain these isn't very
> accurate. (She'll be at the editing meeting next week.)
>

Great! Thanks for getting in touch!

>
> > * Format context menu on iOS/Safari, opt-in/out solution presentation
> >   of Apple's proposal. [10]
> >
> > [10] https://github.com/w3c/editing/issues/141
>
> See also Ryosuke's comments in Issue 93:
>
>                 https://github.com/w3c/editing/issues/93
>
> Personally I'd like to see a declarative way for authors to say which
> inputTypes the contenteditable area supports.


The issue of these context menus really appears to be the #1 reason for
frustration on the part of JS editors developers as of today, and it is
limited to Safari/iOS, so the top priority in respect would be to provide
some way to make Safari/iOS behave like the other browsers on other
platforms. If you can come up with a way that is more granular that allows
for even more options, that would also be OK.

If it turns out it is complicated to come up with something that can be
implemented in the near term, one could also imagine to first have a simple
solution that just turns of the extra context menus, and then add more
advanced and granular solutions some time later.


> Such a declarative
> mechanism could get pretty unweildy, so it might make sense to
> undeprecate & specify contenteditable=plaintext-only, which is a pretty
> common case.
>

contenteditable=plaintext-only apparently doesn't solve the problem
entirely, as it interferes with the pasting HTML on some platforms, and on
iOS, it still adds a context menu for clipboard actions that overlaps other
the JS editor's controls. See a discussion of some JS developers trying to
get around this problem in this thread [1].



>
> Additionally, there are a number of execCommands that don't have
> corresponding inputTypes. I think we'd like to close the gap there. In
> several cases, this would require the ability to pass an argument (e.g.
> foreColor/backColor need a way to specify the color in question).
>
>
execCommand is not really used on the JS side of things in any of the
projects we have been able to find. This is due to the universal brokenness
of execCommand. There are some parts of execCommand (clipboard-related)
that all projects have to use because there is no other way, but most of
the other parts are not in use, as far as we can tell.

So far, we have not added inputTypes for actions that require do not
requite an argument [2]. This is because we haven;'t bothered about
providing a way to add arguments to the beforeInput event. Also, we only
had an immediate need to support those editing operations that have a
context menu entry or a keyboard shortcut of some kind because there isn't
really a way to trigger the other ones anyway (execCommand executed through
script code does not trigger beforeinput events).

What would the use case for having inputTypes for forecolor, etc. be? If
there is a way to change the foreground color within an
contenteditable-element in Safari, I agree we need to have a beforeinput
event for these as well (and have a way to turn this feature off).

I have looked through the context menu on Safari for contenteditable. I
could only get bold/italic to work. There is something there about showing
colors and fonts, but I couldn't get it to do anything for me. Could we get
a full list of all the inputTypes you currently have either shortcuts or
context menus to on any of your platforms for the meeting on the 22nd? I
think that would be very helpful.


[1] https://github.com/ProseMirror/prosemirror/issues/7

[2] https://github.com/w3c/editing/issues/110#issuecomment-215282880






>
> See you in Lisbon,
> Tess
>
>
[1] https://github.com/ProseMirror/prosemirror/issues/7

-- 
Johannes Wilm
Fidus Writer
http://www.fiduswriter.org
Received on Wednesday, 14 September 2016 21:34:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 September 2016 21:34:31 UTC