Mobile document's off-canvas menu drawer loses its menu list
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the materialization of the mobile document variant, where the div.mobile-menu drawer is built without its ul.menu list, and compare it with the desktop path that produces core/navigation. Reproduce with the 768px capture described in the issue and check the mobile drawer's block output for the 17 links. Done means the mobile drawer contains the same menu list as the captured page, and the duplicate-toggle behaviour in #2852 is not changed.
Written by the indexing model from the issue text.
Description
Summary
When a captured page ships a desktop and a mobile document, the mobile document's off-canvas menu drawer is materialized without its menu. The drawer wrapper and its search form survive, but the list (div.mobile-menu > div.animation-wrap > ul.menu > li > a, 17 links) becomes an empty group. The desktop document's copy of the same drawer keeps the list as core/navigation.
Evidence (captured site, 768px)
| capture (served statically) | import | |
|---|---|---|
| drawer, desktop document | 17 links | 11 links (core/navigation) |
| drawer, mobile document (the copy laid out at ≤1024px) | 17 links | 0 links (empty wp-block-group) |
The drawer is opacity:0 until its toggle opens it, so nothing looks different at rest. Once a toggle opens it, the mobile-width drawer is empty. The duplicate-toggle behaviour is tracked in #2852.
Expected
Each document variant's drawer keeps its own menu list, like other repeated variant content does.
AI disclosure: Claude (Anthropic) via Claude Code implemented this under Chris Huber's direction; operator-authorized direct fallback outside Homeboy.
- Dominant language
- PHP
- Stars
- 21
- Forks
- 2
- Avg merge
- 9h 6m
- Merged PRs (30d)
- 589
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Automattic/blocks-engine
-
Solved site promotion gate fails on runner PHP patch drift (expects 8.2.33, runner installs 8.2.34)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Automattic/blocks-engine#2161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/blocks-engine#2061 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Automattic/blocks-engine#1701 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Automattic/blocks-engine#775 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 75/100
Automattic/blocks-engine#3051 ·
Maintainers usually reply within 1 day
All issues in Automattic/blocks-engine
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nextcloud/integration_openai#446 ·
-
bug customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MagnaCapax/PMSS#1101 ·
Maintainers usually reply within 5 days
-
InvoiceSettled is answered 200 when the invoice cannot be re-fetched, so BTCPay never redelivers itOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
btcpayserver/woocommerce-greenfield-plugin#93 ·
Maintainers usually reply within 1 day
-
kind/bug status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100