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

> engineer-adjacent folks in the thread who were privy to that bit of detail > about the work currently being done to extract WebSQL. > > For now I'm gonna focus on wrapping up the release and hope for a speedy > CWS approval. > > Thanks again Anton. > > Cheers, > Hans

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

On Saturday, March 9, 2024 at 7:40:02 AM UTC+2 Hans Meyer wrote: > 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 

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

en it effectively ends for most users? >>> >>> Again, no excuses. I agree the versioning was clearly communicated. Just >>> wanted to give some feedback to consider to possibly minimize confusion in >>> the future. >>> >>> Thanks for your respo

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] Intent to deprecate and remove import assertion 'assert' syntax

For the record, relevant V8 commit landed with removal planned for V8 12.6.[1] [1] https://chromium.googlesource.com/v8/v8/+/ae5a4db8ad86c817f80856901ea121829f8b5184%5E%21/ On Wednesday, December 20, 2023 at 6:42:53 PM UTC+2 Daniel Bratell wrote: > LGTM3 for the plan as outlined by Mike and

Re: [blink-dev] Intent to Ship: Remote Playback API

Hi all, the specification contains numerous (9) references to "user permission", yet there is no section about Permissions API and Permissions Policy integration, as well as Permissions Policy feature/declaration and default allow list. Is this intentional? Of course, this could be accidental

[blink-dev] Re: Intent to Remove: HTTP/2 and gQUIC server push

Hi Grzegorz, HTTP/2 server push was disabled by default in Chrome 106[1]. You can achieve the almost the same latency speedup via preloading and prerendering (rel=preload [2] and rel=prerender) and HTTP Early Hints[3] (supported since Chrome 103) and speculation rules. [1]

Re: [blink-dev] Intent to Ship: Scroll To Text Fragment

Hi Adam, > Is it still not possible to disable this distraction yet? Chrome used to have an option to disable this feature, but the flag was removed. It is possible to remove highlights with extensions. I found "Disable Google Search Text Highlights"

[blink-dev] Re: Intent to Prototype: Web environment integrity API

Hello everyone, has there been any progress on Web environment integrity API since August? In particular: 1. Does Google still have aspirations to prototype this API? The Chrome Platform Status entry specifies that there is "no