Exercise 2: Links Still Open in the Old Browser After Switching — Possible Solution
====================================================================

WHAT'S ACTUALLY HAPPENING
------------------------------
Per this chapter, "Windows 11 made a deliberate, publicly documented
change here from Windows 10: there's no longer a single 'Set as default
browser' button that reassigns every relevant file type and protocol at
once. Each file type and each protocol must be set individually, one at
a time." The user most likely set the new browser as default for one
association (perhaps by clicking "Set as default" inside the new
browser's own settings, which typically sets only a subset) without
separately setting every relevant file type and protocol - most
importantly <code>http</code> and <code>https</code>, the protocols
that actually govern which browser opens when a link is clicked.

WHY THIS ISN'T A BUG OR A MISSED SETTING
------------------------------
Per this chapter's own warn-box, this is "a real, deliberate friction
point... not a bug or a missing feature the user simply hasn't found
yet." The old browser opening some links isn't a leftover glitch to
troubleshoot away - it's the direct, expected result of Windows 11's
own per-association default-setting design working exactly as
Microsoft built it.

WHAT THE USER NEEDS TO DO DIFFERENTLY
------------------------------
Per this chapter, the fix is going to Settings > Apps > Default apps,
selecting the new browser specifically, and individually setting each
relevant association - critically including <code>.htm</code>,
<code>.html</code>, <code>http</code>, and <code>https</code>, as this
chapter names them by name - rather than assuming one click inside the
new browser (or one click anywhere) reassigns everything at once the
way it did in Windows 10.

WHY THIS IS WORTH EXPLAINING RATHER THAN JUST FIXING
------------------------------
Per this chapter, this change is "widely reported as a response to
antitrust scrutiny over steering users back toward Edge" - understanding
that this is a deliberate platform decision, not a fixable bug, helps
set the right expectation for the user (and for any future browser
switch they make) rather than treating each occurrence as a fresh
mystery to diagnose.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the missing http/https association as the likely direct
cause, explains why this chapter frames it as deliberate friction
rather than a bug, and gives the specific corrective steps (setting
each association individually in Default apps) rather than a vague
"check your browser settings" answer.