RFC Start Date
2026-08-31
Target Plan Accepted Date
2026-09-14
Target Transition Unblocked Date
2026-09-14
Earliest Breaking Changes Unblocked Date
2026-10-14
Earliest Open edX Named Release with Breaking Changes
Willow - 2026-10
Rationale
The org.openedx.frontend.layout.learning_header_actions.v1 plugin slot is gated behind both showUserDropdown and authenticatedUser, tying it to the visibility of the user dropdown menu. This is unintended: showUserDropdown should only control the AuthenticatedUserDropdown, not the header's action items (notifications tray, help link, and any plugin content injected into this slot). This prevents consumers who set showUserDropdown={false} from still showing notifications/help, and prevents third-party plugins attached to this slot from rendering independently of that flag. See #676
Removal
- Remove the
org.openedx.frontend.layout.learning_header_actions.v1 slot, defined in LearningHeaderActionsSlot/v1/index.jsx, which currently wraps HeaderNotificationsSlot and LearningHelpSlot and is only rendered by v2 when showUserDropdown is true.
- Delete the
v1/ directory entirely. The shared images/ folder stays, since its screenshots remain valid for v2.
- The root index.jsx will drop the
LearningHeaderActionsSlotV1 named export.
Replacement
Replaced by the org.openedx.frontend.layout.learning_header_actions.v2 slot, defined in LearningHeaderActionsSlot/v2/index.jsx. Once v1 is removed, v2 will render HeaderNotificationsSlot and LearningHelpSlot directly and unconditionally, no longer gated by showUserDropdown.
Deprecation
Mark org.openedx.frontend.layout.learning_header_actions.v1 as deprecated in v1/README.md and in the plugin slots index, pointing consumers to .v2.
Open question: Is there no native way to deprecate a plugin slot?
Additional Info
No response
Transition Unblocked Tasks
Feature Removal Tasks
RFC Start Date
2026-08-31
Target Plan Accepted Date
2026-09-14
Target Transition Unblocked Date
2026-09-14
Earliest Breaking Changes Unblocked Date
2026-10-14
Earliest Open edX Named Release with Breaking Changes
Willow - 2026-10
Rationale
The
org.openedx.frontend.layout.learning_header_actions.v1plugin slot is gated behind bothshowUserDropdownandauthenticatedUser, tying it to the visibility of the user dropdown menu. This is unintended:showUserDropdownshould only control theAuthenticatedUserDropdown, not the header's action items (notifications tray, help link, and any plugin content injected into this slot). This prevents consumers who setshowUserDropdown={false}from still showing notifications/help, and prevents third-party plugins attached to this slot from rendering independently of that flag. See #676Removal
org.openedx.frontend.layout.learning_header_actions.v1slot, defined in LearningHeaderActionsSlot/v1/index.jsx, which currently wrapsHeaderNotificationsSlotandLearningHelpSlotand is only rendered by v2 whenshowUserDropdownis true.v1/directory entirely. The sharedimages/folder stays, since its screenshots remain valid forv2.LearningHeaderActionsSlotV1named export.Replacement
Replaced by the
org.openedx.frontend.layout.learning_header_actions.v2slot, defined in LearningHeaderActionsSlot/v2/index.jsx. Oncev1is removed,v2will renderHeaderNotificationsSlotandLearningHelpSlotdirectly and unconditionally, no longer gated byshowUserDropdown.Deprecation
Mark
org.openedx.frontend.layout.learning_header_actions.v1as deprecated in v1/README.md and in the plugin slots index, pointing consumers to.v2.Open question: Is there no native way to deprecate a plugin slot?
Additional Info
No response
Transition Unblocked Tasks
v2slot: feat: Add V2 of header actions slot #682v1as deprecated inv1/README.mdandplugin-slots/README.mdpluginSlotsconfig from.v1to.v2Feature Removal Tasks
v1/directory (index.jsx,README.md)v2/index.jsxto renderHeaderNotificationsSlotandLearningHelpSlotdirectly and unconditionallyLearningHeaderActionsSlotV1named export from the rootindex.jsxREADME.mdandHeaderNotificationsSlot/README.mdto remove references to.v1