To update you all, my colleagues and I have made a design
documenthttps://docs.google.com/document/d/1vzzi_wQHO0GtLnu-1IYutUKbcpAYlHqZwQlwbfLuowM/edit?hl=enauthkey=CLOa9cgN.
You should all be able to view the document.
I've given editing rights to people who have replied to this thread but
On Feb 1, 2011, at 6:51 PM, Ryosuke Niwa wrote:
• DOMPosition or SimplePosition - This class solely works on DOM, and
is agnostic of renderers and other parts of WebCore. It's meant to be used
in utility functions and classes or passed along between renderers and
WebCore/dom. It
On Fri, Feb 4, 2011 at 10:30 AM, Darin Adler da...@apple.com wrote:
On Feb 1, 2011, at 6:51 PM, Ryosuke Niwa wrote:
• DOMPosition or SimplePosition - This class solely works on DOM,
and is agnostic of renderers and other parts of WebCore. It's meant to be
used in utility functions
Just for context: Maciej and others had some feedback in the similar Rich
Text Editing Questions, Refactoring of Position Class thread from a year
ago (4/2/10). As an aside, I'm wondering if the general thoughts and
reservations about supporting positions inside :before/:after-generated
content
On Wed, Feb 2, 2011 at 3:16 AM, Roland Steiner rolandstei...@google.comwrote:
Just for context: Maciej and others had some feedback in the similar Rich
Text Editing Questions, Refactoring of Position Class thread from a year
ago (4/2/10). As an aside, I'm wondering if the general thoughts and
Hi all,
*
*
*While I'm not intending to write a patch for the following proposal anytime
soon, I'd really like to get your feedback.*
*
*
As you might all know, Position classes in WebCore need refactoring and
cleanup. Part of it is due to legacy editing positions that do many
magics, and we're
6 matches
Mail list logo
