Mega Menu Block: Front-end rendering does not match editor preview

[allancole]

Description

Multiple styling and functionality issues exist in the mega menu plugin where the front-end output significantly differs from the back-end editor preview. Content within the mega menu displays incorrectly on the front-end, including misaligned list items, missing list styles, and hidden nested navigation blocks.

Current Behavior

1. Layout/Styling Mismatch

• List items inside the mega menu appear right-aligned on the front-end despite being left-aligned in the editor
• List items are missing bullet styles on the front-end
• List items are colliding/overlapping with each other ("bumping into the next one")
• Heading blocks (H3, H4) also render as right-aligned on the front-end even when explicitly set to left-align in the editor

2. Navigation Block Hidden Inside Mega Menu

• When placing a Navigation block inside the mega menu, it is completely hidden on the front-end
• The markup is present in the DOM (visible in browser inspector) but the element appears to be hidden via CSS or other means
• No visible error or warning in the editor

3. Page List Block: Parent Not Displayed

• When using a Page List block configured to show children of a specific parent page, the parent page itself is not displayed
• Users must manually add a heading block to label the section
• (Note: This may be a Gutenberg core issue rather than plugin-specific)

4. No Option for Expanded Child Menus by Default

• There is no way to display Navigation block submenus expanded by default (without hover/click interaction)
• All child menu items are hidden behind overlay dropdowns
• (Note: This may be a core Navigation block limitation)

Screenshot:

Editor	Frontend

Expected Behavior

1. Layout Consistency: Front-end rendering should match editor preview exactly—list items should be left-aligned with visible bullet points and proper spacing
2. Navigation Block Visibility: Navigation blocks placed inside the mega menu should render and be visible on the front-end
3. Page List Parent Display (likely a core issue): When selecting a parent page to show its children, the parent page title should optionally be displayed (or this behavior should be documented)
4. Expanded Submenus Option (likely a core issue): Users should have the ability to display child menu items in an expanded state by default, without requiring hover/click interaction

Steps to Reproduce

For Layout Issues:

1. Create a mega menu using the plugin
2. Add a Columns block inside the mega menu
3. Add a Page List block in each column, configured to show children of a parent page
4. Add a Heading block (H3 or H4)
5. Set text alignment to left in the editor
6. Save and view on the front-end
7. Observe: List items are right-aligned, missing bullets, and colliding; headings are also right-aligned

For Hidden Navigation Block:

1. Add a Navigation block inside the mega menu
2. Save and view on the front-end
3. Observe: Navigation block is not visible (inspect DOM to confirm markup exists but is hidden)

Acceptance Criteria

• List items inside the mega menu render with correct alignment (matching editor) on front-end
• List styles (bullets) are preserved on front-end
• List items have proper spacing and do not collide
• Heading blocks respect text alignment settings on front-end
• Navigation blocks placed inside the mega menu are visible and functional on front-end
• Document or address Page List parent display behavior
• Investigate feasibility of "always expanded" option for child menu items

Additional Context

• Some issues (Page List parent display, expanded submenus by default) may be Gutenberg core limitations rather than plugin bugs—these should be triaged accordingly