Add API to WebFrame to enable/disable caret.

Add API to WebFrame to enable/disable caret.
This can be used to disable the caret when the embedder wants
to draw its own caret (for example, for touch based text
editing, the browser shows a caret handle which can be
dragged around with touch).

BUG=none

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=155971

[varunjain, 2013-08-09 18:09:01]

added chromium version of dglazkov

[abarth-chromium, 2013-08-12 18:40:34]

https://codereview.chromium.org/22746004/diff/1/Source/web/WebFrameImpl.cpp
File Source/web/WebFrameImpl.cpp (right):

https://codereview.chromium.org/22746004/diff/1/Source/web/WebFrameImpl.cpp#n...
Source/web/WebFrameImpl.cpp:1371: frame()->selection()->setCaretVisible(enable);
Is there a reason to use a different name in the API and the implementation? 
Perhaps we should use the name "setCaretVisible" in the API...

[varunjain, 2013-08-12 21:43:40]

https://codereview.chromium.org/22746004/diff/1/Source/web/WebFrameImpl.cpp
File Source/web/WebFrameImpl.cpp (right):

https://codereview.chromium.org/22746004/diff/1/Source/web/WebFrameImpl.cpp#n...
Source/web/WebFrameImpl.cpp:1371: frame()->selection()->setCaretVisible(enable);
On 2013/08/12 18:40:34, abarth wrote:
> Is there a reason to use a different name in the API and the implementation? 
> Perhaps we should use the name "setCaretVisible" in the API...

No particular reason. Changed.

[abarth-chromium, 2013-08-12 23:24:02]

lgtm

[commit-bot: I haz the power, 2013-08-12 23:25:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/varunjain@chromium.org/22746004/6001

[commit-bot: I haz the power, 2013-08-13 02:08:07]

Change committed as 155971