https://sqlite.org/releaselog/3_44_0.html
Recently, SQLite released version 3.44.0, introducing a series of
security-related enhancements and improvements. Given the critical role of
SQLite in Chrome's infrastructure, I would like to draw your attention to
some security benefits associated with
Hi, I'm from Mexico and I have an android app created with the Sencha Touch
framework and I use WebSQL for now everything is going great. My question
is, will I also be affected by these changes?
El jueves, 9 de febrero de 2023 a las 10:23:14 UTC-6, Randy Lauen escribió:
> Hi Ben,
>
> I think t
Hola Alfonso!
If you use Ext.data.proxy.SqlView, you internally use Web SQL according to
the documentation at
https://docs.sencha.com/touch/2.1.1/#!/api/Ext.data.proxy.Sql. So yes, your
app will most likely be affected.
Cheers,
Tom
On Fri, Feb 10, 2023 at 3:31 AM Alfonso Ochoa Legorreta <
alego
Hi Ben,
I think that's what I'll experiment with first. I was hoping someone else
had traveled this road already and had some advice. My tentative plan for
migrating is to copy the WebSQL data to SQLite, but keep both
implementations running side by side for a while. If anything goes wrong,
users
*Carl*, the signs are promising for other browsers to implement all the
APIs needed to run SQLite-over-Wasm. I'm optimistic!
*Randy*, how hard would it be to implement something that read user data
from Web SQL and wrote it into a parallel table structure in SQLite? Both
of these will coexist in C
I think I'll pass on all that extra technical debt myself, already
transferred over a million records to mysql after a few hours and am now
sleeping soundly :) Good luck to the rest of the folks that come in late
... will the data be recoverable after the update?
On Wednesday, February 1, 2023
One more question is whether that will work on all browsers.. that could at
least be considered as an improvement. Also, I'm subbed to this convo and
haven't seen any notifications anywhere... Is it supposed to email me?
On Wednesday, February 1, 2023 at 6:50:35 AM UTC-5 tste...@google.com wrote
Hey Randy,
On Tue, Jan 31, 2023 at 10:51 PM Randy Lauen wrote:
> Speaking of nontrivial examples, I have a Chrome extension that relies
> heavily on WebSQL. On my desktop, the WebSQL database for my extension is
> almost 400 MB. I know some users have a database over 1 GB. I'm very
> excited abo
Speaking of nontrivial examples, I have a Chrome extension that relies
heavily on WebSQL. On my desktop, the WebSQL database for my extension is
almost 400 MB. I know some users have a database over 1 GB. I'm very
excited about using Wasm SQLite, since I can (hopefully) configure SQLite
the way
Going to all that trouble for a "replacement" that's not any better .. ok.
Good luck finding anyone who'd actually use it.
On Tuesday, January 31, 2023 at 11:04:23 AM UTC-5 Carl Turechek wrote:
> Are you sure that callback hell can't be avoided using js promises? If
> that is a major reason the
Are you sure that callback hell can't be avoided using js promises? If that
is a major reason then hopefully you're right. I think it should remain in
the desktop browsers at least, or as an option still. Thanks for the heads
up on turning off updates lol
On Thursday, December 15, 2022 at 7:02:5
I'll probably just scrap it and ajax everything to that dusty old mysql
thing. But I do appreciate the links!
On Tuesday, December 13, 2022 at 2:59:39 PM UTC-5 mo...@google.com wrote:
> Hi Carl,
>
> I'm sorry we can't keep Web SQL going any further in its present form. As
> you know, it's been
Referring to this example
https://developer.chrome.com/blog/deprecating-web-sql/ , promises might
resolve the callback madness there. Do you really need actual transactions
if it is in the browser though? Thanks again for the responses! Peace
On Thursday, December 15, 2022 at 7:02:53 PM UTC
Hi all,
I realize we haven't announced the general availability of our Web SQL
replacement on this list yet (apologies). It's an official port of SQLite
to WebAssembly (Wasm) by the SQLite team, which is backed by the Origin
Private File System (OPFS) for maximum performance. You can read all
deta
HI Michal,
We don't yet have a date for removing WebSQL everywhere. We need to finish
looking for more examples of current nontrivial usage. The best I can say
is, in 2023, but not super early in 2023. You'll have plenty of notice!
Ben
On Wed, Dec 14, 2022 at 4:36 PM Michal Šimonfy
wrote:
> H
Hi Ben, thank you for your answer!
I figured that the plan is to phase out support entirely, I was just
wondering whether deprecating and removing WebSQL "in non-secure contexts"
is going to affect chrome extensions (I assume it is not). Is there a
specific timeline for removing WebSQL from the
Our plan is to remove support entirely.
It's good to hear from developers who have been using Web SQL - since the
vast majority of uses we've found on the web emanate from standard
libraries using it for browser sniffing or as a backup for basic key-value
storage. If you're using it, and migration
Hello there!
will WebSQL continue to be available in Chrome extensions (through the
chrome-extension:// scheme)?
Thank you!
All the best,
Michal
On Tuesday, December 13, 2022 at 8:59:39 PM UTC+1 mo...@google.com wrote:
> Hi Carl,
>
> I'm sorry we can't keep Web SQL going any further in its
Hi Carl,
I'm sorry we can't keep Web SQL going any further in its present form. As
you know, it's been deprecated for years and only Chromium still supports
it. It sees little use; almost any site that wants sophisticated storage
wants it to work on all browsers, and so people build things on top
You'll break an app I developed to be passed around as a single html file.
Hope you'll provide us plebs some guidance on finding a replacement
solution.
On Wednesday, November 16, 2022 at 1:22:34 PM UTC-5 mo...@google.com wrote:
> I've done a more thorough search for examples of webkitStorageIn
I don't think that the increased security will have an effect on my app,
but the removal all together is my concern. Sorry if I haven't been clear
enough.
On Thursday, December 8, 2022 at 7:28:58 PM UTC-5 mo...@google.com wrote:
> Yes. Carl, does your app depend on Web SQL, webkitStorageInfo, o
Hi,
Thanks for taking it into account. In a nutshell, my app is a C.R.U.D. that
exports all of the data as json into a new html file along with everything
else required to search through the information. It is a catalogue resonee
where it could be downloaded and searched by anyone using a chrome
I'll note that file:// URLs are considered secure contexts, which may be
relevant for single-html-file apps -- see
https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts#when_is_a_context_considered_secure
On Thu, Dec 8, 2022 at 4:28 PM 'Ben Morss' via blink-dev <
blink-dev@chromium
Yes. Carl, does your app depend on Web SQL, webkitStorageInfo, or something
else?
On Thu, Dec 8, 2022 at 6:55 PM Carl Turechek wrote:
> You'll break an app I developed to be passed around as a single html file.
> Hope you'll provide us plebs some guidance on finding a replacement
> solution.
>
>
I've done a more thorough search for examples of webkitStorageInfo and of
WebSQL in insecure contexts on the web. Among the top 10K sites, the only
usage I found was from standard libraries - and, in these cases, removal
wouldn't cause an error or affect any functionality.
No one in Enterprise at
The developer-facing documentation is being updated in
https://github.com/GoogleChrome/developer.chrome.com/pull/4299.
On Sat, Nov 12, 2022 at 12:26 AM Ayu Ishii wrote:
> We've done some extra communications with enterprise partners and have
> come up with a new target milestone.
> The new targe
We've done some extra communications with enterprise partners and have come
up with a new target milestone.
The new target milestone for this removal is M110, with enterprise policy
available for 2 milestones (M110-111).
Thanks!
Ayu
On Wednesday, June 1, 2022 at 7:49:00 PM UTC-7 Ayu Ishii wrote
Thank you all for the approvals!
And thank you miketaylr@ for the HTTPArchive analysis!
On Wednesday, June 1, 2022 at 1:12:55 PM UTC-7 Mike Taylor wrote:
> On 6/1/22 3:52 PM, Yoav Weiss wrote:
>
> LGTM3
>
> On Wed, Jun 1, 2022 at 8:58 PM Mike Taylor wrote:
>
>> On 6/1/22 1:34 PM, Chris Harrelson
On 6/1/22 3:52 PM, Yoav Weiss wrote:
LGTM3
On Wed, Jun 1, 2022 at 8:58 PM Mike Taylor wrote:
On 6/1/22 1:34 PM, Chris Harrelson wrote:
On Tue, May 31, 2022 at 8:26 PM Ayu Ishii wrote:
Hi Mike!
With the current usage measurements we see, we hadn't
considered
LGTM3
On Wed, Jun 1, 2022 at 8:58 PM Mike Taylor wrote:
> On 6/1/22 1:34 PM, Chris Harrelson wrote:
>
>
> On Tue, May 31, 2022 at 8:26 PM Ayu Ishii wrote:
>
>> Hi Mike!
>>
>> With the current usage measurements we see, we hadn't considered any
>> enterprise policy for opt-out.
>> But certainly
On 6/1/22 1:34 PM, Chris Harrelson wrote:
On Tue, May 31, 2022 at 8:26 PM Ayu Ishii wrote:
Hi Mike!
With the current usage measurements we see, we hadn't considered
any enterprise policy for opt-out.
But certainly can follow the process to do so if you feel that
there may
On Tue, May 31, 2022 at 8:26 PM Ayu Ishii wrote:
> Hi Mike!
>
> With the current usage measurements we see, we hadn't considered any
> enterprise policy for opt-out.
> But certainly can follow the process to do so if you feel that there may
> be risk of undercounting.
> Deprecation of WebSQL in t
Hi Mike!
With the current usage measurements we see, we hadn't considered any
enterprise policy for opt-out.
But certainly can follow the process to do so if you feel that there may be
risk of undercounting.
Deprecation of WebSQL in third-party contexts added a policy that lasted 3
milestones a
I'm happy to see this moving forward, thanks for pushing it ahead!
That said, this seems like the kind of thing that's likely-enough to impact
enterprise that we should include a temporary opt-out to give ourselves
some wiggle room if it turns out that we're undercounting usage. Have y'all
already
34 matches
Mail list logo
