[Webkit-unassigned] [Bug 6523] Extract data from SelectionController

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Fri Jan 13 07:56:38 PST 2006


http://bugzilla.opendarwin.org/show_bug.cgi?id=6523


darin at apple.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #5642|review?                     |review-
               Flag|                            |




------- Additional Comments From darin at apple.com  2006-01-13 07:56 -------
(From update of attachment 5642)
Please don't landed commented out lines like these:

+//#include <qrect.h>
+//#include "editing/visible_text.h"

I don't think Selection.h needs to include "misc/shared.h".

For files like Selection.cpp we now are back to "using namespace DOM" rather
than individual "using" lines.

The copy constructor and assignment operator that are implemented for Selection
do exactly what the defaults would do. In those cases it's better to not
declare or define them and let the compiler take care of it.

Since Selection.h includes things like PassRefPtr.h and dom_position.h, those
includes can be removed from the top of SelectionController.

-	 case SelectionController::RANGE:
+	 case khtml::Selection::RANGE:

Why do we need a khtml:: prefix in the above code and other lines like it?

This seems like a nice next step. Over time we might refine and adjust what
Selection has vs. SelectionController, and change various clients that hold
SelectionController to hold Selection instead.

The above are minor quibbles but lets get answers to them before we do review+.

Did you run layout tests? Do they all give identical results?


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list