[blink-dev] Intent to Ship: FileSystemFileHandle.move() for local files

[Austin Sullivan]

Contact emails

asu...@chromium.org

Specification

https://github.com/whatwg/fs/pull/10

Design docs

https://github.com/a-sully/fs/pull/2

Summary

Support efficient moves and renames of local files (i.e. user-visible files
on the device) with the File System Access API.

Efficient file moves is a core API primitive that dramatically improves the
viability of a number of applications on the web. For example, renaming a
large video file currently requires obtaining access to a new file, copying
all the data, and removing the original. This is slow, error-prone (ex: out
of quota), and a poor developer and user experience.


Blink component

Blink>Storage>FileSystem


Search tags

file , system
, access
, move
, rename
, opfs


TAG review

https://github.com/w3ctag/design-reviews/issues/805

TAG review status

Pending

Risks
Interoperability and Compatibility

Gecko: Negative to local file access more broadly, and therefore this
addition (https://github.com/mozilla/standards-positions/issues/732)

WebKit: No signal on this addition (
https://github.com/WebKit/standards-positions/issues/121) or local file
access in general (https://github.com/WebKit/standards-positions/issues/28)

Web developers: Strongly positive (
https://github.com/WICG/file-system-access/issues/64)

Other signals:

Ergonomics

See the "Improve the ergonomics of the API" section of the explainer

Security

See the "Security Considerations" section of the explainer

WebView application risks

N/A

Debuggability

Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?

No, accessing local files with the File System Access API is not supported
on Android

Is this feature fully tested by web-platform-tests

?

Yes

Flag name

kFileSystemAccessMoveNonOpfsFiles

Requires code in //chrome?

False

Launch bug

https://launch.corp.google.com/launch/4200956

Estimated milestones

M111

Anticipated spec changes

No anticipated inter-op issues with file moves. Directory moves are being
punted for now while we resolve inter-op issues (see
https://github.com/whatwg/fs/issues/59 for more context)

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6271579653144576

This intent message was generated by Chrome Platform Status
.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnvaEXisJRYpRYJtRW%2BYiN_eL27opNRvjH6U3v0R6nHV8tEtA%40mail.gmail.com.

Re: [blink-dev] Proposal of web facing feature about Sec-GPC implementation

[Ari Chivukula]

Thanks for reaching out! This is the right place to publish intents to
launch new features in Chrome, and an overview of the process can be found
here: https://www.chromium.org/blink/launching-features/

I believe the prototyping phase is the best place to start given GPC itself
already has a specification. https://privacycg.github.io/gpc-spec/

Some examples of the format in action can be found here:
https://groups.google.com/a/chromium.org/g/blink-dev/search?q=subject%3Aintent%20subject%3Ato%20subject%3Aprototype

~ Ari Chivukula (Their/There/They're)


On Fri, Jan 20, 2023 at 12:22 PM Maxim Nesterov 
wrote:

> I uploaded change for review
>  with
> Sec-GPC  implementation (both additional header and js api), but was mentioned
>
> that
> the change should be approved on blink-dev@chromium.org first.
> Could you, please, help me with that?
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dcdd636b-f476-4291-883b-267b260f8d90n%40chromium.org
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGpy5DKZ0vi5NnxqesVWwfAEo8mXPPw9afh%2BuO9CRyRm4owR%2Bg%40mail.gmail.com.

[blink-dev] Proposal of web facing feature about Sec-GPC implementation

[Maxim Nesterov]

I uploaded change for review 
 with  
Sec-GPC  implementation (both additional header and js api), but was mentioned 
that
 
the change should be approved on blink-dev@chromium.org first.
Could you, please, help me with that?

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dcdd636b-f476-4291-883b-267b260f8d90n%40chromium.org.

Re: [blink-dev] Intent to Ship: Origin Isolation By Default / Deprecate document.domain on stable

['Eiji Kitamura' via blink-dev]

FYI, the enterprise bit has been added to the article.
https://developer.chrome.com/blog/immutable-document-domain/

On Tue, Jan 17, 2023 at 1:21 AM Brandon Heenan  wrote:

> We'll make the update in the enterprise release notes too. Thanks for
> keeping us in the loop
>
> On Mon, Jan 16, 2023 at 9:46 AM Rick Byers  wrote:
>
>> Thanks so much Eiji!
>>
>> On Mon, Jan 16, 2023 at 3:06 AM Eiji Kitamura  wrote:
>>
>>> I've updated the blog post
>>>  stating
>>> Chrome 111 is where we ship the feature, but looks like it's rolling out
>>> through 111 and 112?
>>> I'll update the blog post to mention `OriginAgentClusterDefaultEnabled`
>>> enterprise policy.
>>>
>>>
>>> On Sat, Jan 14, 2023 at 1:37 AM Rick Byers  wrote:
>>>
 Thanks for the update Daniel, good luck!

 In case others, like me, have missed or forgotten the long history of
 this difficult deprecation and what it means for web developers, this blog
 post is a good summary
 . One
 critical thing it doesn't mention, but probably should, is that the 
 OriginAgentClusterDefaultEnabled
 enterprise policy
 
 can also be used to revert the default on managed devices (though it looks
 like the launching milestone needs to be updated there too).

 Rick

 On Fri, Jan 13, 2023 at 9:53 AM 'Daniel Vogelheim' via blink-dev <
 blink-dev@chromium.org> wrote:

> Hello all,
>
> We've now handled the bugs we've discovered, and I would like to make
> another attempt at launching. I'll follow the plan that was approved here,
> but two milestones later: Launch to 50% beta in M111 (or late M110, if I
> can still catch a bit of that release cycle), and then ramp on stable once
> M112 is out.
>
>
> On Wed, Dec 14, 2022 at 6:36 PM Daniel Vogelheim 
> wrote:
>
>> Hello all,
>>
>> An update: Unfortunately we have discovered a bug with this feature,
>> just as I was getting ready to enable it. The bug also affects pages that
>> have not even set document.domain. Since I have now missed a substantial
>> portion of the 109 beta cycle I'd like to delay the roll out once more, 
>> and
>> shift it by one milestone (or two; depending on when everything is 
>> fixed).
>>
>> On the positive side: Recently the last of the previously identified
>> big document.domain users, that together accounted for about 50% of
>> remaining usage, has dropped their usage. So current usage is lower than
>> previously reported. See the usage dip around late November at
>> deprecate.it (1st graph).
>>
>> On Thu, Nov 10, 2022 at 5:42 PM Mike Taylor 
>> wrote:
>>
>>> LGTM3
>>>
>>> On 11/10/22 11:18 AM, Chris Harrelson wrote:
>>>
>>> LGTM2
>>>
>>> On Thu, Nov 10, 2022, 4:19 AM Yoav Weiss 
>>> wrote:
>>>
 LGTM1 to roll this out to 50% of Beta/Dev/Canary for either M108 or
 M109, and carefully roll this out for M110, once it hits stable.

 On Wed, Nov 9, 2022 at 7:05 PM Daniel Vogelheim <
 vogelh...@google.com> wrote:

> On Wed, Nov 9, 2022 at 6:10 PM Mike Taylor 
> wrote:
>
>> On 10/27/22 11:49 PM, 'Daniel Vogelheim' via blink-dev wrote:
>>
>> Hello all,
>>
>> The approval for the Intent To Ship for Origin Isolation By
>> Default / Deprecate document.domain
>> 
>> asks for a separate intent for the actual default change
>> .
>> This is that separate intent.
>>
>> A summary of what happened so far:
>>
>> - Shipping Origin Isolation by Default (and thereby deprecating
>> document.domain) has security benefits, but compatibility risk.
>>
>> - We added warnings to the developer console and issues panel,
>> published a blog post, and engaged in direct outreach. This has 
>> resulted in
>> substantial, measurable reduction of usage. Some sites keep using
>> document.domain, but have mitigated the deprecation with other 
>> means. This
>> makes the risk difficult to measure.
>>
>> - Sampling of sites with document.domain usage and manual
>> inspection yields a potential breakage estimate at ~0.015% of page 
>> views.
>>
>> What we're asking for here is:
>>
>> - Enable the feature at 50% for beta (+ dev + canary) during
>> M109, as a "last call" for web site authors.
>>
>> This sounds like a good idea. Is 

Re: [blink-dev] Intent to extend experimentation: Back/forward cache NotRestoredReason API

[Yoav Weiss]

LGTM to experiment till M114 (inclusive)

On Fri, Jan 20, 2023 at 6:59 AM Daisuke Enomoto 
wrote:

>
> We would like to extend the origin trial for 3 additional milestones, with
> the extension starting in 112 continuing through 114. The initial
> experiment was approved for the OT running from 109 through 111.
>
> Contact emails
>
> yu...@google.com, yu...@chromium.org, fer...@chromium.org
>
> Explainer
>
>
> https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/NotRestoredReason.md
>
> Design docs
>
>
> https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/NotRestoredReason.md
>
> Summary
>
> NotRestoredReason API reports the reasons why a page is not served from
> BFCache after a history navigation. The report is accessible via the
> PerformanceNavigationTiming API. The report attributes reasons to specific
> frames as much as possible, while respecting cross-origin security concerns.
>
> Blink component
>
> UI>Browser>Navigation>BFCache
> 
>
> TAG review
>
> https://github.com/w3ctag/design-reviews/issues/739
>
> TAG review status
>
> Issues addressed
>
> Risks
>
>
>
> Interoperability and Compatibility
>
>
>
> Gecko: No signal:
>
>
> WebKit: No signal:
>
>
> Web developers: Positive (
> https://github.com/w3c/navigation-timing/issues/171#issuecomment-1062672989
> )
>
>
>
> Security
>
> We do not report detailed information about cross-origin iframes. For
> cross-origin iframes, we only report if they blocked bfcache or not, and we
> do not report the reasons why.
>
>
> Goals for experimentation
>
> We would like developers to use the new field notRestoredReasons in
> performance navigation entry, e.g.
> performance.getEntriesByType('navigation')[0].notRestoredReasons;
>
> The goal of the experiment is to gather feedback from developers about the
> API shape.
> Reason this experiment is being extended
>
> We had requested this Origin Trial to be run for 3 milestones,
> specifically from 109 to 111 without realizing the Origin Trial guideline
> 
> suggesting 6 milestones. We would like to extend this OT for another 3
> milestones or to 114 inclusive by applying the 6 milestone guidelines we
> originally missed, to give sufficient time for partners to give us feedback.
>
>
> Debuggability
>
> In DevTools console, try:
>
> performance.getEntriesByType('navigation')[0].notRestoredReasons;
>
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?
>
> No
>
>
> Is this feature fully tested by web-platform-tests
> 
> ?
>
> No
>
>
> DevTrial instructions
>
>
> https://chromium.googlesource.com/chromium/src/+/main/docs/experiments/not-restored-reasons.md
>
>
> https://github.com/rubberyuzu/bfcache-not-retored-reason/blob/main/HowToTest.md
>
>
> Flag name
>
> --enable-experimental-web-platform-features
>
>
> Tracking bug
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1326344
>
>
> Launch bug
>
> https://launch.corp.google.com/launch/4200848
>
>
> Estimated milestones
>
> OriginTrial desktop last (new request)
>
> 114
>
> OriginTrial desktop last
>
> 111
>
> OriginTrial desktop first
>
> 109
>
> OriginTrial desktop last (new request)
>
> 114
>
> OriginTrial Android last
>
> 111
>
> OriginTrial Android first
>
> 109
>
> OriginTrial webView last (new request)
>
> 114
>
> OriginTrial webView last
>
> 111
>
> OriginTrial webView first
>
> 109
>
>
> Link to entry on the Chrome Platform Status
>
> https://chromestatus.com/feature/5684908759449600
>
>
> Links to previous Intent discussions
>
> Intent to prototype:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/os3qUVtqyWo/m/4cs6GCN5BAAJ
>
> Intent to Experiment:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/ce4hr99dUDc/m/C4wYpnKiAwAJ
> Read for Trial:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/7jBZLdt7EsY/m/KiTrSzbSBgAJ
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA5e698QcKZSthm%3Dz_4pi8cOzi4kfbx-AXveC%2BAKimUh-tMycA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 

[blink-dev] Intent to Ship: CSS Nesting

['Steinar H. Gunderson' via blink-dev]

Contact emails: se...@chromium.org, futh...@chromium.org
Explainer: None

Specification: https://drafts.csswg.org/css-nesting

Summary: Add the ability to nest CSS style rules inside other style rules,
combining selectors from the outer with the inner rule for increasing
modularity and maintainability of style sheets.

Blink component: Blink>CSS

TAG review: https://github.com/w3ctag/design-reviews/issues/791

TAG review status: Pending

Risks: There is a threat of a formal objection in CSSWG.

Interoperability and Compatibility:

Gecko: Positive (https://github.com/mozilla/standards-positions/issues/695)
WebKit: Positive (https://github.com/WebKit/standards-positions/issues/69)

Debuggability
Nesting style rules will be a big change for editing and displaying style rules 
in the inspector:

- Showing displaying nested rules for matching declarations
- Editing selectors
- Inserting nested rules
- etc...

Tracking issue for devtools support: https://crbug.com/1172985
Devtools says they're on track for shipping in M111.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux,
Chrome OS, Android, and Android WebView)? Yes

Is this feature fully tested by web-platform-tests? Yes

Flag name: CSSNesting

Requires code in //chrome? False

Tracking bug: https://crbug.com/1095675

Estimated milestones
DevTrial on desktop 109
DevTrial on Android 109
Shipping112


Anticipated spec changes: See above.

Link to entry on the Chrome Platform Status:
https://chromestatus.com/feature/5800613594529792

Links to previous Intent discussions:
Intent to prototype: 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/YzrEmc%2BqlqPv72Au%40google.com

-- 
Software Engineer, Google Norway

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/Y8ph9gk50U2D92f3%40google.com.