|
|
Created:
4 years, 2 months ago by shaktisahu Modified:
4 years, 2 months ago Reviewers:
Avi (use Gerrit), dglazkov, Brian Goldman, esprehn, David Trainor- moved to gerrit, nyquist, Khushal CC:
anandc+watch-blimp_chromium.org, bgoldman+watch-blimp_chromium.org, blink-reviews, blink-reviews-api_chromium.org, chromium-reviews, creis+watch_chromium.org, darin-cc_chromium.org, dglazkov+blink, dtrainor+watch-blimp_chromium.org, gcasto+watch-blimp_chromium.org, jam, jessicag+watch-blimp_chromium.org, khushalsagar+watch-blimp_chromium.org, kinuko+watch, kmarshall+watch-blimp_chromium.org, lethalantidote+watch-blimp_chromium.org, maniscalco+watch-blimp_chromium.org, marcinjb+watch-blimp_chromium.org, mlamouri+watch-content_chromium.org, nasko+codewatch_chromium.org, nyquist+watch-blimp_chromium.org, perumaal+watch-blimp_chromium.org, scf+watch-blimp_chromium.org, shaktisahu+watch-blimp_chromium.org, sriramsr+watch-blimp_chromium.org, steimel+watch-blimp_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDisable caret blinking for blimp
For blimp, blinking caret in a text input area causes lot of redundant
state update messages being sent between client and server. To reduce
the data usage, a settings was added to blink to disable the blinking.
BUG=652899
Committed: https://crrev.com/22c4d40260078dfe23612368f2ae9519729062ce
Cr-Commit-Position: refs/heads/master@{#424222}
Patch Set 1 #
Total comments: 4
Patch Set 2 : Addressed comments #Patch Set 3 : Using RendererPrefereces #
Total comments: 1
Patch Set 4 : BUILD.gn changes #Messages
Total messages: 37 (16 generated)
shaktisahu@chromium.org changed reviewers: + dtrainor@chromium.org
Description was changed from ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG= ========== to ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG= ==========
shaktisahu@chromium.org changed reviewers: + nyquist@chromium.org
Description was changed from ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG= ========== to ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG=652899 ==========
Also nit; could you swap 'server' for 'engine' in the CL description? https://codereview.chromium.org/2381373002/diff/1/content/renderer/render_vie... File content/renderer/render_view_impl.cc (right): https://codereview.chromium.org/2381373002/diff/1/content/renderer/render_vie... content/renderer/render_view_impl.cc:991: settings->setDisableCaretBlinking(prefs.disable_caret_blinking); Could you add a comment as to what this does? https://codereview.chromium.org/2381373002/diff/1/third_party/WebKit/public/w... File third_party/WebKit/public/web/WebSettings.h (right): https://codereview.chromium.org/2381373002/diff/1/third_party/WebKit/public/w... third_party/WebKit/public/web/WebSettings.h:132: virtual void setDisableCaretBlinking(bool) = 0; It looks like these are supposed to be alphabetically sorted.
bgoldman@chromium.org changed reviewers: + bgoldman@chromium.org
Can you add a TEST= line to the description?
shaktisahu@chromium.org changed reviewers: + avi@chromium.org, sky@chromium.org
avi@ - PTAL at content/ sky@ - PTAL at third_party/WebKit/
content lgtm You will need a content reviewer.
On 2016/10/05 17:44:26, Avi wrote: > content lgtm > > You will need a content reviewer. Sorry, you will need an IPC reviewer.
On 2016/10/05 17:07:31, shaktisahu wrote: > avi@ - PTAL at content/ > > sky@ - PTAL at third_party/WebKit/ I'm not a good third_party/WebKit owner. Please file a local owner.
sky@chromium.org changed reviewers: - sky@chromium.org
lgtm % nits to move some methods around. https://codereview.chromium.org/2381373002/diff/1/third_party/WebKit/Source/w... File third_party/WebKit/Source/web/WebSettingsImpl.cpp (right): https://codereview.chromium.org/2381373002/diff/1/third_party/WebKit/Source/w... third_party/WebKit/Source/web/WebSettingsImpl.cpp:465: void WebSettingsImpl::setDisableCaretBlinking(bool disableCaretBlinking) Move to above setDisableReadingFromCanvas https://codereview.chromium.org/2381373002/diff/1/third_party/WebKit/Source/w... File third_party/WebKit/Source/web/WebSettingsImpl.h (right): https://codereview.chromium.org/2381373002/diff/1/third_party/WebKit/Source/w... third_party/WebKit/Source/web/WebSettingsImpl.h:59: void setDisableCaretBlinking(bool) override; Move this down to above setDisableReadingFromCanvas?
shaktisahu@chromium.org changed reviewers: + dglazkov@chromium.org
dglazkov@ - PTAL at third_party/WebKit/
lgtm, but please add a TEST= like bgoldman@ suggested.
esprehn@chromium.org changed reviewers: + esprehn@chromium.org
I think you want to instead move the caret to be a separate composited layer and have the blinking be done client side like selection handles. Many users have never seen one before and I susoefits confusing and looks like the page is stuck. Separately we have a setting to control the blink speed of the caret already. Doing WebRenderTheme::setCaretBlinkInterval(0) should already disable the blinking. Not lgtm :)
On 2016/10/07 at 17:42:36, esprehn wrote: > I think you want to instead move the caret to be a separate composited layer and have the blinking be done client side like selection handles. Many users have never seen one before and I susoefits ^ suspect*
On 2016/10/07 17:43:20, esprehn wrote: > On 2016/10/07 at 17:42:36, esprehn wrote: > > I think you want to instead move the caret to be a separate composited layer > and have the blinking be done client side like selection handles. Many users > have never seen one before and I susoefits > ^ suspect* We'll have a modal dialog instead of doing text insertion directly into the page content (ping me on chat if you want to see the mocks), so the page content won't be visible or interactive. We just don't want blink doing unnecessary work if we know it's not needed. That's a good idea about using the renderer preferences :).
Much simpler now :). Using caret_blink_interval = 0 instead. dtrainor@, esprehn@ - PTAL.
lgtm
lgtm. https://codereview.chromium.org/2381373002/diff/40001/blimp/engine/session/ta... File blimp/engine/session/tab.cc (right): https://codereview.chromium.org/2381373002/diff/40001/blimp/engine/session/ta... blimp/engine/session/tab.cc:108: render_view_host->SyncRendererPrefs(); Would it be nicer if content gave a callback before the Prefs are sent to the renderer, something along the lines of: https://cs.chromium.org/chromium/src/content/public/browser/content_browser_c...
The CQ bit was checked by shaktisahu@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from avi@chromium.org, dtrainor@chromium.org, nyquist@chromium.org Link to the patchset: https://codereview.chromium.org/2381373002/#ps40001 (title: "Using RendererPrefereces")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromeos_x86-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...) linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_clobber_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by shaktisahu@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from avi@chromium.org, esprehn@chromium.org, dtrainor@chromium.org, nyquist@chromium.org, khushalsagar@chromium.org Link to the patchset: https://codereview.chromium.org/2381373002/#ps60001 (title: "BUILD.gn changes")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG=652899 ========== to ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG=652899 ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Description was changed from ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG=652899 ========== to ========== Disable caret blinking for blimp For blimp, blinking caret in a text input area causes lot of redundant state update messages being sent between client and server. To reduce the data usage, a settings was added to blink to disable the blinking. BUG=652899 Committed: https://crrev.com/22c4d40260078dfe23612368f2ae9519729062ce Cr-Commit-Position: refs/heads/master@{#424222} ==========
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/22c4d40260078dfe23612368f2ae9519729062ce Cr-Commit-Position: refs/heads/master@{#424222} |