@ojan: Regarding point 4: "Only show the latest redirection: close current infobar then show the new one with the new blocked redirection."
This is not very straightforward to do now, as mutating infobars is not supported by the current system. I could change that, but the way infobars work currently is closely tied to the deprecated desktop infobars and we plan to completely separate the Android ones from it soon. So I would prefer to not have to do work that we already plan to throw away.
The current behaviour is that we show an infobar for each redirection, the new ones stacking behind the currently shown infobar. They can be visible once the foreground one is closed. Considering how often this would happen I think the current state is acceptable until we have a decent path to implement the required behaviour. WDYT?
Re comment 6, this would effectively have the behavior of only showing the latest one, up until the user dismisses it. Is that accurate? That seems fine to me.
I feel like either showing the whole stack or showing the latest is fine. I think showing the first one is likely to be confusing because it's the one closest to the last action that they did that is most likely to be what they are aiming for.
But...honestly, it's so rare for there to be more than one that I think we are probably fine doing whatever as long as we UMA how often we would need to show more than 1 so we can verify that it's as rare as we think it should be.
re #c15: Actually been able to implement the infobar replacement concisely, so I didn't do the UMA to evaluate whether it's worth doing. Hope that's fine.
No more work planned for the Android UI for new, closing this bug.
Comment 1 by dgn@chromium.org
, Aug 15 201748.8 KB
48.8 KB View Download
109 KB
109 KB View Download