Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Following up on the removal for WebSQL for Android WebView. We've gotten approval from Android & WebView team to proceed and will be doing a gradual Finch rollout of the removal starting M133. Progress will be tracked on this issue . Best, Ayu On Monday, March 11,

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Apparently my earlier response got stuck in moderation but for the record this was exactly what I was looking for Anton. Thank you! Hans On Saturday, March 9, 2024 at 5:12:34 PM UTC-7 Anton Bershanskyi wrote: > Hi Hans, > > > bit of detail about the work currently being done to extract WebSQL.

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Hans, > bit of detail about the work currently being done to extract WebSQL. You might be interested in this bug titled "Delete WebSQL data after API removal". Also, data deletion will occur only after the actual API code is deleted, which will

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

> I'm not aware of such polyfil, however I'm not sure why you would need one Ah ok. I misunderstood. This is actually the biggest part of the lift and risk in my particular case. There's a ton of nested db.transaction()/tx.executeSql() calls that would need to be rewritten and the app in some

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Hans, > Am I correct in understanding that there's a polyfil that allows the use of the WebSQL API surface with the WASM-based SQLite port? I'm not aware of such polyfil, however I'm not sure why you would need one, considering the similarity of the WebSQL API and WASM port: both are merely

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Does anyone know if the WebSQL db file itself will remain intact? I'm hoping yes, as that would preserve some manual options for recovery. Hans On Thursday, March 7, 2024 at 2:54:53 PM UTC-7 Anton Bershanskyi wrote: > Hi Hans, > > It's unfortunate that you find yourself in this situation. I'm

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Thank you Anton and Thomas for your responses. I really appreciate it. Anton, I did some experimentation with the WASM-based SQLite port today and I'm curious to understand more about the approach you mentioned. In particular: 1) Am I correct in understanding that there's a polyfil that allows

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

In case it's any helpful, I have written a migration guide on how to go from Web SQL to SQLite . It's admittedly only tested on toy data, so your actual mileage may vary, but at least the overall mechanics should be somewhat useful at l

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Hans, It's unfortunate that you find yourself in this situation. I'm not a Google or Chromium representative, but official representatives answered this exact question before and consistently rejected any f

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Thanks for the explanation Panos. That makes sense. OK so... please forgive me folks. I know this is a crazy thing to ask, I really do, but I need to take the shot. Is there ANY possibility whatsoever that access to the API can be preserved through 124? I've been grinding away for a year on a

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

The difference between the last trial milestone and the end date is due to the fact that origin trial tokens contain the expiration date by design. Given that the token needs to expire after the ending milestone has passed and given the often lengthy browser update cycle for some users, we ended up

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Fair enough Anton. Admittedly a bit of wishful thinking on my part. Although FWIW, the origin trial status in dev tools only mentions the expiration date, not version. By no means an excuse, but I'm curious, why express the trial expiration in terms of a date at all, much less a date that is 1.

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Hans, Could you please clarify which web page suggests that the WebSQL availability would extend to Chrome 124 inclusive? All news/articles I could find online suggest that the last version supporting WebSQL would be 123: - Feature: Deprecate and Remove WebSQL

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Ayu, Can you clarify... are you saying the deprecation trial does NOT extend to Chrome 124? I would not have expected that given that the trial's expiration date has been communicated consistently as *May 28, 2024*. Thanks, Hans On Friday, February 23, 2024 at 11:15:46 AM UTC-7 Ayu Ishii w

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Clémence, We're still working with the WebView team to nail down the exact timeline, but will update this thread once it is decided. For context for others, there is a bug in WebView removal where the API is still accessible when WebsiteSettings.SetDatabaseEnabled

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi all :) Have you decided a timeline for WebSQL support removal on Android WebViews ? We've already developed a SQLite alternative but there will be performance impacts on our mobile app as soon as WebSQL is disabled and we need to anticipate and communicate with our clients about the "switch"

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Antonio, That is correct, 123 will be the last supported version via flag or policy. 124 will be the first version WebSQL will no longer be available even with a flag or policy. Best, Ayu On Friday, February 23, 2024 at 8:02:48 AM UTC-8 Antonio MORENO wrote: > Hi all, > > Related to this to

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi all, Related to this topic, a bit of a simple question: In the initial announcement, it seemed to indicate that Chrome 123 would be the first version without any kind of support for WebSQL. However, at least in the current version of the beta (123.0.6312.4) support is still there, and can b

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi, We have been communicating this deprecation for a while now so unfortunately, we will not extend it further. It’s a significant source of security issues so we will keep the original deprecation timeline. If that can be useful to your situation, SQLite is available in the browser: https://de

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Just started using the origin trial in one of our apps that requires a slightly overly extertive lift to change from webSQL to IndexedDB. The expiry says May 28, 2024 -- what is the potential that date could be extended while we work to release our new version? On Friday, September 8, 2023 at 4

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Guillem, The page load limit only applies to trials that introduce new features, not deprecation trials like this one that remove a feature. Apologies for the confusion. Thanks, Panos On Thu, Sep 7, 2023 at 10:29 AM 'Guillem Olivé' via blink-dev < blink-dev@chromium.org> wrote: > Hi, > > I

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi, I am working by a third-party enterprise and we are still using webSQL functionality. Our application will be refactored to remove it, but it will take some time to make it possible. We are apprehensive about the disclaimer in the WebSQL Deprecation Trial registration: "I understand that I

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

