The Java Client should be aware of the readback status.

The Java Client should be aware of the readback status.

The ReadBack response should be notified to the Java Client to make necessary decisions.

BUG=472457
Committed: https://crrev.com/f9747e19ad48dfb99c3a4a09e690d67502204cd7
Cr-Commit-Position: refs/heads/master@{#324214}

[patro, 2015-03-31 13:21:58]

behara.ms@samsung.com changed reviewers:
+ davidben@chromium.org, sievers@chromium.org

[patro, 2015-03-31 13:21:59]

Kindly Review,

Thanks
Shyam Patro

[no sievers, 2015-03-31 19:05:20]

lgtm

[davidben, 2015-03-31 19:14:02]

Is there a bug associated with this? I'm not sure what the context is here.

[patro, 2015-04-01 05:51:11]

On 2015/03/31 19:14:02, David Benjamin wrote:
> Is there a bug associated with this? I'm not sure what the context is here.

Created a bug and updated the description.

When we call getScaledContentBitmap, we receive
a response like READBACK_SUCCESS, READBACK_FAILED, READBACK_FORMAT_NOTSUPPORTED,
after processing the request. This response should be passed to
the application, to take necessary decisions.
This patch takes care of sending this response to app.

[AKV, 2015-04-01 14:49:24]

ajith.v@chromium.org changed reviewers:
+ ajith.v@chromium.org

[AKV, 2015-04-01 14:49:25]

https://codereview.chromium.org/1040393002/diff/1/content/public/android/java...
File
content/public/android/java/src/org/chromium/content/browser/ContentReadbackHandler.java
(right):

https://codereview.chromium.org/1040393002/diff/1/content/public/android/java...
content/public/android/java/src/org/chromium/content/browser/ContentReadbackHandler.java:28:
*                   failure.
Please update doxygn description corresponds to newly added response parameter.

https://codereview.chromium.org/1040393002/diff/1/content/public/android/java...
content/public/android/java/src/org/chromium/content/browser/ContentReadbackHandler.java:66:
callback.onFinishGetBitmap(bitmap, response);
You may have to incorporate same changes in
ContentViewReadbackTest->onFinishGetBitmap() function as well to make
ContentShell test bot happy. Please take care of that as well.

[patro, 2015-04-02 08:50:56]

The CQ bit was checked by behara.ms@samsung.com

[patro, 2015-04-02 08:50:56]

The patchset sent to the CQ was uploaded after l-g-t-m from sievers@chromium.org
Link to the patchset: https://codereview.chromium.org/1040393002/#ps20001
(title: " ")

[commit-bot: I haz the power, 2015-04-02 08:51:21]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1040393002/20001

[commit-bot: I haz the power, 2015-04-02 09:04:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-04-02 09:04:48]

Try jobs failed on following builders:
  android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...)

[patro, 2015-04-08 09:20:53]

The CQ bit was checked by behara.ms@samsung.com

[patro, 2015-04-08 09:20:53]

The patchset sent to the CQ was uploaded after l-g-t-m from sievers@chromium.org
Link to the patchset: https://codereview.chromium.org/1040393002/#ps40001
(title: "Fixed build errors")

[commit-bot: I haz the power, 2015-04-08 09:21:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1040393002/40001

[commit-bot: I haz the power, 2015-04-08 11:48:14]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-04-08 11:48:59]

Patchset 3 (id:??) landed as
https://crrev.com/f9747e19ad48dfb99c3a4a09e690d67502204cd7
Cr-Commit-Position: refs/heads/master@{#324214}