Releases: bUnit-dev/bUnit
1.18.4
Fixed
- Some characters where not properly escaped. Reported by @pwhe23. Fixed by @linkdotnet.
- Clicking a submit button or submit input element inside a form, submits the form, if the submit button or submit input element does not have the
@onclick:preventDefaultattribute set. Reported by @linkdotnet. Fixed by @egil.
1.17.2
- Submit buttons and input fields now no longer cause a form submit when they have the
@onclick:preventDefaultattribute. By @JelleHissink.
1.16.2
- Changed semantic comparer to handle elements parsed outside their proper context, e.g. an
<path>element parsed without being inside a<svg>element. The semantic comparer will now be able to treat those as regular elements and thus be able to compare correctly to other elements of the same type and with the same node name. By @egil.
1.15.5
- Upgrade AngleSharp.Diffing to 0.17.1
1.14.4
Added
- Added
IMemoryCacheby default to the Services container. By @linkdotnet.
Fixed
- Added support in
FakeNavigationManagerto handle umlauts. - Fixed a bug where attribute values did not get escaped. Reported by @brettwinters. Fixed by @linkdotnet.
1.13.5
This release contains a bunch of small tweaks and fixes.
1.12.6
Fixed
- The created HTML contained encoded strings. Reported by @tobiasbrandstaedter. Fixed by @linkdotnet.
1.11.7
Added
- Added the
StateFromJsonmethod to theNavigationHistorytype, to make it easy to deserialize navigation state stored as JSON during a call toNavigationManager.NavigateTo, e.g. as seen with the newInteractiveRequestOptionstype available in .NET 7. By @linkdotnet and @egil.
1.10.14
Added
-
Added new test double
FakeWebAssemblyHostEnvironmentthat implementsIWebAssemblyHostEnvironment. By @KristofferStrube. -
Added
Bindmethod to parameter builder that makes it easier to emulate the@bind-Valuesyntax in C#-based tests.When writing tests in razor files, the
@bind-directive can be directly applied like this:<MyComponent @bind-Value="myParam"></MyComponent>
The same expression in C# syntax is more verbose like this:
RenderComponent<MyComponent>(ps => ps .Add(c => c.Value, value) .Add(c => c.ValueChanged, newValue => value = newValue) .Add(c => c.ValueExpression, () => value));
With the new
Bindmethod this can be done in one method:RenderComponent<MyComponent>(ps => ps .Bind(c => c.Value, value, newValue => value = newValue, () => value));
By @linkdotnet and @egil.
-
Added support for
NavigationLock, which allows user code to intercept and prevent navigation. By @linkdotnet and @egil.
Fixed
JSInterop.VerifyInvokereported the wrong number of actual invocations of a given identifier. Reported by @otori. Fixed by @linkdotnet.
1.9.8
Changed
WaitForAssertionmethod is now marked as an assertion method with the[AssertionMethod]attribute. This makes certain analyzers like SonarSource's Tests should include assertions happy. By @egil.
Fixes
-
A race condition existed between
WaitForState/WaitForAssertionandFindComponents, if the first used the latter. Reported by @rmihael, @SviatoslavK, and @RaphaelMarcouxCTRL. Fixed by @egil and @linkdotnet. -
Triggering of event handlers now runs entirely inside the renderers synchronization context, avoiding race condition between elements in the DOM tree being updated by the renderer and the event triggering logic traversing the DOM tree to find event handlers to trigger. Reported by @FlukeFan. Fixed by @egil.