Skip to content

Fix Agent 365 guide navigation and feedback access - #539

Merged
Alejandro Lopez (soyalejolopez) merged 1 commit into
microsoft:masterfrom
soyalejolopez:soyalejolopez-a365-guide-navigation
Sep 14, 2026
Merged

Alejandro Lopez (soyalejolopez) merged 1 commit into
microsoft:masterfrom
soyalejolopez:soyalejolopez-a365-guide-navigation

Conversation

@soyalejolopez

Copy link
Copy Markdown
Member

Summary

Fixes two reported issues in the public Microsoft Agent 365 Customer Implementation Guide: Detailed navigation did not bring the selected section into view, and readers could not find where to submit feedback.

Root cause

Detailed navigation updated the active panel state without scrolling to it. Because the guide keeps its sections visible for continuous reading, selecting an item could leave the overview on screen. The shared header also lacked a feedback entry point.

Changes

  • Scroll the selected Detailed section into view after activation, for both clicks and Arrow/Home/End keyboard navigation.
  • Respect the reader's reduced-motion preference.
  • Keep all Detailed sections and task content available rather than hiding them to simulate tabs.
  • Add a native Submit feedback link to the shared header in both Simple and Detailed modes, pointing to https://github.com/microsoft/FastTrack/issues.
  • Update the guide version and changelog to 1.1.1.
  • Preserve the latest upstream diagrams, preview assets, and Roadmap removal. Only the guide HTML, README, and changelog change.

Validation

  • npm run check passed.
  • Browser validation covered mouse and Arrow/Home/End navigation, reduced motion, Simple/Detailed switching, feedback availability, and browser console errors.
  • All 17 Detailed panels and 65 task cards remain available.
  • Independently reviewed with GPT 5.6 Sol following the Claude 4.8 UI implementation.
  • Final branch comparison contains only three intended files; the working tree is clean.

Preview behavior

The feedback control is a native link and does not require JavaScript. Detailed navigation still requires scripting; this change does not claim to enable interactive controls in viewers that disable scripts or block embedded frames.

Scope

No product guidance changes, external feedback submissions, or changes outside the deployment guide. Built on upstream commit 50e7ecb99c034dcfb9e0d0cf4629a549091092da.

Scroll detailed navigation targets into view with reduced-motion support and add an accessible native feedback link.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@soyalejolopez
Alejandro Lopez (soyalejolopez) merged commit 35e9901 into microsoft:master Sep 14, 2026
4 checks passed
@soyalejolopez
Alejandro Lopez (soyalejolopez) deleted the soyalejolopez-a365-guide-navigation branch September 14, 2026 21:09
@github-actions

Copy link
Copy Markdown
Contributor

🛰️ PR Sweeper report

Risk: 🟢 LOW · Security gate: ✅ passing · Files: 3

🔒 Automated guardrails (authoritative)

No secret, PII, file-policy, or scope issues detected. ✅

🤖 Dual-model AI review (advisory)

AI review unavailable for this run (models not reachable or no diff). Guardrails above are unaffected.

  • GPT-class reviewer (openai/gpt-5): skipped — GitHub Models HTTP 410: {"error":{"code":"github_models_retirement_brownout","message":"GitHub Models is temporarily unavailable as part of a scheduled retirement brownout."}}

  • Deep-reasoning reviewer (openai/o3): skipped — GitHub Models HTTP 410: {"error":{"code":"github_models_retirement_brownout","message":"GitHub Models is temporarily unavailable as part of a scheduled retirement brownout."}}


The automated guardrails are authoritative and gate the security status. The AI review is advisory and never auto-merges. Thanks for contributing to FastTrack! 🛩️

@github-actions github-actions Bot added the sweeper:risk-low PR Sweeper: low risk label Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sweeper:risk-low PR Sweeper: low risk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants