Lines Matching +full:formatting +full:- +full:error +full:- +full:messages

39 * `foo_js` JavaScript bindings; used as compile-time dependency.
40 * `foo_js_data_deps` JavaScript bindings; used as run-time dependency.
44 ninja -C out/r services/echo/public/interfaces:interfaces_js
81   handle and dispatches incoming messages to a user-defined interface
118 example, binding/extracting `InterfacePtrInfo`, setting connection error
132 endpoint, dispatching incoming messages to the implementation.
146 error (unless the disconnection is caused by closing/destroying an endpoint, in
148 incoming messages for an endpoint on disconnection, the connection error won't
149 be triggered until the messages are drained.
152 * Mojo system-level causes: process terminated, resource exhausted, etc.
153 * The bindings close the pipe due to a validation error when processing a
158 Regardless of the underlying cause, when a connection error is encountered on
159 a binding endpoint, that endpoint's **connection error handler** (if set) is
176 **Note:** Closing one end of a pipe will eventually trigger a connection error
181 it observes the connection error.
187 Similar to the non-associated interface case, we have:
195   the connection and dispatches incoming messages to a user-defined interface
198 See [this document](https://www.chromium.org/developers/design-documents/mojo/associated-interfaces)
232 <!-- Automatic dependency loading -->
237 <!-- Manual dependency loading -->
253 <!-- Assume that mojo.config.autoLoadMojomDeps is set to true: -->
255 <!-- No duplicate loading; recommended. -->
258 <!-- No duplicate loading, although unnecessary. -->
262 <!-- Load bar.mojom.js twice; should be avoided. -->
263 <!-- when foo.mojom.js is loaded, it sees that bar.mojom.js is not yet loaded,
264      so it inserts another <script> tag for bar.mojom.js. -->
272 ## Name Formatting
273 As a general rule, Mojom definitions follow the C++ formatting style. To make
278 |----------------------|------------------------|