[mollykreis]

Pull Request

🤨 Rationale

The blur events on components in NimbleBlazor cause the component to re-render when they are fired. In most cases, this isn't a problem because the component re-rendering when it is blurred isn't noticeable. However, for some parent components (like the NimbleDialog), it causes problems because the whole subtree is re-rendered when the dialog is blurred. This means that if it is blurred by an action not represented in the component bindings, such as opening a select, that action is lost.

👩‍💻 Implementation

• Add a new EventUtilities internal static class to NimbleBlazor that is heavily based on Microsoft docs (only changes are to satisfy the repo's lint rules)
• Update all blur events in NimbleBlazor to use the new EventUtilities helpers to keep the blur event firing from causing a component render

🧪 Testing

Manually tested in the example app the known problematic scenario, which is multiple selects in a dialog. Without this change, opening a select takes 2 clicks because a blur event on the dialog causes the select to render immediately after it is opened (rendering in the closed state). With this change, that no longer occurs.

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.