[Webkit-unassigned] [Bug 106817] [CSS Regions] Selecting text inside + outside regions does not work properly

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=106817


Zoltan Horvath <zoltan at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zoltan at webkit.org




--- Comment #24 from Zoltan Horvath <zoltan at webkit.org>  2013-07-31 13:18:45 PST ---
(In reply to comment #23)
> (From update of attachment 207284 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=207284&action=review
> 
> > Source/WebCore/editing/VisibleSelection.h:95
> > +    PassRefPtr<Range> getRangeAt(int) const;
> > +    int rangeCount() const;
> 
> We don't want to support these APIs. r-.

I have some questions.
Is it your opinion or Apple's point of view on this decision? Can you share some details what was behind this decision?

Are you planning to support multi range selection ever? If yes, is there any internal solution already for the problem, and you want to merge that code later to the trunk? I'm asking because there is a comment here: http://trac.webkit.org/browser/trunk/Source/WebCore/editing/VisibleSelection.h#L92 about multi-range selection which suggest that not supporting it is just a temporary state.

If we don't want to support multi-range selection, then we can agree on the correctness of the solution which prevents selection over different flow threads. Or do you have another idea?
Javier started a thread on the mailing list regarding to this topic too. (https://lists.webkit.org/pipermail/webkit-dev/2013-July/025179.html) 

It would be good to hear your opinion! Thanks.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.