+ Khalil who's working on the messaging/interventions UX project.

Thanks for flagging this Matt - I added you to an older thread discussing this very issue. 

This behavior is not unique to the new Translate infobar. From Ariel: "Infobars show in the order they are triggered. TLDR is that there isn't a prioritization based on infobar content, it's just the order in which they're triggered...* Layout that displays infobars in a stack. Handles all the animations when adding or removing * infobars and when swapping infobar contents. * * The first infobar to be added is visible at the front of the stack. Later infobars peek up just * enough behind the front infobar to signal their existence; their contents aren't visible at all. * The stack has a max depth of three infobars. If additional infobars are added beyond this, they * won't be visible at all until infobars in front of them are dismissed."

In previous discussion we talked about potentially stacking based on content instead of triggering order. 

I might suggest that from an EM perspective, this may be particularly problematic as I would expect the Translate and Data Saver infobars to show up on a lot of pages at the same time. Perhaps we have metrics that tell us how serious the problem is in practice.

To the best of my knowledge, we don't have metrics on this (i.e. concurrent Translate AND Previews). I am also pretty concerned about this with regard to EM users, particularly since the Previews infobar doesn't auto-dismiss. 

Khalil - do you have any updates in the state of the messaging/interventions UX project? 

Yana - No concrete mocks for this occurrence as of now. It's on my radar and I'll bubble this up as a top priority. I put some time down for us to chat about this in detail tomorrow. 

We can probably estimate how many pageloads or users are affected by this if you have UMA metrics on when the Translate infobar is shown (we have UMA on the Data Saver infobar). Can you tell me what that UMA is and I can run some queries?

Sorry Leo looked at this yesterday and I meant to share this here: based on latest 7 days for stable versions, ~38% Translate infobars were shown behind other infobars. We used InfoBar.Shown.Hidden("TRANSLATE_INFOBAR_DELEGATE") and InfoBar.Shown.Visible("TRANSLATE_INFOBAR_DELEGATE") to get to this number.

That sounds pretty serious then. Do we have metrics on how often the occluding infobar is closed by the user allowing Translate to be revealed?

Not directly AFAIK.

Hey Khalil, has any progress been made in the UI world on solving this issue?

I've been full-time on Bling for the past quarter — I haven't had a chance to revisit this beyond my initial Messages UI exploration a few months back: https://docs.google.com/presentation/d/1bqJwXvJ0DW4WeJRD5Tk9H5DQ-ywzMZNT2ebgX4y5OB4/edit#slide=id.g25f1ae45ff_0_137

Happy to discuss potential solutions in person :)

Issue 829966 has been merged into this issue.