Fix Graphics2D in NaCl.

Fix Graphics2D in NaCl.

This makes Graphics2D resource creation no longer under the "dev" flag.

It also makes binding a graphics context non-synchronous. It doesn't need to be synchronous other than returning success/failure, which almost nobody will check anyway, and most success/failure cases we can detect in the proxy anyway. Doing this prevents the synchronous bind from racing with the async creation in the nested-message-loop case which can run sync messages out-of-order.

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=170841

[bbudge, 2012-12-03 21:16:54]

LGTM with a comment

https://codereview.chromium.org/11308332/diff/1/ppapi/proxy/ppb_instance_prox...
File ppapi/proxy/ppb_instance_proxy.cc (right):

https://codereview.chromium.org/11308332/diff/1/ppapi/proxy/ppb_instance_prox...
ppapi/proxy/ppb_instance_proxy.cc:815: enter.functions()->BindGraphics(instance,
device);
Maybe a comment that we're discarding the return value here, and why that's OK.