This enables individual control over whether a shadow root is clonable (via standard platform cloning commands such as `cloneNode()`). By default, declarative shadow roots are clonable. Imperative shadow roots can now be controlled via a parameter to `attachShadow()`.
None
This is a slight change in behavior, which poses a very small compat risk. Prior to this feature, only declarative shadow roots within `<template>` elements would get automatically cloned. With the change, any declarative shadow root, even in the main page, will get cloned. Safari already shipped the new behavior, reducing the risk. I plan to enable this functionality slowly and monitor for breakage and bug reports.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
https://wpt.fyi/results/shadow-dom/declarative/clonable.window.html
No milestones specified