Remove duplicate .nav-links CSS selector

[Copilot]

Summary

Addresses feedback from #15566 (review comment) to remove duplicate .nav-links selector in website/style.css.

Changes:

• Removed redundant .nav-links selector (lines 1038-1040) that only set display: none
• Kept complete selector (lines 1038-1052) with all mobile menu styles including display: none

Before:

.nav-links {
    display: none;
}
.nav-links {
    display: none;
    flex-direction: column;
    background: rgba(48,48,48,0.98);
    /* ... rest of mobile menu styles */
}

After:

.nav-links {
    display: none;
    flex-direction: column;
    background: rgba(48,48,48,0.98);
    /* ... rest of mobile menu styles */
}

Test plan

Validated CSS syntax (balanced braces) and tested mobile navigation rendering at 375px viewport.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/15850

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 3 New Failures, 68 Pending

As of commit 046e167 with merge base be8b775 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2
• pull / unittest-buck / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2
• pull / unittest-editable / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 2

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @Copilot!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!