What to make of a draggable bottom sheet when there is no need to drag it?

[JayPanoz]

This is opening a can of worms but here we go. As a reminder:

• the bottom sheet draggability is set through preferences with a min-, peek- and max-height;
• the settings and their order are customisable in preferences too so we render these dynamically.

In EPUB, you would have an idea of what preferences to set depending on each action. And Customisable settings aren’t necessarily a concern.

Typically you would have a scrollable area where draggability makes sense:

The Web Publication prototype made the issue clearer since we will have settings available based on displayTransformability in publication.metadata.accessibility. And the complication is that of course an implementer can decide to not provide these settings, leaving with only zoom for instance.

In other words, it could look like this at peek height:

While the content perfectly fits at min height:

And does not make any sense at max-height:

In other words, it could be sized based on content-height in that case.

The challenge is that we do not know ahead of time. We only know once the bottom sheet and its contents are effectively rendered.

[HadrienGardeur]

I guess we could let the app control that by making this optional.

In the case of a Web Publication, the app will know whether it's display transformable for example.