About https://github.com/mdn/content/pull/34087/files, I guess that behavior is required per the spec? I can’t find where in the spec that behavior is defined.

That is, specifically this part:

<meta> redirect happens after the page is completely loaded, which is after all scripts have executed

I guess https://html.spec.whatwg.org/multipage/document-lifecycle.html#refresh could be possibly be sort of intentionally misread to state that meta http-equiv="refresh" should be handled in the loading process in the same way that the Refresh header is handled — but that doesn’t seem to be at all what the spec actually says (instead, it’d sort of be backward with the respect to how the spec actually does describe the relationship between the two) —

The Refresh HTTP response header is the HTTP-equivalent to a meta element with an http-equiv attribute in the Refresh state. It takes the same value and works largely the same. Its processing model is detailed in create and initialize a Document object.

OK, it’s since been pointed out to me that the relevant requirements are in fact already in the spec, in the definition of “a refresh is said to have come due” in step 13 of https://html.spec.whatwg.org/multipage/semantics.html#attr-meta-http-equiv-refresh

For the purposes of the previous paragraph, a refresh is said to have come due as soon as the later of the following two conditions occurs:

• At least time seconds have elapsed since document's completely loaded time, adjusted to take into account user or user agent preferences.
• If meta is given, at least time seconds have elapsed since meta was inserted into the document document, adjusted to take into account user or user agent preferences.

annevk: https://github.com/whatwg/html/issues/10407#issuecomment-2164768308

i feel like i did answer the actual question you asked about what happened to it, which is all i was trying to add.. 😋