| Index: ppapi/api/pp_completion_callback.idl
|
| diff --git a/ppapi/api/pp_completion_callback.idl b/ppapi/api/pp_completion_callback.idl
|
| index 46b6342aa2b83b6a53579f66162bef57636f343b..72aed837704b6ed4b5ab679623f54e0ba0c0329f 100644
|
| --- a/ppapi/api/pp_completion_callback.idl
|
| +++ b/ppapi/api/pp_completion_callback.idl
|
| @@ -70,7 +70,7 @@ enum PP_CompletionCallback_Flag {
|
| * callback, and the callback will be invoked later (barring
|
| * system or thread shutdown; see PPB_MessageLoop for details).
|
| * Required callbacks are the default.
|
| - *
|
| + * <br /><br />
|
| * NOTE: If you use a required callback on a background thread,
|
| * you must have created and attached a PPB_MessageLoop.
|
| * Otherwise, the system can not run your callback on that thread,
|
| @@ -87,7 +87,7 @@ enum PP_CompletionCallback_Flag {
|
| * callbacks, but can provide better performance for some APIs
|
| * (especially APIs with buffered reads, such as PPB_URLLoader or
|
| * PPB_FileIO).
|
| - *
|
| + * <br /><br />
|
| * NOTE: If you use an optional callback on a background thread,
|
| * and you have not created and attached a PPB_MessageLoop, then
|
| * the method you invoke will fail without running and return
|
| @@ -98,10 +98,10 @@ enum PP_CompletionCallback_Flag {
|
| * run to completion and return an appropriate code when finished
|
| * (see below for more information). Blocking completion
|
| * callbacks are only supported on background threads.
|
| - *
|
| + * <br /><br />
|
| * <code>PP_BlockUntilComplete()</code> provides a convenient way
|
| * to specify blocking behavior. Refer to
|
| - * <code>PP_BlockUntilComplete</code> for more information.
|
| + * <code>PP_BlockUntilComplete</code> for more information.
|
| *
|
| * When the callback is run asynchronously, the result parameter passed to
|
| * <code>func</code> is an int32_t that, if negative indicates an error code
|
|
|