revert commit 1fe19578c2 which changed `anchor()` values to `position-area`.
I'm not sure what compelled me to do that change initially, except the easier to understand syntax. Hopefully it wasn't important.
But oddbird polyfill expects `anchor()` values, which it converts to pixel values for positioning.
This updates the position try results by using a different method of setting the area of the anchored element. Rather than using the inset properties with `anchor()`, it uses `position-area`.
Largely this is written by an LLM after I provided the targets, and I've looked through the tests themselves to confirm they are accurate. There may be improvements in how to actually *set up* the tests, though, as I am less familiar with those.
This has two test suites: the first for html structure, the second for behavior. Each of them calls another script that provides helper functions for setting things up and taking them down. This keeps the test suites themselves fairly lean.
This fixes the odd alignments of menu-wrapper names by ensuring that both menuitems and menu-wrappers (actually their child triggers) both have space for icons.
Unless a menu item has the `no-dismiss` attribute (set to either `''` or `'true'`), clicking a menu item will dismiss the menu. Clicking a submenu trigger will not dismiss the menu.
The `no-dismiss` attribute must take a string, either empty or `'true'` because react doesn't allow boolean custom attributes.
Ideally side effects (server calls, etc.) should happen outside of useEffect anyway for reasons like this; Putting the save in the button click keeps the logic in one place instead of spread across multiple functions and renders,
(This change was already made in my local copy toward combining Edit/New/Home pages.)
Gazook89