2025-02-26 Meeting notes

All public Working Group meetings follow the Recording Policy for Open edX Meetings

Date

Feb 26, 2025

Time	Item	Presenter	Notes

Time

Item

Presenter

Notes

@Adam Stankiewicz

Toast

See prior PWG discussion here.
- Did we decide on children used as a ReactNode (proposed) vs. string (currently supported)?
  - Original use case was not a blocker (FormattedMessage vs. intl.formatMessage).
  - [Adam] My 2C: ideally, we’d have some intentional design forethought into Toast use cases before accepting ReactNode as children, to ensure consistent design patterns with regards to titles, icons, etc. Could these be special props for titles, icons, etc. instead of allowing anything in children?
- We noted a bug with auto-focus. Did this get ticketed?
  - Toast auto-focus not behaving correctly · Issue #3450 · openedx/paragon
There’s no standard way to “stack” toasts, if consuming MFEs do at all (e.g., most Toast implementations tend to re-use an existing Toast on successive actions vs. stacking multiple toasts, which limits user feedback).
- Most toast packages (see below) provide a function (e.g., toast) to be called that makes a Toast visible, stacked if multiple, without each use case worrying about managing toast state for each instance.
  - GitHub - timolins/react-hot-toast: Smoking Hot React Notifications 🔥
  - GitHub - fkhadra/react-toastify: React notification made easy 🚀 !

@Adam Stankiewicz

Need to confirm whether we need to use CSS vars here, and/or calc().

@Brian Smith