Hi Mustaq,

On 4/21/22 11:05 AM, Mustaq Ahmed wrote:


        Contact emails

[email protected], [email protected]


        Explainer

https://github.com/WICG/capability-delegation <https://github.com/WICG/capability-delegation>


        Specification

https://wicg.github.io/capability-delegation/spec.html <https://wicg.github.io/capability-delegation/spec.html>

(Work in progress for fullscreen algorithm change: https://github.com/WICG/capability-delegation/pull/28 <https://github.com/WICG/capability-delegation/pull/28>)


        Design doc

https://docs.google.com/document/d/1ax54Lf2W3_TovVOj35duKTbcOlXe-nJ-KQdWiy1Ye0c <https://docs.google.com/document/d/1ax54Lf2W3_TovVOj35duKTbcOlXe-nJ-KQdWiy1Ye0c>


        Summary

This feature is based on the general delegation mechanism (https://chromestatus.com/feature/5708770829139968 <https://chromestatus.com/feature/5708770829139968>) shipped on M100.


Fullscreen Capability Delegation allows a Window to transfer the ability to call requestFullscreen() to another Window it trusts after relinquishing the transient user activation at the sender Window.

Does this only work for standard requestFullscreen, or will it work for webkitRequestFullscreen as well?


        Blink component

Blink>Fullscreen <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFullscreen>


        TAG review

Covered by the review for the general delegation mechanism: https://github.com/w3ctag/design-reviews/issues/655 <https://github.com/w3ctag/design-reviews/issues/655>


        TAG review status

Covered by the approval for the general delegation mechanism:https://github.com/WICG/capability-delegation/pull/23 <https://github.com/WICG/capability-delegation/pull/23>


        Risks

Interoperability and Compatibility risks remain unchanged from the general delegation mechanism; see that intent here: https://groups.google.com/a/chromium.org/g/blink-dev/c/PHT_2X7oRBE/m/gR9UiZxBAQAJ <https://groups.google.com/a/chromium.org/g/blink-dev/c/PHT_2X7oRBE/m/gR9UiZxBAQAJ>


        External signals

Gecko:Positive (https://github.com/mozilla/standards-positions/issues/565 <https://github.com/mozilla/standards-positions/issues/565>, also see: https://github.com/WICG/capability-delegation/issues/10 <https://github.com/WICG/capability-delegation/issues/10>)

I don't think these quite count as official Positive signals (but yes, the comments from Anne are promising!). Can we ping the standards-position issue and ask for one?

WebKit:No signal

Have we asked? I looked at the Payment Request, and it seems like we didn't, but maybe I'm looking in the wrong spot. If not, can we?

Web developers:Positive (https://crbug.com/931966#c5 <https://crbug.com/931966#c5>)


        Debuggability

This remains unchanged from the general intent: https://groups.google.com/a/chromium.org/g/blink-dev/c/PHT_2X7oRBE/m/gR9UiZxBAQAJ <https://groups.google.com/a/chromium.org/g/blink-dev/c/PHT_2X7oRBE/m/gR9UiZxBAQAJ>


        Ongoing technical constraints

None.


        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
        
<https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>?

Not yet

Is there something missing to test this (or capability detection in general), or is it just that you haven't written the WPTs yet?


        Flag name

--enable-blink-features=CapabilityDelegationFullscreenRequest


        Requires code in //chrome?

Yes, work in progress


        Tracking bug

https://crbug.com/1293083 <https://crbug.com/1293083>


        Estimated milestone

103


        Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6441688242323456 <https://chromestatus.com/feature/6441688242323456>


        Links to previous Intent discussions

Intents for the general delegation mechanism:

 *

    I2P:
    
https://groups.google.com/a/chromium.org/g/blink-dev/c/9CeLYndESPE/m/AhEttheMBQAJ
    
<https://groups.google.com/a/chromium.org/g/blink-dev/c/9CeLYndESPE/m/AhEttheMBQAJ>

 *

    I2E (with Payment Request):
    
https://groups.google.com/a/chromium.org/g/blink-dev/c/i6pAWsjU7zg/m/UK0lGnKuAAAJ
    
<https://groups.google.com/a/chromium.org/g/blink-dev/c/i6pAWsjU7zg/m/UK0lGnKuAAAJ>

I2S (with Payment Request): https://groups.google.com/a/chromium.org/g/blink-dev/c/PHT_2X7oRBE/m/gR9UiZxBAQAJ <https://groups.google.com/a/chromium.org/g/blink-dev/c/PHT_2X7oRBE/m/gR9UiZxBAQAJ>
--
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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAB0cuO63mt3wbrDHhy7ieb4yAwd0YNhmQM11Mdg3eXfhpt558g%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAB0cuO63mt3wbrDHhy7ieb4yAwd0YNhmQM11Mdg3eXfhpt558g%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e95f9057-7aa0-a758-470b-65e4d0cf04d5%40chromium.org.

Reply via email to