[webkit-dev] [blink-dev] Selection & CSS Regions
yosin at chromium.org
Wed Dec 18 17:17:28 PST 2013
I would like to take Render Tree based approach, but I don't want to make
Render Object to have state of selection. Actually, Render object have
selected state for rendering but these states should be implementation
detail of rendering and not expose to editing module.
Selection for Shadow DOM tree is similar to CSS Region. Shadow DOM tree
also randomizes rendering order against (shadow/non-shadow) DOM tree order.
Using render tree information for selection also allows us to handle
position:absolute elements, e.g. advertised elements displayed displayed at
We have a plan to make TextIterator to traverse Render Tree rather than DOM
tree for ease and robust support of Shadow DOM tree.
On Thu, Dec 19, 2013 at 1:24 AM, Manuel Rego Casasnovas <rego at igalia.com>wrote:
> we've been working for a while in selection and CSS Regions.
> Current implementation is working fine from the DOM tree point of view,
> the retrieved content when you do a selection is right (fulfilling the
> editing spec ).
> However, in several use cases with CSS Regions, highlighted content in
> the view does not match with the retrieved one, which is wrong.
> We've been thinking in different 2 different approaches to fix this
> problem. They're explained in detail in the following wiki page:
> Sorry for the cross posting, but we'd like to know the opinion, doubts
> and concerns of editing/selection experts in both projects (WebKit and
> Blink) before going further with the implementation.
> What do you think? Could any of these approaches be eventually
> integrated upstream?
> Thank you very much,
>  https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev