Jack Steinberg

Additional Considerations for position: - The positions suggested are as follows: - `"top-left"` - `"top-center"` - `"top-right"` - `"middle-left"` - `"middle-center"` - `"middle-right"` - `"bottom-left"` - `"bottom-center"` - `"bottom-right"` -...

I did a brief survey of the default positioning for libraries and got these results: - Top-right (3): react-toastify, ngx-toastr, Sweet Alert 2 - Bottom-stretch (3): Ionic, Android Snackbar, Android...

Vertical writing mode is an interesting concept to consider, which we could combat using [logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Logical_Properties/Basic_concepts), which is interesting and worth looking into. As far as stretch is concerned we...

Thank you for creating an issue to discuss these, this has been really helpful for the accessibility research which is currently our highest-priority task. After exploring these roles, the specs...

Within the time I took to research existing toast implementations I didn’t spend the time accessibility testing each, and now that I am creating a more in-depth accessibility study I...

Thank you for mentioning the `dialog` and `log` roles, we need to look further into those as we progress in our accessibility study to see if they would make sense...

I agree with the sentiment that the name `theme` doesn’t quite capture the essence of the feature; that different toasts should be treated differently, in more than just a cosmetic...

After having spent some time looking into accessibility concerns it seems to me that the current default of 2000ms is too short. Furthermore, having an action-toast disappear while you intend...

I like (1) most as a strategy, but I agree that it seems strange to change the `closeButton` on a toast as a side effect of changing the duration. In...