mus_browser_tests are passing on "linux_chromium_chromeos_ozone_rel_ng" where it's built/isolated on the same bot. The test is failing on "Linux ChromiumOS Ozone Tests (1)" where it's isolated but it gets built on "Linux ChromiumOS Ozone Builder". Is it possible that some manifest isn't getting copied between the two trybots?

Maybe? We don't currently report successful manifest connections. Only failures.

With the first test passing I think at least one of the parallel runs has access to the manifest.

I think it's crashing because the TextInputState mojom doesn't match the enum. If this is in fact causing the crash, then https://chromium-review.googlesource.com/c/570056/ should fix it.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1bd7abc4753464b2af466ba95eb6ccd9327f76f0

commit 1bd7abc4753464b2af466ba95eb6ccd9327f76f0
Author: Antonio Gomes <tonikitoo@igalia.com>
Date: Mon Jul 17 04:44:48 2017

Add entries for content editable and date/time field in Mojo's text input state

Both chrome --mash and chrome --mus --use-ime-service use
InputMethodMus for IME. In such cases, pages with 'content editable'
elements simply hang with the following error and stack trace:

  [ERROR:validation_errors.cc(90)] Invalid message: VALIDATION_ERROR_UNKNOWN_ENUM_VALUE

  #1 0x56228f4e5a9e mojo::internal::ReportValidationError()
  #2 0x56228c7ee648 mojo::internal::TextInputState_Data::Validate()
  #3 0x56228c7e2da9 ui::mojom::internal::WindowTree_SetImeVisibility_Params_Data::Validate()
  #4 0x56228c9dfbe2 ui::mojom::WindowTreeRequestValidator::Accept()
  #5 0x56228f4d423c mojo::FilterChain::Accept()
  #6 0x56228f4d5755 mojo::InterfaceEndpointClient::HandleIncomingMessage()
  #7 0x56228f4dc84c mojo::internal::MultiplexRouter::ProcessIncomingMessage()
  #8 0x56228f4dc03f mojo::internal::MultiplexRouter::Accept()
  #9 0x56228f4d4256 mojo::FilterChain::Accept()
  (...)

This happens because in InputMethodMus::UpdateTextInputType,
ui::TextInputType::TEXT_INPUT_TYPE_CONTENT_EDITABLE is the value
(correctly) used to construct the mojo::TextInputState instance
to be sent to Mus.
Down the road, WindowTreeClient::SetImeVisibility calls out to Mus
passing the mojo::TextInputState instance created previously.

At the mojo validation step, it fails (see stack above) because
text_input_state.mojom does not declare CONTENT_EDITABLE
(see IsKnownValue impl in <out>/gen/ui/platform_window/mojo/text_input_state.mojom-shared-internal.h).

Patch fixes this by syncing up ui::TextInputType, blink::WebTextInputType
and mojo::TextInputType.

PS: For the sake of completeness, DATE_TIME_FIELD enum item was added,
    and mojo::TextInputType::LAST is renamed to ::MAX in order to be able to
    compile assert it against ui::TEXT_INPUT_TYPE_MAX.

TEST=load any page with 'contenteditable' attr, in chrome --mash.

BUG= 718105 , 742491 

Change-Id: Icbea847e7fc655ca3c04243fefb8d67abaaa9239
Reviewed-on: https://chromium-review.googlesource.com/570056
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487025}
[modify] https://crrev.com/1bd7abc4753464b2af466ba95eb6ccd9327f76f0/ui/platform_window/mojo/OWNERS
[modify] https://crrev.com/1bd7abc4753464b2af466ba95eb6ccd9327f76f0/ui/platform_window/mojo/ime_type_converters.cc
[modify] https://crrev.com/1bd7abc4753464b2af466ba95eb6ccd9327f76f0/ui/platform_window/mojo/text_input_state.mojom