Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2025-07-01 Thread 'Ashley Gullen' via blink-dev
Thanks for the update. A bit of a wait but sounds like we'll get there in the end. On Mon, 30 Jun 2025 at 20:04, Torne (Richard Coles) wrote: > On Mon, 30 Jun 2025 at 11:42, 'Ashley Gullen' via blink-dev < > blink-dev@chromium.org> wrote: > >> Hi folks, apol

Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2025-06-30 Thread &#x27;Ashley Gullen&#x27; via blink-dev
ther not implement onShowFileChooser(), or > should apply filtering. > > On Mon, Oct 28, 2024 at 10:57 PM Peter Beverloo > wrote: > >> Hi Joel, could you summarise how this has ended up working on WebView, as >> there's neither permissions nor UI there? Will app

Re: [blink-dev] Intent to Prototype: Limiting Access to Local Fonts

2025-04-03 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Presumably this does not affect the Local Font Access API (queryLocalFonts())? Once that method has resolved will the returned fonts then be allowed to be used in font rendering? On Wed, 2 Apr 2025 at 22:36, Chromestatus wrote: > Contact emails ta...@google.com, riz...@google.com > > Explainer >

Re: [EXTERNAL] Re: [blink-dev] Intent to Remove: SwiftShader Fallback

2025-03-11 Thread &#x27;Ashley Gullen&#x27; via blink-dev
; *From:* Ken Russell >>> *Sent:* Monday, March 3, 2025 10:39 AM >>> *To:* Ashley Gullen >>> *Cc:* Geoff Lang ; Erik Anderson < >>> erik.ander...@microsoft.com>; Rick Byers ; David >>> Adrian ; blink-dev ; >>> geof...@chromium.org >

Re: [EXTERNAL] Re: [blink-dev] Intent to Remove: SwiftShader Fallback

2025-02-28 Thread &#x27;Ashley Gullen&#x27; via blink-dev
>> forcibly disable SwiftShader as a scream test. And after you switch over >> the default, it could enable enterprises caught unaware to have some >> additional window of time to plan mitigations (by re-enabling it via >> policy) before you proceed with fully depreca

Re: [blink-dev] Intent to Remove: SwiftShader Fallback

2025-02-13 Thread &#x27;Ashley Gullen&#x27; via blink-dev
I wrote about this previously but I'm still concerned this is a major breaking change for existing published WebGL content on the web. If the figure of 2.7% comes from my previous citing of Web3DSurvey ( https://web3dsurvey.com/) then this should be seen as very much an underestimate, because that

Re: [blink-dev] Re: Intent to Ship: H26x Codec support updates for MediaRecorder

