Bug 45508

Summary: Move functions from Frame to SelectionController as planned
Product: WebKit Reporter: Darin Adler <darin>
Component: HTML EditingAssignee: Darin Adler <darin>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, dglazkov, webkit.review.bot, zecke
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch abarth: review+, abarth: commit-queue-

Darin Adler
Reported 2010-09-09 18:00:15 PDT
Move functions from Frame to SelectionController as planned
Attachments
Patch (82.65 KB, patch)
2010-09-09 18:23 PDT, Darin Adler
abarth: review+
abarth: commit-queue-
Darin Adler
Comment 1 2010-09-09 18:23:32 PDT
WebKit Review Bot
Comment 2 2010-09-09 20:09:01 PDT
Adam Barth
Comment 3 2010-09-09 21:27:33 PDT
Comment on attachment 67130 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=67130&action=prettypatch Please try not to break the chromium build when landing. Thanks! > WebKit/chromium/src/WebFrameImpl.cpp:1716 > + return IntRect(frame()->selection()->selectionBounds(false)); Not just selection()->bounds(false) ? > WebKit/mac/WebView/WebHTMLView.mm:6052 > + coreFrame->selection()->selectionTextRects(list, SelectionController::RespectTransforms); selection()->selectionTextRects => selection()->textRects ?
Darin Adler
Comment 4 2010-09-10 08:13:17 PDT
Sure, we could rename these functions now that they are on the SelectionController, but I think it’s probably best to do that in a separate pass. I’ll think about doing it now, though.
Adam Barth
Comment 5 2010-09-10 10:03:20 PDT
ok. I just noticed you renamed granularity, which seemed like a good idea.
Darin Adler
Comment 6 2010-09-10 10:13:14 PDT
(In reply to comment #5) > I just noticed you renamed granularity, which seemed like a good idea. That case was different; believe it or not I didn’t rename things. Frame::selectionGranularity() was a function with the body "return selection()->granularity()", and I chose to delete that rather than moving it to SelectionController. One problem with renaming is that SelectionController is accessed with a call named selection() yet represents more than just the selection; the broader concept of selection control. So in some cases we might need to keep selection in the names of selection controller functions. But despite that it does seem likely we can remove the word selection from virtually all SelectionController function names. Just not sure if I should do it now as part of this patch.
Darin Adler
Comment 7 2010-09-10 15:07:09 PDT
Ryosuke Niwa
Comment 8 2012-05-30 00:50:58 PDT
*** Bug 23431 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.