- From: Peter Sorotokin <psorotok@adobe.com>
- Date: Mon, 22 Mar 2004 00:26:07 -0800
- To: Dean Jackson <dean@w3.org>
- Cc: Jim Ley <jim@jibbering.com>, www-svg@w3.org
At 06:50 PM 3/22/2004 +1100, Dean Jackson wrote: >On Sun 21 Mar 2004, Peter Sorotokin wrote: > > > At 02:35 PM 3/22/2004 +1100, Dean Jackson wrote: > > > > >On Sat 20 Mar 2004, Jim Ley wrote: > > > > > >> The editable attribute is a very useful feature, currently though what > > >> happens to the child elements of flowDiv's when they are edited isn't > > >clear. > > > > > >With <text editable="true">Hi <tspan class="name">Jim</tspan>!</text> > > >we currently plan to flatten everything into a single node (and thus > > >lose the styling information). > > > > > >Yes, this is nasty, but the feature is really for simple text editing, > > >not complex text editing (think HTML <input type="text">). > > > > > >So, it <flowRoot> should follow the same pattern. > > > > Dean, I think what we decided is that editable behavior won't change the > > DOM structure of the editable text (i.e. it won't create/destroy elements, > > etc.), not that it will flatten everything. So you can add support for > more > > complex on to of that. > >Fair enough - sorry for forgetting. > >So it will never delete text nodes? Even if I remove all the >text (using DEL), I'm left with a empty node? Yes > If I position the >cursor just after a <tspan> and just before >another <tspan>, where does the text I type go (into >the first, into the second, or between)? From the DOM perspective these are different positions. From the UI perspective it will try to move between nodes only as necessary. >I have a feeling that we won't be able to specify much that >will help people. A rich text control would be expected to >insert nodes, which will require scripting. Yes, and we just need to provide hooks. Peter >I figure we might as well keep the discussion here for now. > >Dean
Received on Monday, 22 March 2004 03:25:04 UTC