Rand Scullard

FWIW, I just reproduced the error using the CodePen sample from my original bug report (see above). I am using Chrome 106.0.5249.119 on Windows.

I have a suggestion for a change to useNavigate that might resolve this. For the sake of argument, here is a version of useNavigate stripped down to only the parts...

@HansBrende You're right, my useRef suggestion wouldn't prevent the extra renders because of the underlying reference to the LocationContext. Thank you for clarifying! (I think my useRef would help with...

@ryanflorence I agree with @deleteme, I am really more concerned with effects being triggered. Additional renders don't create a problem in my use case. I still think the effect problem...

We just upgraded from Bootstrap 5.1.3 to 5.2.1 and this Popper warning started appearing. We are using margin to offset a dropdown inside our Bootstrap navbar. Apparently we can't use...

Conditional rendering definitely causes problems with react-resize-detector. In my testing, if the referenced element doesn't exist when useResizeDetector is first called, you will never get a resize notification - even...

You probably don't want to turn off source map generation for your entire project, but you can suppress the source map warnings from rrule and get a clean build. The...

> Where you have added it? @IvanGrekov Check out the comment I referenced. I did it the way they described.

@jladbury The WCAG 2 version of isReadable works great, it's just the current application of that function to mostReadable that creates a problem. I think I have a solution: Change...

I disagree that WCAG2 "seeks to achieve the latter, at the expense of the former." If anything, WCAG2 wisely takes a very conservative position on the question of readability; for...