Repository navigation
Fix responsive V2 chat table overflow - #1913
Merged
Paul Lizer (paullizer) merged 1 commit intoNov 10, 2026
Merged
Paul Lizer (paullizer) merged 1 commit into
Paul Lizer (paullizer) merged 1 commit into
Conversation
Expand table-bearing assistant replies within the conversation, wrap long cell content, and contain remaining overflow in keyboard-accessible table regions. Add responsive regression coverage and fix documentation, and bump the app to 0.261.425. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Nov 10, 2026
f292209
into
microsoft:Development
13 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.261.425.Linked issue
N/A. The user requested proceeding without a GitHub issue.
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedApplication:
0.261.424->0.261.425. No deployer changes.Testing / validation
npm --prefix .\application\v2_ui run build -- --outDir ..\..\ui_tests\artifacts\orchestration-plan-editor- passed TypeScript compilation and production build; Vite reported its existing large-chunk warning.python .\functional_tests\test_v2_chat_table_layout.py- 3 passed.python .\functional_tests\test_v2_mobile_layout.py- 5 passed.python -m pytest .\ui_tests\test_v2_chat_table_layout.py .\ui_tests\test_v2_mobile_chat_layout.py -q --tb=short- 18 passed (9 table regressions and 9 existing mobile regressions). Covers 320-1920px viewports, both themes/width preferences, resizing, citations, streaming/finalization/reload, and keyboard scrolling to the last column.python .\functional_tests\test_docs_site_quality.py- 6/6 checks passed.git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check- passed.Known baseline failures: The adjacent orchestration streaming suite has missing pending-input API stubs and an outdated
Review the running planbutton expectation.python -m pytest .\ui_tests\test_v2_orchestration_streaming_bubble.py -q -k "a_run_shows_only" --tb=shortreproduced 1 assertion failure and 1 teardown error with all three production UI files restored to their original source. These unrelated tests were left unchanged. UI detector findings concern an existing activity animation and a false positive matching<img>in an accessibility comment, not this change.Documentation
Added
docs/explanation/fixes/V2_CHAT_TABLE_OVERFLOW_FIX.md. Release notes remain unchanged: approval was requested, but the user was unavailable. No new capability or control requires feature documentation.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No routes or settings-response boundaries changed. Markdown keeps semantic React rendering with raw HTML disabled. Build outputs, screenshots, and other local test artifacts are not committed.