Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetpack Banner: Impossible to close it on mobile #101115

Open
zaguiini opened this issue Mar 10, 2025 · 2 comments
Open

Jetpack Banner: Impossible to close it on mobile #101115

zaguiini opened this issue Mar 10, 2025 · 2 comments
Labels
[Pri] Low Address when resources are available. [Status] Auto-allocated [Status] Escalated to Product Ambassadors Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@zaguiini
Copy link
Contributor

Context and steps to reproduce

During my tests, I wasn't able to see the "Continue in Browser" button and unable to pinch to zoom out and see the button. Clicking in the overlay also didn't close the banner.

Image

Site owner impact

Fewer than 20% of the total website/platform users

Severity

Critical

What other impact(s) does this issue have?

No response

If a workaround is available, please outline it here.

No response

Platform

No response

@Robertght
Copy link

I was able to replicate this but only after logging in the first time. I suppose we're doing some checks there.

@Automattic/t-rex since this appears to be related to the dashboard, would it be something for your team to look at?

I'm adding a Low priority to this.

@Robertght Robertght added [Pri] Low Address when resources are available. Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Mar 11, 2025
@Robertght Robertght moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Mar 11, 2025
@dsas
Copy link
Contributor

dsas commented Mar 11, 2025

@Automattic/t-rex since this appears to be related to the dashboard, would it be something for your team to look at?

Not especially, I don't think we've ever worked on the dashboard. I don't have any objection to someone on T-Rex taking a look though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Pri] Low Address when resources are available. [Status] Auto-allocated [Status] Escalated to Product Ambassadors Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests

4 participants