[Nearby] Reland: Validate device name in onboarding.
The original change was reverted due to a test failing on linux-chromeos-dbg. Reverted here: https://chromium-review.googlesource.com/c/chromium/src/+/2448510 The fix was to remove the browsePreload() override so that the test starts on chrome://os-settings to ensure that strings.m.js is loaded. Original change's description: > [Nearby] Validate device name in onboarding. > > This adds support for validating the device name that a user enters > during the Nearby Share onboarding flow. Validation happens as the user > types and also when they try to proceed to the next screen. If an > invalid name is detected, an error message will appear and the "Next" > button will be disabled. > > Screenshots: > https://screenshot.googleplex.com/3USR7ftg7QCwJhR.png > https://screenshot.googleplex.com/6Cr6pedUxWnUKju.png > > Bug: b:169582004 > Change-Id: I07d4822e0ea099b30d23ed34a5f70f01940a3009 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441150 > Reviewed-by: Kyle Horimoto <khorimoto@chromium.org> > Reviewed-by: James Vecore <vecore@google.com> > Commit-Queue: Michael Hansen <hansenmichael@google.com> > Cr-Commit-Position: refs/heads/master@{#813193} Bug: b:169582004 Change-Id: I48e1aa7325db74f673cb3e6bc60de49ca8b7af9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448665Reviewed-by:Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Michael Hansen <hansenmichael@google.com> Cr-Commit-Position: refs/heads/master@{#814398}
Showing
Please register or sign in to comment