WebSQL Deprecation Trial registration is now available at https://developer.chrome.com/origintrials/#/view_trial/494270059103911937 On Friday, June 30, 2023 at 6:48:09 AM UTC-7 tste...@google.com wrote: > Timeline updated in developer-facing comms: > https://github.com/GoogleChrome/developer.ch

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Timeline updated in developer-facing comms: https://github.com/GoogleChrome/developer.chrome.com/pull/6725. On Mon, Jun 26, 2023 at 10:57 PM Ayu Ishii wrote: > Hi blink owners, > > With request from partners, we are planning to update the timeline to > enable deprecation trial from M117 (previou

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

M117-123 - Deprecation trial What does this mean in terms of when trial registration will be available at https://developer.chrome.com/origintrials/#/trials/active ? I'm the author of an extension that's currently using Web SQL Database. I'd like to take advantage of the deprecation trial wh

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Thanks for the update, no concerns with the change! BTW, I've added WebSQL as the #1 example case around "ease of adaptation " in our blink compat principles. I tried to briefly summarize t

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi blink owners, With request from partners, we are planning to update the timeline to enable deprecation trial from M117 (previously M118) to provide a larger window to integrate with the trial before full removal in M119. The rest of the timeline will stay the same. NEW - Target timeline: M1

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

On Tue, May 16, 2023 at 10:29 AM Asier Lostalé wrote: > Hi Thomas, > > Thanks for your reply. > > If possible, I'd like to clarify a couple of topics: > > - I see there is already an "Allows access to WebSQL APIs" flag that can > be used to force access to WebSQL. For how long is this flag planne

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Thomas, Thanks for your reply. If possible, I'd like to clarify a couple of topics: - I see there is already an "Allows access to WebSQL APIs" flag that can be used to force access to WebSQL. For how long is this flag planned to be kept? Will it be available from M119 to M123? What about af

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi all, Thanks for communicating the plans for this removal with this additional information. However, we still have two questions about this: - Does it mean that in M119 WebSQL will not be working by default, but it will still be possible to enable it back with this configuration setting?

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Hi Asier, - Does it mean that in M119 WebSQL will not be working by default, but it > will still be possible to enable it back with this configuration setting? > Would this be the case until M123? As a site owner, you can take part in the deprecation trial, which will be available until Chrome 1

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Here's the PR that updates the removal timeline for the developer-facing article: https://github.com/GoogleChrome/developer.chrome.com/pull/6187. On Wed, May 3, 2023 at 11:46 AM Ayu Ishii wrote: > Thank you for the review & approvals! > We will update the thread if there are changes to the timel

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

Thank you for the review & approvals! We will update the thread if there are changes to the timeline. Best, Ayu On Wednesday, May 3, 2023 at 8:40:35 AM UTC-7 Mike West wrote: > LGTM3. Good luck with the launch, I've been excited about this for a while > and I'm looking forward to reducing our a

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

LGTM3. Good luck with the launch, I've been excited about this for a while and I'm looking forward to reducing our attack surface. -mike On Wed, May 3, 2023 at 3:21 PM Mike Taylor wrote: > LGTM2 - kudos to the team for the very detailed compat and risk analysis, > as well as proactively engagi

Re: [blink-dev] Re: Intent to Deprecate and Remove Web SQL

LGTM2 - kudos to the team for the very detailed compat and risk analysis, as well as proactively engaging in outreach. Good luck. :) On 5/3/23 6:59 AM, Yoav Weiss wrote: LGTM1 Thanks for the details analysis. The rollout plan seems reasonable, and the low effective breakage gives me hope that