LGTM3 On Wednesday, September 2, 2026 at 11:13:19 AM UTC-4 Yoav Weiss wrote:
> LGTM2 > > On Wed, Sep 2, 2026 at 5:12 PM Rick Byers <[email protected]> wrote: > >> LGTM1 >> >> On Wed, Aug 26, 2026 at 3:47 PM 'Munira Tursunova' via blink-dev < >> [email protected]> wrote: >> >>> *Contact emails* >>> [email protected] >>> >>> *Explainer* >>> https://webkit.org/blog/17285/rolling-the-dice-with-css-random >>> https://css-tricks.com/almanac/functions/r/random >>> >>> *Specification* >>> https://www.w3.org/TR/css-values-5/#random >>> >>> *Summary* >>> The random() function brings generative randomness to CSS, allowing web >>> authors to generate a random numeric value within a specified range. For >>> example, web authors can use random() to scatter elements randomly within >>> their container: >>> >>> .dot { >>> /* Position each dot randomly */ >>> position: absolute; >>> top: random(0%, 100%); >>> left: random(0%, 100%); >>> } >>> >>> This feature also includes caching controls. By default, each random() >>> function resolves to a new, distinct value. Web authors can override this >>> default by passing a <random-key> value as the function's first argument to >>> control how random values are shared across properties and elements. >>> >>> *Blink component* >>> Blink>CSS >>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >>> >>> *Web Feature ID* >>> Missing feature >>> >>> *Motivation* >>> The CSS random() function provides a native way to generate random >>> values directly in CSS without relying on JavaScript, reducing code >>> complexity while making it easier for developers to create varied and >>> dynamic designs. >>> >>> *Initial public proposal* >>> *No information provided* >>> >>> *Search tags* >>> random <https://chromestatus.com/features#tags:random> >>> >>> *TAG review* >>> *No information provided* >>> >>> *TAG review status* >>> Pending >>> >>> *Goals for experimentation* >>> None >>> >>> *Risks* >>> >>> >>> *Interoperability and Compatibility* >>> Low, shipped in Safari and positive signals from Firefox >>> >>> *Gecko*: Positive ( >>> https://github.com/mozilla/standards-positions/issues/809) >>> >>> *WebKit*: Shipped/Shipping ( >>> https://webkit.org/blog/17285/rolling-the-dice-with-css-random) >>> >>> *Web developers*: No signals >>> >>> *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? >>> *No information provided* >>> >>> >>> *Debuggability* >>> Currently not supported in DevTools value debugger. Might be hard to >>> support since we need to know the specified random value position for >>> caching. See: issues.chromium.org/issues/40068516. >>> >>> *Will this feature be supported on all six Blink platforms (Windows, >>> Mac, Linux, ChromeOS, Android, and Android WebView)?* >>> Yes >>> >>> *Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >>> Yes >>> >>> https://wpt.fyi/results/css/css-values?label=master&label=experimental&aligned&q=random >>> >>> *Flag name on about://flags* >>> *No information provided* >>> >>> *Finch feature name* >>> CSSRandomFunction >>> >>> *Rollout plan* >>> Will ship enabled for all users >>> >>> *Requires code in //chrome?* >>> False >>> >>> *Tracking bug* >>> https://issues.chromium.org/issues/413385732 >>> >>> *Estimated milestones* >>> Shipping on desktop 155 >>> Shipping on Android 155 >>> >>> *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). >>> *No information provided* >>> >>> *Link to entry on the Chrome Platform Status* >>> https://chromestatus.com/feature/5324559251275776?gate=6579011069280256 >>> >>> -- >>> 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 visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAO7W_BJPLpBboYSF9%2BJrrRv8Obi%3DtUDXRw3BJvpuJd9TzVqKg%40mail.gmail.com >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAO7W_BJPLpBboYSF9%2BJrrRv8Obi%3DtUDXRw3BJvpuJd9TzVqKg%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 visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY_qHd4swn0H_csNasixsX4GAKmE-GMtEdjQFvpTDF12Ow%40mail.gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY_qHd4swn0H_csNasixsX4GAKmE-GMtEdjQFvpTDF12Ow%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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fa9c24b7-b92a-46e5-ba0d-15e76ed92673n%40chromium.org.
