Change Details

Echo currently maintains 2 versions of the badge that users interact with: - The initial server side rendered version (usually rendered by skins)) - A client side OOUI version that is rendered when the badge is clicked (replacing the existing version) We've accumulated various technical debt over the years of skins having to maintain their own styles whenever the OOUI button is rendered # Proposed solution Please progressively enhance the existing button rather than replacing it.

Echo currently maintains 2 versions of the badge that users interact with: - The initial server side rendered version (usually rendered by skins)) - A client side OOUI version that is rendered when the badge is clicked (replacing the existing version) We've accumulated various technical debt over the years of skins having to maintain their own styles whenever the OOUI button is rendered # Proposed solution Please progressively enhance the existing button rather than replacing it. # QA [] When clicking the button a PopupWidget should be shown pointing to the existing button [] Hooks should be used to update the notification count

Echo currently maintains 2 versions of the badge that users interact with: - The initial server side rendered version (usually rendered by skins)) - A client side OOUI version that is rendered when the badge is clicked (replacing the existing version) We've accumulated various technical debt over the years of skins having to maintain their own styles whenever the OOUI button is rendered # Proposed solution Please progressively enhance the existing button rather than replacing it. # QA [] When clicking the button a PopupWidget should be shown pointing to the existing button [] Hooks should be used to update the notification count