Ky sajt do të funksionojë me kufizime, teksa bëjmë mirëmbajtjen e tij për të përmirësuar punën tuaj. Nëse një artikull nuk e zgjidh problemin tuaj dhe dëshironi të bëni një pyetje, kemi bashkësinë tonë të asistencës, e gatshme për t’ju ndihmuar, te @FirefoxSupport në Twitter dhe/r/firefox në Reddit.

Avatar for Username

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Kjo rrjedhë është arkivuar. Ju lutemi, bëni një pyetje të re, nëse keni nevojë për ndihmë.

What is the expected navigation behavior of a 204 response to a form post.

  • 1 përgjigje
  • 0 e kanë hasur këtë problem
  • 1 parje
  • Përgjigjja më e re nga grimzecho

grimzecho
grimzecho
more options

According to Mozilla, the 204 No Content response "indicates that a request has succeeded but that the client doesn't need to navigate away from its current page".

However, when Firefox receives such a code in response to a status code, it triggers the `window.onbeforeunload` event and any associated handlers. This has side-effects such as closing any open websocket connections associated with the page, re-rendering the DOM (which fires various lifecycle methods in single page apps), and other similar activities that are generally associated with navigating away from a page.

Is this behavior intended or documented anywhere? Or should it be considered a bug?

According to Mozilla, the [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204 204 No Content] response "indicates that a request has succeeded but that the client doesn't need to navigate away from its current page". However, when Firefox receives such a code in response to a status code, it triggers the `window.onbeforeunload` event and any associated handlers. This has side-effects such as closing any open websocket connections associated with the page, re-rendering the DOM (which fires various lifecycle methods in single page apps), and other similar activities that are generally associated with navigating away from a page. Is this behavior intended or documented anywhere? Or should it be considered a bug?

Krejt Përgjigjet (1)

grimzecho
grimzecho I zoti i pyetjes
more options

--edit-- There is a typo. The first sentence of the second paragraph should read: "However, when Firefox receives such a code in response to a form post, it triggers ..."