Hold on until I do another commit. Found another issue and fixing it too.

@versile2 u can now update your branch and get the UnitTests.Viewer improvements. Either rebase or use "update branch" below.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.18%. Comparing base (fb91812) to head (a21b27c).
Report is 3 commits behind head on dev.

@@            Coverage Diff             @@
##              dev   #10106      +/-   ##
==========================================
- Coverage   91.18%   91.18%   -0.01%     
==========================================
  Files         411      411              
  Lines       12483    12483              
  Branches     2429     2429              
==========================================
- Hits        11383    11382       -1     
  Misses        557      557              
- Partials      543      544       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

All good now, repositioned popovers were continuing when it would be scrolled off screen.

Seeing this on the Select examples

https://mudblazor.com/components/select#multiselect-customized-selection-text

looking, were there any changes to select besides my popover changes? I'm not saying they didn't but mine should not have caused this type of action (in my testing this is similar to what happens when two popoverproviders that don't error out).

Seeing this on the Select examples

https://mudblazor.com/components/select#multiselect-customized-selection-text

looking, were there any changes to select besides my popover changes? I'm not saying they didn't but mine should not have caused this type of action (in my testing this is similar to what happens when two popoverproviders that don't error out).

There was #10071 but it worked as of that PR

Unable to interact with the the docs search results since #10089 on my end and appears to still be an issue with this PR at the moment

Seeing this on the Select examples

https://mudblazor.com/components/select#multiselect-customized-selection-text

looking, were there any changes to select besides my popover changes? I'm not saying they didn't but mine should not have caused this type of action (in my testing this is similar to what happens when two popoverproviders that don't error out).

There was #10071 but it worked as of that PR

It works fine for me? Also I've narrowed down the oddity only to mudselects with an AnchorOrigin set to Bottom Center where Transform Origin isn't set. I will get back to it when I get back.

There was #10071 but it worked as of that PR

It works fine for me? Also I've narrowed down the oddity only to mudselects with an AnchorOrigin set to Bottom Center where Transform Origin isn't set. I will get back to it when I get back.

I'm not sure the select was indeed broken by the #10089
I'm still in process of git bisect, I will let ya all know what commit broke it 100%

@danielchalmers was your commit "Inputs, Menu: Standardize default origin point (#10071)" that broke it.
Bisect showed that, and then I double checked by manually reverting your commit from the current head and checked that it fixes it, then i returned your commit and it's broken.

@versile2 pls do not work on the select problem from the popover perspective, as @danielchalmers probably has to fix it.

Unable to interact with the the docs search results since #10089 on my end and appears to still be an issue with this PR at the moment

Working for me with #10089, didn't check it with this commit yet.

upd: yea I have no problem with interacting the menu like on the video even with this PR

Just for the record as I think about it I believe @danielchalmers actually fixed something someone had broken and these examples are set manually to bottom center. Which is exactly what's happening it's opening bottom center.

Just for the record as I think about it I believe @danielchalmers actually fixed something someone had broken and these examples are set manually to bottom center. Which is exactly what's happening it's opening bottom center.

That makes sense. I'll update the examples

Just to confirm I don't need to do anything else with this correct?

Tried again, still unable to interact with autocomplete popovers. Tested in the Wasm project and the test viewer

#10106 (comment)

I'm not having any issues, to my knowledge the others aren't either? Your video didn't show up so I can't see from that.
I may be in the dark here, but if you can point me into something I can look into it I'll work on fixing it.

@ScarletKuro feel free to merge

@henon @ScarletKuro I'll merge it as everyone seems satisfied

Wow, weird. It's working on my other computer so I'll just approve it if it's working for everyone else. Will have to figure out what's up with my desktop!

Have you tried to clean build + incognito + different browser? Little worried it doesn't work on your PC

Wow, weird. It's working on my other computer so I'll just approve it if it's working for everyone else. Will have to figure out what's up with my desktop!

Have you tried to clean build + incognito + different browser? Little worried it doesn't work on your PC

Clearing build, cache, etc did the trick