[Beacon] Forbidding submitting Documents

• From: Jonas Sicking <jonas@sicking.cc>
• Date: Thu, 12 Dec 2013 17:16:02 -0800
• To: Webapps WG <public-webapps@w3.org>, Arvind Jain <arvind@google.com>
• Message-ID: <CA+c2ei_ahM-PKRKB=9L8amBtOL4zQF9-X7yp7RJqzgC9TRrKTQ@mail.gmail.com>

Hi All,

I'm wondering if we should forbid submitting Document objects with
sendBeacon. It seems to me like submitting documents doesn't make a
lot of sense for the use cases that we have in mind, and serializing a
Document can be a non-trivially heavy operation.

It mostly seems like it's there for compatibility with XHR, but given
that this is a separate API, it doesn't seem like there's a lot of
value to it. It basically just turns into extra code that UAs have to
lug around and which likely will mostly go unused.

Additionally pages can always use XMLSerializer to satisfy the same
use case if they really want to.

/ Jonas

Received on Friday, 13 December 2013 01:16:59 UTC