Matt Nolting

Notes from 5/14 discussion @mcoker @srambach **Q:** Why should we remove `:where()` **A:** It may be an anti-pattern, but we will look into this. The more important aspect of this...

# Notes from 5/15 community meeting ### Useful links **Issues** Cascade layers: ([proposal PR](https://github.com/patternfly/patternfly/pull/6567)) Root scoping: ([proposal PR](https://github.com/patternfly/patternfly/issues/6647)) **Resources** * https://devtoolstips.org/tips/en/find-expensive-selectors/ * https://csswizardry.com/2011/09/writing-efficient-css-selectors/ * https://blogs.windows.com/msedgedev/2023/01/17/the-truth-about-css-selector-performance/ ## Potential issues * Should...

> I wonder if something like [data-reset="selector"].pf-v6-reset could work? Going from right to left with [bottom-up parsing](https://en.wikipedia.org/wiki/Bottom-up_parsing) ([like CSS selector matching does](https://stackoverflow.com/questions/5797014/why-do-browsers-match-css-selectors-from-right-to-left/5813672#5813672)), it'd look for everything with the class first,...

## TLDR ### toggle group shouldn't be inside pf-v6-c-menu__item-text. React followup is here: [10406](https://github.com/patternfly/patternfly-react/issues/10406) ---- ## Core issue The issue is with `toggle-group` (and other components) whose reduced parent size...

TLDR: toggle group shouldn't be inside `pf-v6-c-menu__item-text`.

> OK, what's the advisable way to include the toggle group inside the menu? Is it to drop `pf-v6-c-menu__item-text`? That is correct.

> * We should take out the styling that adds `aspect-ratio` to a button. The plain button handles this as specified by design with a `min-width`, which purposefully lets the...