GitLab

This CL shapes the role of a KeyboardAccessoryData.Tab element:
It is an element that provides a specific benefit to the Manual UI by...
... providing data that is used by the bar to render a tab (upcoming)
... providing the content for a separate tab in the bottom sheet.

This means, that the bottom sheet provides space for tabs and manages the
general visibility and active states of tabs.
The exact content of a tab doesn't matter to the AccessorySheetComponent.
That way, it should become fairly straight forward to implement a new tab
that is rendered into bottom sheet and accessory.

The first concrete instance of a bottom sheet will follow soon: a
bottom sheet that contains password related actions and data.
(It's important to not mix this specific data into the AccessorySheet
component as other upcoming sheets are already planned, like one for
payments and one for address data.)

Bug: 811747
Change-Id: Id8bd8c389496246166d26a6c298056a142c36566
Reviewed-on: https://chromium-review.googlesource.com/1047285
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#559180}