Open Bug 1918216 Opened 1 year ago Updated 3 months ago

Update Dropdown custom component to match M3 design

Categories

(Firefox for Android :: Design System and Theming, task)

All
Android
task

Tracking

()

People

(Reporter: npoon, Unassigned)

References

(Depends on 1 open bug, Blocks 6 open bugs)

Details

There were ideas mentioned in the comments in this patch of things that can be improved and what to look out for to ensure we don't introduce a regression. Also, consider making our Dropdown component more similar to the Material API so that we can easily swap it in in the future.

The current composable also requires parameters such as whether the device is in landscape orientation to help use the correct padding. It would be ideal if we didn't need this parameter as it makes the component less generic and more specific to the Translations use case.

We should also investigate whether the TextMeasurer is necessary to get the correct DropdownMenu width. Compose should be able to make the menu the correct size depending on the item inside.

Severity: -- → N/A
Depends on: 1917346
Summary: Investigate if we can modernize and simplify the `Dropdown` component → Investigate if the `Dropdown` component can be simplified and modernized
See Also: → 1919104
See Also: → 1953310
Blocks: 1975015

We now have a new design for the Dropdown to match M3 so we should now update the Dropdown from M2 to M3 in this ticket.

The new M3 dropdown uses the design of an outlined text field and a menu to make up the dropdown.

We need to keep in mind all of the different quirks of the current dropdown when updating it. There were a lot of things that were intentionally done (including for a11y) when the translations project was in progress

WebCompat Reporter dropdown
Menu
Text Field

Summary: Investigate if the `Dropdown` component can be simplified and modernized → Update Dropdown custom component to match M3 design
You need to log in before you can comment on or make changes to this bug.