Re: [w3c/manifest] Icon purpose "splashscreen" and splashscreen text (#844)

@NotWoods yes I was talking to @andreban before and suggested that we do something like the below. (Based on ScreenLock design).

If you request the splashscreen lock as one of the first things in your code, you can delay the dismissal and avoid adding another splash screen like Twitter does, or you can even find our what image was used and where it exactly was placed in the viewport and then flip to it and add animations

```webidl
[SecureContext]
partial interface Navigator {
  [SameObject] readonly attribute SplashScreenLock splashscreenLock;
};

[SecureContext, Exposed=(Window)]
interface SplashScreenLock {
  Promise<SplashScreenLockSentinel> request(optional SplashScreenLockOptions options);
};

[SecureContext, Exposed=(Window)]
interface SplashScreenLockOptions {
   rootTransition: "none" | "fade-out"
}

[SecureContext, Exposed=(Window)]
interface SplashScreen {
  required DOMRectReadOnly imageBoundingBox;
  required USVString imageSrc;
  DOMString sRGBHex;

}

[SecureContext, Exposed=(Window)]
interface SplashScreenLockSentinel : EventTarget {
  readonly attribute boolean released;

  readonly DOMString backgroundColor // sRGBHex: html#valid-simple-colour
  readonly USVString imagesrc;

  DOMRectReadOnly imageBoundingBox(); // may change with resize

  Promise<undefined> release();
  attribute EventHandler onrelease;
};
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/844#issuecomment-967093110