What is the issue with the HTML Standard?
In https://html.spec.whatwg.org/multipage/nav-history-apis.html#inner-navigate-event-firing-algorithm step 32.7, only navigationType "push" and "replace" are stated to run "URL and history update steps". However in the chromium implementation, it is also run for "reload" navigationType, and some WPT tests assume this behavior in order for them to pass. Shouldn't this be reflected in the spec?
Relevant commit from chromium's navigate_event.cc:
" // In the spec, the URL and history update steps are not called for reloads.
// In our implementation, we call the corresponding function anyway ."
What is the issue with the HTML Standard?
In https://html.spec.whatwg.org/multipage/nav-history-apis.html#inner-navigate-event-firing-algorithm step 32.7, only navigationType "push" and "replace" are stated to run "URL and history update steps". However in the chromium implementation, it is also run for "reload" navigationType, and some WPT tests assume this behavior in order for them to pass. Shouldn't this be reflected in the spec?
Relevant commit from chromium's navigate_event.cc:
" // In the spec, the URL and history update steps are not called for reloads.
// In our implementation, we call the corresponding function anyway ."