Open chunhtai opened 4 years ago
cc @LongCatIsLooong
I ping the wrong issue in my PR please ignore
@chunhtai is this high priority?
raise to P1 according to the discussion in b/166068876
@LongCatIsLooong says he's currently working on this.
(issue triage): According to @LongCatIsLooong we are waiting for clarification from the customer.
I've lowered this issue's priority pending getting some additional clarity about exactly what's going wrong in the customer's app and what a practical solution would be.
The wait label hit timeout but since this is reproducible I'll leave this open.
Hi @mehmetf , we are waiting for the respond in the internal issue.
Thanks. This was part of an automated update. I lowered the priority of the internal bug (which is considered the source of truth for priorities).
Reproduces on the latest versions of flutter using the code sample provided in https://github.com/flutter/flutter/issues/64973#issue-689509515
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
CC @LongCatIsLooong
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
CC @LongCatIsLooong
For future reference, a pinned header doesn't expand until you scroll the scroll view to the start. We need to distinguish "show on screen" and "fully expand", since the latter would also imply that scroll view be scrolled to the start -- a side effect that could be annoying for the user to undo if they're 100 pages in.
The closed PR would allow a pinned header to fully expand when showOnScreen
is called, without scrolling to the start, but I wasn't sure that's the right change to make, I wonder if the material spec has related guidelines.
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
I have lowered the priority here since this is no longer blocking the customer. It was also discussed in the internal issue that this behavior actually matches native iOS behavior, in that the header receiving focus does not cause it to expand.
Internal: b/168395763
Steps to Reproduce
expect: collapsed header should be expended when it has the focus actual: header still collapses when focused.
the bug seemed to be introduced in https://github.com/flutter/flutter/commit/fe55dc2b135b5b71ae3c19062b34dc6e8d02e9d5