You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Number: v9.5.39-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#106120 Email or phone of affected tester (no customers):gd868gd+34n@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Desktop / Windows 11 App Component: Other
Action Performed:
Open the Expensify Web App and log in
Enable "resizableRHP" beta override
Go to any chat and click on its header to open the Details
Enable the Screen reader
Press Tab until you reach the left edge of the RHP
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
The web session reported signed in, but displayed a blank page; no resizing or screen-reader reproduction was established. Keep DeployBlockerCash: the responsible implementation is identified, but the failure mechanism remains unconfirmed.
Step
Status
1. Open web app and log inSession state reported authenticated and onboarding complete, but the app rendered blank.
✅
2. Enable resizableRHP beta overrideBlocked by the blank app; no accessible controls were available.
❌
3. Open a chat’s DetailsBlocked: no chat header was accessible.
❌
4. Enable a screen readerReal Windows/Chrome screen-reader testing was unavailable in the Linux headless browser.
❌
5. Tab to the RHP’s left resize edgeNot tested; actual separator focus could not be established.
❌
6. Press Left three times and verify resizingNo runtime width measurements were obtained.
Investigation:Keyboard support and ARIA for the resize handle introduced this behavior and was deployed before the reported staging build. It is the primary candidate—not a confirmed root cause.
The resize handler requires keyboard events reaching the focused separator. The key interpreter rejects modified arrows. Three unmodified Left presses should widen the panel by 24px total, unless clamped at maximum width.
An earlier accessibility-tree defect was already addressed: the merged dialog structure encloses both the panel and resize handle. That earlier defect should not be cited as the shipped cause.
Next action: QA should identify the screen reader/version and interaction mode, start below maximum width, confirm actual separator focus, and compare reader-off/on behavior while checking whether ArrowLeft reaches the handler and aria-valuenow changes. This distinguishes intercepted arrows, focus divergence, and width clamping.
Deploy recommendation: Retain the blocker pending that retest. Reverting the candidate PR removes keyboard resizing rather than restoring previously working behavior; a revert is not yet demonstrated to resolve this report.
@jponikarchuk looks like you're using some screen keyboard to navigate the layout. I tried to reproduce it with the regular keyboard on mac and it worked just fine. Please let me know if this is some custom app, or maybe screen reader opens the keyboard when turned on on windows? I'm afraid I can't reproduce this :/ @Krishna2323 do you have any idea what could have caused this?
@war-in I used the built-in screen keyboard that I enabled in the Windows Accessibility settings separately from the Screen Reader. I used it to display my keyboard actions.
The Screen Reader is also the built-in one.
The issue is also reproducible on Windows Chrome with the physical laptop keyboard.
The issue is also reproducible on Windows Chrome with the physical laptop keyboard.
@jponikarchuk is it also reproducible when the screen reader is off? Did this happen to you in other places that can be resized (table columns with the resizableTableColumns beta on)?
@war-in The issue is reproducible with the resizable columns when the Screen Reader is on, and not reproducible when it’s off (in both columns and RHP).
Activity
melvin-bot commentedon Nov 13, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #106120
applause-bot commentedon Nov 13, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/8816ec5cb2e2fe72ec6140369e3477c4249044817b77e27c4f8c28a103a98524
melvin-bot commentedon Nov 13, 2026
@lakchote @Krishna2323 you have been assigned to this deploy blocker because you reviewed the offending PR: #106120
melvin-bot commentedon Nov 13, 2026
@war-in you have been assigned to this deploy blocker because you authored the offending PR: #106120
melvin-bot commentedon Nov 13, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 13, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
MelvinBot commentedon Nov 13, 2026
🤖 Web test steps verification results:⚠️ partial
The web session reported signed in, but displayed a blank page; no resizing or screen-reader reproduction was established. Keep
DeployBlockerCash: the responsible implementation is identified, but the failure mechanism remains unconfirmed.1. Open web app and log in
Session state reported authenticated and onboarding complete, but the app rendered blank.2. Enable resizableRHP beta override
Blocked by the blank app; no accessible controls were available.3. Open a chat’s Details
Blocked: no chat header was accessible.4. Enable a screen reader
Real Windows/Chrome screen-reader testing was unavailable in the Linux headless browser.5. Tab to the RHP’s left resize edge
Not tested; actual separator focus could not be established.6. Press Left three times and verify resizing
No runtime width measurements were obtained.Investigation: Keyboard support and ARIA for the resize handle introduced this behavior and was deployed before the reported staging build. It is the primary candidate—not a confirmed root cause.
The resize handler requires keyboard events reaching the focused separator. The key interpreter rejects modified arrows. Three unmodified Left presses should widen the panel by 24px total, unless clamped at maximum width.
An earlier accessibility-tree defect was already addressed: the merged dialog structure encloses both the panel and resize handle. That earlier defect should not be cited as the shipped cause.
Next action: QA should identify the screen reader/version and interaction mode, start below maximum width, confirm actual separator focus, and compare reader-off/on behavior while checking whether ArrowLeft reaches the handler and aria-valuenow changes. This distinguishes intercepted arrows, focus divergence, and width clamping.
Deploy recommendation: Retain the blocker pending that retest. Reverting the candidate PR removes keyboard resizing rather than restoring previously working behavior; a revert is not yet demonstrated to resolve this report.
view run · no recording available
3 remaining items
JS00001 commentedon Nov 13, 2026
Lets not block on this
cocvn157 commentedon Nov 14, 2026
war-in commentedon Nov 17, 2026
@jponikarchuk looks like you're using some screen keyboard to navigate the layout. I tried to reproduce it with the regular keyboard on mac and it worked just fine. Please let me know if this is some custom app, or maybe screen reader opens the keyboard when turned on on windows? I'm afraid I can't reproduce this :/
@Krishna2323 do you have any idea what could have caused this?
jponikarchuk commentedon Nov 18, 2026
@war-in I used the built-in screen keyboard that I enabled in the Windows Accessibility settings separately from the Screen Reader. I used it to display my keyboard actions.
The Screen Reader is also the built-in one.
The issue is also reproducible on Windows Chrome with the physical laptop keyboard.
Expensify_7313016_Repro.mp4
war-in commentedon Nov 18, 2026
@jponikarchuk is it also reproducible when the screen reader is off? Did this happen to you in other places that can be resized (table columns with the
resizableTableColumnsbeta on)?jponikarchuk commentedon Nov 18, 2026
@war-in The issue is reproducible with the resizable columns when the Screen Reader is on, and not reproducible when it’s off (in both columns and RHP).
Sreen_Reader_Columns.mp4
expensify-chore-bot commentedon Nov 19, 2026
@Krishna2323 Whoops! This issue is 2 days overdue. Let's get this updated quick!
jakubkalinski0 commentedon Nov 20, 2026
Hi everyone, I'm Jakub from SWM and I'll be looking after this issue next week while @war-in is OOO