2025-02-11 Thread &#x27;Ashley Gullen&#x27; via blink-dev
As a web developer interested in Chrome's video encoding capabilities with both WebCodecs and MediaRecorder, I had no idea until reading this that Chrome actually already shipped support for HEVC encoding with WebCodecs in M130 - it doesn't appear to be listed on chromestatus.com. Could Google make

Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2025-01-21 Thread &#x27;Ashley Gullen&#x27; via blink-dev
on Android? If there's no good story for that, perhaps this >>>>> shouldn't ship until there is. (My sense matches Ashley's, that Android >>>>> doesn't actually support opening directories if it can't then open files >>>>> inside thos

Re: [blink-dev] PSA: Add Permission modals for Keyboard and Pointer Lock

2024-12-20 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Hi folks, FWIW I think this change might have caused this bug where the audio volume is permanently reduced after showing a permission prompt: https://issues.chromium.org/issues/385300194 Ashley On Fri, 20 Dec 2024 at 13:15, 'Muyao Xu' via blink-dev < blink-dev@chromium.org> wrote: > Hi Raf, >

Re: [blink-dev] Re: Concerns over removal of SwiftShader fallback

2024-11-28 Thread &#x27;Ashley Gullen&#x27; via blink-dev
aufort > wrote: > >> According to https://issues.chromium.org/40277080, I believe >> geoffl...@chromium.org should be able to help you. >> >> On Wed, Nov 27, 2024 at 4:22 PM 'Ashley Gullen' via blink-dev < >> blink-dev@chromium.org> wrote: >>

[blink-dev] Re: Concerns over removal of SwiftShader fallback

2024-11-27 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Hi folks, it's been a week, is anyone from the relevant team able to review this and respond? Best regards Ashley On Wed, 20 Nov 2024 at 16:54, Ashley Gullen wrote: > Hi Blink developers, > > I am concerned about this entry on Chrome Platform Status "Remove > SwiftShader fallback", currently s

Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2024-11-14 Thread &#x27;Ashley Gullen&#x27; via blink-dev
cker` function >>> should be omitted.) >>> >>> I also see that this re-used the overall File System Access Chrome >>> Status entry <https://chromestatus.com/feature/6284708426022912>, so >>> the API owners weren't prompted to actually L

Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2024-10-30 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Yes, we use dirHandle.getFileHandle(name, { create: true }). We use that to create new files in the chosen folder. That is fundamental to how our PWA saves data in folders (and I'd have thought fundamental to the use of a directory picker). On Wed, 30 Oct 2024 at 08:40, Joel Hockey wrote: > I've

Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2024-10-29 Thread &#x27;Ashley Gullen&#x27; via blink-dev
that the > defaults avoid any surprises there, security, privacy or otherwise. > > Thanks, > Peter > > >> >> On Mon, Oct 28, 2024 at 10:57 PM Peter Beverloo >> wrote: >> >>> Hi Joel, could you summarise how this has ended up working on WebView, >

Re: [blink-dev] Intent to Ship: File System Access on Android and WebView

2024-10-28 Thread &#x27;Ashley Gullen&#x27; via blink-dev
I'd be very happy to see the File System Access API ship on Android! However from my testing it doesn't look ready yet. Using our PWA Construct ( https://editor.construct.net) in Canary 132, create a new empty project and try saving it with Menu > Project > Save as, and: - Choosing 'Save as sin

Re: [blink-dev] Intent to Ship: WebGPU timestamp queries

2023-10-26 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Is the requirement for cross-origin isolation stricter than the requirements to use EXT_disjoint_timer_query{_webgl2}? If so it will present a porting problem when switching WebGL content to WebGPU. On Thu, 26 Oct 2023 at 11:21, 'François Beaufort' via blink-dev < blink-dev@chromium.org> wrote:

Re: [blink-dev] Intent to Ship: Baselines in New TextMetrics API in Canvas

2023-08-22 Thread &#x27;Ashley Gullen&#x27; via blink-dev
There is still this open issue about inconsistent TextMetrics measurements across browsers: https://bugs.chromium.org/p/chromium/issues/detail?id=1183752 I think it may involve this unresolved spec issue: https://github.com/whatwg/html/issues/6731 This is causing us constant annoying compatibility

Re: [blink-dev] Re: Intent to Ship: WebGPU

2023-01-12 Thread &#x27;Ashley Gullen&#x27; via blink-dev
OK thanks - it's just at the moment it's not clear if extensions aren't supported due to missing implementation (so it won't work anywhere), or an unsupported system (in which case I can potentially get it working and test my code if I find the right system setup). Extra visibility on that would be

Re: [blink-dev] Re: Intent to Ship: WebGPU

2023-01-12 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Can I ask what the release schedule is for the various WebGPU extensions as well? It's not currently clear to me which extensions are planned to be shipped with the first release of WebGPU and which are to be implemented later down the line. As of today's Canary 111.0.5534.0 on Windows 11 with a n

Re: [blink-dev] Intent to Prototype: JPEG XL decoding support (image/jxl) in blink

2022-10-31 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Apologies for bringing back an old thread, but I thought it was important to bring this up here. I was surprised to read that Google are abandoning their efforts to implement JPEG-XL: https://bugs.chromium.org/p/chromium/issues/detail?id=1178058#c84 As I understood it, JPEG-XL brought significant

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

2021-10-22 Thread &#x27;Ashley Gullen&#x27; via blink-dev
Just to be clear: you can already asynchronously create content to copy to the clipboard in Chrome, because its user activation rules give you 1 second to prepare the data. Assuming sites like Excel Online can prepare their data within 1 second, then it's already possible to do this within user act

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

2021-10-22 Thread &#x27;Ashley Gullen&#x27; via blink-dev
I know that this change aims to align with the specification and Safari. I am questioning why the specification needs this in the first place, given the user activation rules already specified. It looks like if other browsers support the specified user activation rules, then this part of the specif

Re: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

2021-10-21 Thread &#x27;Ashley Gullen&#x27; via blink-dev
I'm not sure why this API needs to exist. It used to be the case that you could not write to the clipboard after await in Chrome. That's because after an await it was no longer in a synchronous user input trigger, and so the call was blocked. User Activation v2 fixed that. Now you can write to th