Steps to repro:

1. Navigate to https://tests.peter.sh/notification-generator/
2. Grant notification permission
3. Go to chrome://settings/content/notifications
4. Add 'https://tests.peter.sh' to the blocked list via the 'Add' button which provides a free-form text box.

Observed results:
- https://tests.peter.sh is added to the block list (expected) BUT https://tests.peter.sh:443 still appears under the 'Allow' list
- Typing 'Notification.permission' in the devtools console on https://tests.peter.sh/notification-generator/ returns 'allowed' and notifications can still display.

Expected results:
- https://tests.peter.sh appears in the block list AND https://tests.peter.sh:443 disappears from 'Allow' list
- Typing 'Notification.permission' in the devtools console on https://tests.peter.sh/notification-generator/ returns 'blocked' and notifications do not display.

----

Note that if permission was never granted for https://tests.peter.sh:443, blocking https://tests.peter.sh manually via the 'Add' button does block the site as expected.

Note also this is not an issue on mobile because sites cannot be added manually to the block/allow list on mobile.

---------------


The observed behaviour is arguably logical but very confusing for users who think they have blocked the site but actually they haven't because permission was still granted on the default port. E.g.  Issue 807523  ('Notifications for google maps show even though set to blocked')