[lexical-react] fix: ensure attributes are set immediately on menu

[sodenn]

Description

With the changes introduced in Lexical 0.25.0 (notably #7181 and #7164), the menu now renders immediately. However, this has led to two issues:

1. Missing attributes on initial render
The menu container <div> is rendered before its attributes are assigned. As a result:

• Styles defined via anchorClassName are not applied immediately, causing visibility issues. The attributes only appear after the user makes further inputs. In my case, the menu is covered by a dialog because the z-index from my custom class is not applied initially.
• Other missing attributes, such as role and aria-label, make automated testing more difficult.

2. Persistent DOM Element (not addressed in this PR)
The menu container <div> remains in the DOM even when the menu is closed. This can lead to duplicate IDs, potentially causing accessibility and testing issues.

Fix in This PR
This PR ensures that all attributes are correctly assigned as soon as the menu is rendered.

Before

After

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lexical	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 24, 2025 5:17pm
lexical-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 24, 2025 5:17pm

[etrepum]

As you've mentioned this does fix some problems, but other issues remain primarily due to the id conflict that now arises since all of the menus are rendered concurrently.

e.g. this code no longer works correctly (due to prior regressions):

const scrollIntoViewIfNeeded = (target: HTMLElement) => {
  const typeaheadContainerNode = document.getElementById('typeahead-menu');
  if (!typeaheadContainerNode) {
    return;
  }

[etrepum]

Perhaps a path for a short term fix might be to only assign the id to the active menu, so there's only one typeahead-menu in the document at a time. That probably wouldn't require changing the tests and other logic that depends on the typeahead-menu id

Test suite failures

[etrepum]

This looks good to me and seems to work well with manual testing in the playground, nice job! Will merge assuming the extended test suite is clear.

[etrepum]

Looks like there are some test failures, I don't think it's meaningful to perform this specific test on collab so we should just skip it there