Re: [whatwg/url] URLSearchParams and URL [Serializable] (#370)

I'm on the fence whether this is necessary. Seems like there isn't a strong case of passing the objects between browsing contexts, because the input typically arrives in string format already (in each context). Storing in Indexed DB is more interesting, with the possible downside of being bigger (in bytes) to store than the serialized string representation? (Upside is [maybe] performance--not having to re-parse a string into its component parts... though it still happens, we'd just be moving the timing from an explicit Javascript step to having the platform reconstitute the object for you from whatever serialized form is used to store the object internally).

@bakulf can you provide more context on the scenario you're working with? Was this just an unexpected missing feature you ran into, or was there some reason you need to keep the interface object around?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/370#issuecomment-360918165