Joachim Schuler

Hi, This still is buggy in v0.5.8 http://plnkr.co/edit/3YoIOChUnxmghFlKtPZT?p=preview Thanks

What if we left the old API in place, and added a new option for consumers to use who want to pass react strict mode? Example: > Popper.tsx ``` return...

Noticed that I had to click multiple times on the trigger for the menu to show in this example https://patternfly-react-pr-7807.surge.sh/demos/composable-menu/#composable-strict-mode-dropdown

Looks like there are state updates even if the width has not changed, could be potential reason behind the issue https://github.com/patternfly/patternfly-react/blob/e688e3b26385dc09280dca250d72a733ce18b52a/packages/react-core/src/components/Page/Page.tsx#L201 Perhaps wrapping it in a conditional can help alleviate...

As a workaround I am resorting to adding `` and increment `stateVariable` whenever I want to change the input to force a re-render.

@michpetrov thank you, you're correct. I've updated the example and my description of the issue which is more accurately about clearing the error state of an invalid datepicker input.

Nice, cleans up the side nav (in local workspaces we see it listed under Extensions). Of course visibility in pf.org will be a wider discussion, but that is not what...

I think @tlabaj meant that the QE team would update the code to enable OUIA IDs. If you have team members that would like to contribute those changes to PatternFly...

Came across this issue, I've recently added composable Table components and they appear more performant on the surface. I didn't dig in too much but I've created examples here: Heavyweight...

@AjayJagan yes, i have created examples http://patternfly-react.surge.sh/extensions/virtual-scroll-table#using-composable-table-components and http://patternfly-react.surge.sh/extensions/virtual-scroll-window-scroller#using-composable-table-components