Re: [blink-dev] Seeking feedback on element proposal

2022-08-19 Thread Chris Harrelson 
Hi Marcos,

Thanks for the email and explainer/spec links! I have two updates for you.

First: some folks who own this feature area in Google Chrome have added
some feedback here
 (which I know
you've already seen, just noting it here for completeness).

Second, I wanted to mention that there is a bi-weekly HTML spec triage
meeting that you're welcome to present at for general feedback, and about
any potential concerns or issues with integration of the  element
into the HTML spec (*). Feel free to reach out to +Panos Astithas
 who is happy to schedule a time for you.

(*) Though I should note that in terms of implementer interest from
Chromium for landing such a spec, we'd rely on the view of the feature area
owners I mentioned above.

Regards,
Chris

On Wed, Aug 17, 2022 at 4:31 PM Marcos Caceres  wrote:

> Hi Blink-Dev / Chromium folks,
>
> WebKit project is seeking input into our recently proposed HTML 
> element, which was submitted for incubation to the Immersive Web CG at the
> W3C.
>
> We have an explainer that outlines the motivation (and tries to answer how
> this is different to using WebGL, lowering barrier of entry, potential use
> cases, etc.):
> https://github.com/immersive-web/model-element/blob/main/explainer.md
>
> And the *very rough* makings of a spec (mostly just red boxes outlining
> all the potential issues we've identified so far):
> https://immersive-web.github.io/model-element/
>
> We'd love to get your feedback, either here or as issues filed in the
> repository:
> https://github.com/immersive-web/model-element/issues
>
> We know that trying to standardize  is going to be a significant
> undertaking with a lot of challenges, but we are really excited about
> bringing this new capability to Web. Looking forward to getting your
> feedback and collaborating on incubating it!
>
> Kind regards,
> Marcos
>
>
> --
> 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/e4d49d61-f1ac-4249-9f21-95a2697d7c31n%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/CAOMQ%2Bw9T7Scm_WBNRAV31XTNjx5-yVoHaCK-wJi%2BZCbtmDvfDg%40mail.gmail.com.

Re: [blink-dev] Intent to Remove: window.webkitStorageInfo

2022-08-19 Thread 'Ben Morss' via blink-dev 
Thanks for doing this, Ayu. Once our mechanisms are in place for informing
partners more thoroughly, I think these deprecations will be simpler!



On Fri, Aug 19, 2022 at 10:07 AM Mike Taylor  wrote:

> Thanks for the heads up Ayu.
>
> On 8/18/22 8:47 PM, Ayu Ishii wrote:
>
> Hi everyone,
>
> Updating the thread to inform that we have decided to extend the target
> milestone until we've properly informed our partners. Will update the
> thread again when we have a new target.
>
> Thanks,
> Ayu
> On Tuesday, August 9, 2022 at 7:57:19 AM UTC-7 jmedley via Chromestatus
> wrote:
>
>> My notes say this is shipping in 106. Regardless, please enter the
>> shipping milestone in the correct fields. (Click Edit all fields, the
>> scroll to the bottom.) Thanks, Joe
>>
> --
> 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/13fd6dd9-aceb-4fd8-af25-4603d523c478n%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/f2fa2d9e-1da7-edec-5fe6-9a28fede890e%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/CAA6%2Bj4tgtKytkE2AogMd1XfwA2bzka67yOmYtNNXn99snmfirQ%40mail.gmail.com.

Re: [blink-dev] Intent to Extend Experiment: Conditional Focus

2022-08-19 Thread Mike Taylor 

LGTM to extend to M108 inclusive.

On 8/18/22 4:33 PM, 'Elad Alon' via blink-dev wrote:



Hi Blink owners,


We'd like to extend the Conditional Focus experiment. It is currently 
running m102-m105, and we'd like to extend by 3 additional milestones, 
making it m102-m108 (inclusive).




Contact emails

elada...@chromium.org


Explainer

https://github.com/WICG/conditional-focus/blob/main/README.md


Specification

https://wicg.github.io/conditional-focus


Design docs


https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM


Summary

Extend the getDisplayMedia() APIs to ensure that tab-capture and 
window-capture return a new subclass of MediaStreamTrack called 
FocusableMediaStreamTrack. This new subclass exposes the focus() 
method. This new method allows Web-applications, when capture starts, 
to decide whether the captured tab/window should be immediately 
focused, or whether the capturing tab+window should remain the focused 
one.




Blink component

Blink 


TAG review

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


TAG review status

Pending


Risks



Interoperability and Compatibility



/Gecko/: No signal

/WebKit/: No signal

/Web developers/: No signals

/Other signals/:


Ergonomics

N/A



Activation

Not challenging - just feature-detect: // Pre-existing functionality: 
const mediaStream = await navigator.mediaDevices.getDisplayMedia(); 
const [track] = mediaStream.getVideoTracks(); // New functionality 
behind feature-detection: if (!!track.focus) { track.focus(...); }




Security

See design-doc.


Reason this experiment is being extended

0. Some relevant background: Originally, this feature ended up ready 
and in Origin Trial quite some time before our partners were ready to 
take advantage and participate in the experiment. The OT was therefore 
_shifted_ and _restarted_ multiple times, eventually landing on the 
range of m102-m105. Our partners are now ready and have started 
rolling out code taking advantage of this feature - so far internally 
within their organization, and soon to the general public.
1. More time is required for our partners' deliberate rollout to reach 
more users, allowing these partners to provide more accurate, 
battle-tested feedback.
2. Mozilla and Apple have both engaged positively with the proposal 
(see here 
). 
Mozilla has made a proposal 
 
for a general change to getDisplayMedia(), and suggested that the API 
shape of Conditional Focus should be altered to fit that new shape. 
The added complexity of tying Conditional Focus to adjacent API 
changes prolongs the time to finalize Conditional Focus. While this is 
ongoing, we should keep supporting partners who have invested 
engineering time in this OT.


We are therefore requesting extension by 3 milestones, making the 
experiment run for m102-m108 (inclusive).




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

Supported on all Desktop platforms, but not on any mobile platforms.



Is this feature fully tested by web-platform-tests

?

No


Flag name

ConditionalFocus


Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1215480


Launch bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1214483


Estimated milestones

OriginTrial desktop last105 (but extension to 108 hereby requested)
OriginTrial desktop first   102



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5646614535340032


Links to previous Intent discussions

Intent to prototype: 
https://groups.google.com/a/chromium.org/g/blink-dev/c/lbuqOGx07xY
Intent to Experiment: 
https://groups.google.com/a/chromium.org/g/blink-dev/c/I4RE2pbocTg



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/CAMO6jDPC5EYjk1k%2B6_46erSvGNRYMkWk1Uxo4xGpouO4ROFDmQ%40mail.gmail.com 
.


--
You received this message because you are subscribed to the

Re: [blink-dev] Intent to Implement and Ship: Rich PWA installation dialogs - desktop

2022-08-19 Thread Mike Taylor 

On 8/18/22 6:52 PM, Phillis Tang wrote:



Contact emails

phil...@chromium.org


Explainer

https://github.com/w3c/manifest-app-info/blob/main/explainer.md


Specification

https://www.w3.org/TR/manifest-app-info

This feature has been shipped on Mobile - see previous status entry 
 and I2S 
. 

Enabling this on the desktop uses the same "description" and 
"screenshots" fields.


We additionally implemented parsing for the screenshots' "platform 
" member, 
but that was included in the original spec and design.



Summary

Gives developers the ability to add more data (descriptions and 
screenshots) to their PWA install dialog and gives users more insight 
into the apps they are about to install. This implements PWA richer 
install UI on desktop. See previous chromstatus entry for mobile - 
https://chromestatus.com/feature/6422599217184768




Blink component

UI>Browser>WebAppInstalls>Desktop 




TAG review

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


TAG review status

Issues addressed


Risks



Interoperability and Compatibility



/Gecko/: No signal
I see from the mobile I2S that 
https://github.com/mozilla/standards-positions/issues/492 was filed. 
Might be worth pinging that thread and pointing to this I2S, in case 
someone has input.


/WebKit/: No signal


Could we file for a signal at 
https://github.com/WebKit/standards-positions/issues?




/Web developers/: Positive 



/Other signals/:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such 
that it has potentially high risk for Android WebView-based applications?




Debuggability



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

?

No, there is an open issue for this: 
https://github.com/w3c/manifest-app-info/issues/26 




Flag name

chrome://flags/#enable-desktop-pwas-detailed-install-dialog


Requires code in //chrome?

Yes


Tracking bug

https://crbug.com/1326252


Launch bug

https://crbug.com/1326714


Estimated milestones

106



Anticipated spec changes

Open questions about a feature may be a source of future web compat or 
interop issues. Please list open issues (e.g. links to known github 
issues in the project for the feature specification) whose resolution 
may introduce web compat/interop risk (e.g., changing to naming or 
structure of the API in a non-backward-compatible way).


https://github.com/w3c/manifest-app-info/issues/55
Thanks for pointing this out! It would be nice to try to reach consensus 
on this issue before shipping, then maybe needing to immediately 
deprecate/rename the platform member.



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5206272861798400

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/CABcACaihvDYf47Z%3Dxivbr_NOXgBMW6NbL01av%3D4_FHEA9UXiPw%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 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0341686e-fa2c-4389-6a03-0ded072c91ec%40chromium.org.

Re: [blink-dev] Intent to Remove: window.webkitStorageInfo

2022-08-19 Thread Mike Taylor 

Thanks for the heads up Ayu.

On 8/18/22 8:47 PM, Ayu Ishii wrote:

Hi everyone,

Updating the thread to inform that we have decided to extend the 
target milestone until we've properly informed our partners. Will 
update the thread again when we have a new target.


Thanks,
Ayu
On Tuesday, August 9, 2022 at 7:57:19 AM UTC-7 jmedley via 
Chromestatus wrote:


My notes say this is shipping in 106. Regardless, please enter the
shipping milestone in the correct fields. (Click Edit all fields,
the scroll to the bottom.) Thanks, Joe

--
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/13fd6dd9-aceb-4fd8-af25-4603d523c478n%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/f2fa2d9e-1da7-edec-5fe6-9a28fede890e%40chromium.org.