Skip to content

[CP Staging] Revert "Fix disabled Next button not announced as disabled by screen readers"#82602

Merged
mountiny merged 1 commit intomainfrom
revert-81779-mavrickdeveloper/fix-disabled-next-button-sr-announcement
Feb 17, 2026
Merged

[CP Staging] Revert "Fix disabled Next button not announced as disabled by screen readers"#82602
mountiny merged 1 commit intomainfrom
revert-81779-mavrickdeveloper/fix-disabled-next-button-sr-announcement

Conversation

@AndrewGable
Copy link
Contributor

@AndrewGable AndrewGable commented Feb 16, 2026

Reverts #81779

Fixed Issues

$ #81779

@github-actions
Copy link
Contributor

🚧 @AndrewGable has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@mountiny mountiny changed the title Revert "Fix disabled Next button not announced as disabled by screen readers" [CP Staging] Revert "Fix disabled Next button not announced as disabled by screen readers" Feb 17, 2026
@mountiny mountiny marked this pull request as ready for review February 17, 2026 12:41
@mountiny mountiny requested review from a team as code owners February 17, 2026 12:41
@melvin-bot melvin-bot bot requested review from JS00001 and joekaufmanexpensify and removed request for a team February 17, 2026 12:41
@melvin-bot
Copy link

melvin-bot bot commented Feb 17, 2026

@JS00001 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Straight revert

@mountiny mountiny merged commit 2ac413a into main Feb 17, 2026
33 of 37 checks passed
@mountiny mountiny deleted the revert-81779-mavrickdeveloper/fix-disabled-next-button-sr-announcement branch February 17, 2026 12:44
@melvin-bot
Copy link

melvin-bot bot commented Feb 17, 2026

@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@github-actions
Copy link
Contributor

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@mountiny
Copy link
Contributor

Not emergency, straight revert

OSBotify pushed a commit that referenced this pull request Feb 17, 2026
…r/fix-disabled-next-button-sr-announcement

[CP Staging] Revert "Fix disabled Next button not announced as disabled by screen readers"

(cherry picked from commit 2ac413a)

(cherry-picked to staging by mountiny)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Feb 17, 2026
@OSBotify
Copy link
Contributor

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.3.20-4 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.20-6 🚀

platform result
🕸 web 🕸 cancelled 🔪
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants