Oleksandr Fediashov

@sopranopillow see also https://github.com/microsoft/fluentui/issues/27955#issuecomment-1559595354.

FYI It's a general issue and happens for other components, too.

Closing for housekeeping 🏡

@Hotell AFAIR Node 16 can run it, Node 18 is required only for one of storage adapters to use native fetch.

> It's a little flaky, sometimes the position is correct but sometimes is not.  I was able to reproduce the issue: positioning is broken randomly, but it reproduces frequently.

@samavati looks that it happens on initial render of a tooltip: so open CodeSandbox, hover a button, it repros like on my screenshot.

The bug is tricky as it's related to the layout of that page. - When we compute position a tooltip appear on a bottom of a page - That state...

I spent some time looking on this and here are some concerns/observations related to this. Both Fluent UI React v0 & v8 are using runtime CSS-in-JS, that allows them to...

@NotWoods thanks for feedback. Actions there: - Check if `unicode-range` option works and we have proper fonts on CDN - Propose an opt-in solution to create `@font-face` definitions via RFC...

> Hey @MLoughry, I work at Microsoft FX Search and we have a similar problem where we have multiple render roots, and ideally we would like only one React context...