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.

Sign up for GitHub

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

Jump to bottom

[Navigation Block][iPad]Menu remains open even if another is opened #82478

Closed
ricklabsdotn8 opened this issue Oct 2, 2023 · 4 comments
Closed

[Navigation Block][iPad]Menu remains open even if another is opened #82478

ricklabsdotn8 opened this issue Oct 2, 2023 · 4 comments
Assignees
@gikaragia
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Core Blocks Blocks that come with Gutenberg. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. Groundskeeping Issues handled through Dotcom Groundskeeping rotations Needs retest Flagged for retesting by Quality Engineering [Platform] Simple [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug

Comments

@ricklabsdotn8
Copy link

Quick summary

The submenu remains open even when another submenu is opened on iPad.

Navigation.Block.Submenu.Issue.mp4

[Test on Browserstack]

Steps to reproduce

  1. Go to Appearance → Editor → Navigation
  2. Modify the Navigation so that each menu item has sub-items
  3. Preview page on iPad
  4. Click on dropdown arrow
  5. Click on another dropdown arrow

What you expected to happen

The previous dropdown that is open should close

What actually happened

The dropdown remains open

Impact

Some (< 50%)

Available workarounds?

No but the platform is still usable

Platform (Simple and/or Atomic)

Simple

Logs or notes

7071962-zen
@ricklabsdotn8 ricklabsdotn8 added [Type] Bug Needs triage Ticket needs to be triaged labels Oct 2, 2023
@github-actions github-actions bot added [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts [Platform] Simple [Pri] High Address as soon as possible after BLOCKER issues labels Oct 2, 2023
@github-actions
Copy link

github-actions bot commented Oct 2, 2023

Support References

This comment is automatically generated. Please do not edit it.

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Oct 2, 2023
@cuemarie
Copy link

cuemarie commented Oct 2, 2023 •
edited
Loading

📌 REPRODUCTION RESULTS

  • Tested on Simple – Replicate
  • Tested on Atomic – Replicated
  • Replicable outside of Dotcom – Yes

📌 FINDINGS/SCREENSHOTS/VIDEO
I'm able to replicate this using my (Firefox) browser's responsive tools across Simple, Atomic and simple Self-Hosted test sites. It appears to get worse the more I scroll/use the menu items on the page - below is a comparison of all 3 environments:

Simple , Atomic, Self-Hosted

DHfWr7.mov

Simple

Gutenberg: v16.6.0
Editing Toolkit: v3.80059
WP AMP: 2.0.5
Theme: TwentyTwenty-Three

Atomic

WP 6.3.1
Gutenberg: v16.6.0
Editing Toolkit: v3.80059
Theme: TwentyTwenty-Three

Self-Hosted

WP 6.3.1
Gutenberg: v16.7.0
Theme: TwentyTwenty-Three

📌 ACTIONS

@cuemarie cuemarie added [Pri] Normal Schedule for the next available opportuinity. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Core Blocks Blocks that come with Gutenberg. and removed [Pri] High Address as soon as possible after BLOCKER issues Needs triage Ticket needs to be triaged [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts labels Oct 2, 2023
@cuemarie cuemarie moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Oct 3, 2023
@cuemarie
Copy link

WordPress/gutenberg#55198 aims to fix this in GB 16.9

@cuemarie cuemarie added the Needs retest Flagged for retesting by Quality Engineering label Oct 18, 2023
@mrfoxtalbot mrfoxtalbot moved this to To triage in Dotcom Core Fix Needed Sep 2, 2024
@gikaragia gikaragia self-assigned this Sep 5, 2024
@gikaragia
Copy link
Contributor

gikaragia commented Sep 5, 2024 •
edited
Loading

This is now fixed by WordPress/gutenberg#55198

@gikaragia gikaragia added the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gikaragia gikaragia

Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Core Blocks Blocks that come with Gutenberg. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. Groundskeeping Issues handled through Dotcom Groundskeeping rotations Needs retest Flagged for retesting by Quality Engineering [Platform] Simple [Pri] Normal Schedule for the next available opportuinity. [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug
Projects
Automattic Prioritization: The One Board ™
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cuemarie @gikaragia @ricklabsdotn8