Remove outdated statement that browsers tend to handle the popstate event differently on page load (mdn#43373)

* Update popstate event handling details mdn#43368

Updated the section on the handling of popstate event on page load across different browsers.

Closes mdn#43368

* Update files/en-us/web/api/window/popstate_event/index.md

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Remove outdated information about popstate event handling on page load.

based on review comment mdn#43373 (review)

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: johanrd

files/en-us/web/api/window/popstate_event/index.md

@@ -47,8 +47,6 @@ These methods and their corresponding events can be used to add data to the hist
 
 Note that just calling `history.pushState()` or `history.replaceState()` won't trigger a `popstate` event. The `popstate` event will be triggered by doing a browser action such as a click on the back or forward button (or calling `history.back()` or `history.forward()` in JavaScript).
 
-Browsers tend to handle the `popstate` event differently on page load. Chrome (prior to v34) and Safari always emit a `popstate` event on page load, but Firefox doesn't.
-
 > [!NOTE]
 > When writing functions that process `popstate` event it is important to take into account that properties like `window.location` will already reflect the state change (if it affected the current URL), but `document` might still not. If the goal is to catch the moment when the new document state is already fully in place, a zero-delay {{domxref("Window.setTimeout", "setTimeout()")}} method call should be used to effectively put its inner _callback_ function that does the processing at the end of the browser event loop: `window.onpopstate = () => setTimeout(doSomeThing, 0);`