fix: [#1847] Navigation with location.href now adds to history

[TrevorBurnham]

Closes #1847

Problem

Setting location.href doesn't increment history.length. The href setter calls browserFrame.goto() → BrowserFrameNavigator.navigate(), which pushes to history for full navigations. However, when using a detached window (e.g. new Window(), the common test scenario), validateFrameNavigation() returns false and the code falls through to a path that only updates the URL via setURL() without pushing a history entry.

Changes

packages/happy-dom/src/browser/utilities/BrowserFrameNavigator.ts

• In the validateFrameNavigation fallback path (used by detached windows), push a history entry before calling setURL(), matching the behavior of the normal navigation path.

packages/happy-dom/test/history/History.test.ts

• Added test verifying history.length increases after setting location.href on a detached window.

[capricorn86]

History should not be changed when inside a window of a DetachedBrowser as there is no navigation happening. The user stays on the same page. For it to work with unit tests, it can fallback to setting the current URL without navigating.

[TrevorBurnham]

History should not be changed when inside a window of a DetachedBrowser as there is no navigation happening.

But it's already the case that history.pushState() (for example) works in DetachedBrowser. Why would we simulate realistic behavior for that method but not for the href setter?