Scott Vachalek

Worked for me just using next's built-in `Head` element too: ``` import Head from "next/head"; import { config, dom } from "@fortawesome/fontawesome-svg-core"; config.autoAddCss = false; ... return ( {dom.css()} ......

Seems sensible to warn about, if it's specified explicitly. AFAIK our UIs don't add step= unless a user specifies it, which is pretty rare. Most of the time, it's trying...

The UI could potentially offer searching longer time spans in exchange for certain restrictions (prefixed, case-sensitive regexes only) but this forces users to remember better what they are searching for;...

Option 3 seems good. The default could be based on the statistic tag, or the UI could interpret the statistic tag to set a reasonable value. For consistent formatting, possibly...

Sorry, didn't see the question earlier. Probably for readability, a list like ```(,max,avg,count,),:stats``` would work best.

A lot of time has passed and I'm not even working on the project that was using this button anymore, but just to clarify the discussion: the problem is not...

Came here looking to find the history on just this issue. This is by far the most common bug I have seen with promises, particularly the `Promise` case.

I'm getting it when trying to upscale, so lowering resolution works but defeats the whole point.