Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

Hi all, Quick question, has this warning for first party contexts been finally added ? Or, otherwise, is there a decision on whether it will be finally added or not? Thanks in advance, and regards, Antonio. On Thursday, 28 October 2021 at 16:59:31 UTC+2 ari...@chromium.org wrote: > I agree w

Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

Hi Ari, Very clear, thanks a lot for the information! Regards, Antonio. On Fri, 19 Nov 2021 at 13:24, Ari Chivukula wrote: > We're gathering metrics to see how feasible deprecation is on different > timelines and to determine the scope of outreach that would be necessary. > Once that's done,

Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

We're gathering metrics to see how feasible deprecation is on different timelines and to determine the scope of outreach that would be necessary. Once that's done, if we move forward an intent to deprecate will be sent to blink-dev with the plan for comment before it's implemented. Some of this dep

Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

I agree with you, and hope we can soon make such an announcement (and add the warning for developers). On Thu, Oct 28, 2021 at 07:56 Fernando Serboncini wrote: > Given that we are disabling this for 3rd parties, would it make sense to > already start warning 1st-party usage (saying that this doe

Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

Given that we are disabling this for 3rd parties, would it make sense to already start warning 1st-party usage (saying that this doesn't work at all for 3rd parties and that it will be removed in the future)? I don't know what's the guideline regarding having a deprecation warning without a clear

Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

Sorry for the delay, the data for actually reading/writing a database (as opposed to opening it ) in a third party context ended up being nearly identical (