Status Update
Comments
ia...@google.com <ia...@google.com> #2
That's working as expected. Let's consult with Javier about his thoughts.
tr...@google.com <tr...@google.com> #3
Did we get any input from Javier for this?
tr...@google.com <tr...@google.com> #4
The current implementation after the fix is aligned with the foundation API AnchoredDraggable
- I think it makes sense to provide an optional parameter for devs to provide the initial anchor to use, as it's hard to provide a reasonable default.
Let me know if you have different thoughts. : )
ma...@google.com <ma...@google.com> #5
I think it makes sense to provide an optional parameter for devs to provide the initial anchor to use, as it's hard to provide a reasonable default.
That sounds reasonable to me. Is there a separate bug for that or should I file one?
One thing that I think will be weird is that the size of the panes can come from that anchor or from PaneScaffoldDirective defaultPanePreferredWidth (possibly influenced by the hinge?). In an ideal world, I think we would have the sizes all come from anchors, but that wouldn't work today with three panes visible. I'll add a note to the doc on this.
ma...@google.com <ma...@google.com>
ma...@google.com <ma...@google.com>
na...@google.com <na...@google.com> #6
We don't have a separate bug for that but it's already being supported via:
rememberPaneExpansionState(
...
initialAnchoredIndex = i,
)
You raised a very good point about having parallel ways to set up pane sizes.
To me it's sort of reasonable as there are actually referring to different use cases and have different priorities -
- Hinge policies always have the highest priority.
- Pane expansion (and its anchors) are associated with layout splits, but less with the "roles" of the panes that occupy those splits.
Modifier.preferredWidth
always has the lowest priority - more like a fallback default.
I guess we can have more detailed explanation in the doc if this can be confusing?
Description
1.1 snapshot: 12421028
If you enable predictive back and use a
NavigableListDetailPaneScaffold
, dragging the gesture to start it and then moving back to the original position to release and cancel it results in a weird limbo state. The modifiers from the list pane will be used but the content won't, so it doesn't seem to reset to details correctly.Sample code: