pharos
pharos copied to clipboard
ithaka
JSTOR's design system
**The problem** Popovers and dropdowns currently listen for clicks and determine whether the click target is within the body of the component to see if the component should close. The...
**Expected behavior** - A button's rendered content touches all four walls of its real estate - Elements around the button also behave such that those four walls are the button's...
**The problem** I want the project to be on the latest and greatest of as many dependencies as possible to ensure we stay apace of the ecosystem. **The solution** *...
**The problem** Checkboxes can sometimes require contextual information to prevent confusion for users. Users may struggle to understand the purpose of or implications of toggling a checkbox. **The solution** Introduce...
At present, when there is no image available for an image card or a collection card, we show a grey background with an information icon and a message "Image preview...
**The problem** Storybook prefers that the `preview` configuration files be statically-defined, because for some purposes they statically parse the file rather than depending on its runtime behavior (see storybookjs/storybook#27510 and...
**Expected behavior** The side navigation is hidden by default, a menu icon button is present to open the side navigation, and when it is open it has a close button...
**The problem** I want the logs during unit testing to be mostly silent, so that when a message is printed it is a salient signal that there might be something...
**Expected behavior** The page should load as the rest of the component pages do with documentation. **Actual behavior** The page is blank and appears to be broken **Steps to reproduce...
**The problem** There are several instances where having more complex data than just plain text would be useful in a table component, but that currently isn't possible with the way...
