Sebastian "Sebbie" Silbermann
Sebastian "Sebbie" Silbermann
Reopening since the [PR that would implement this feature](https://github.com/facebook/react/pull/17473#issuecomment-760298266) is still open.
It sounds like the expected behavior described by @FenzaFenz but without a clear reproduction (minimal code that reproduces the issue ideally with [codesandbox](https://react.new/) or cloneable repository) it's hard to tell.
> Unfortunately I cannot reproduce, but what appears to be a headless chrome87 scanner fairly consistently reproduces the issue. Could you create a cloneable repository that has the minimal amount...
Portals specifically allow breaking DOM order. One use case is z-index but it's also any other style cascading (which is called out in the docs for `overflow: hidden`). But changing...
> "Do not use to implement disclosure, combobox, or tooltip patterns as this will break DOM order." Just because DOM order is changed, doesn't necessarily mean these a11y patterns do...
If you want to measure performance you're most likely better off using [`React.Profiler`](https://reactjs.org/docs/profiler.html) like so `` > Logging 'measure' after is inserted into right place and being visible. Could you...
> as [doc](https://beta.reactjs.org/learn/synchronizing-with-effects#how-to-handle-the-effect-firing-twice-in-development) says the do something should be only logged once. The docs don't say that. They say you should do the cleanup to fix issues caused by running...
> I understood the cleanup is to fix issues caused by double firing. Yes and it does. > My point is that if the logic handling under the local variable...
It doesn't look like this bug report has enough info for one of us to reproduce it. Please provide a CodeSandbox (https://react.new), or a link to a repository on GitHub....
This looks like you're transpiling to the JSX runtime for development while using react in production. Could you provide a complete, minimal reproduction of the issue?