Add History page feature

[greyivy]

Asana Task/Github Issue: https://app.asana.com/0/0/1208850639107971/f

Description

Adds a new web-based History page feature (for use on Windows and macOS). Distinct to the less-specific https://github.com/duckduckgo/privacy-configuration/blob/main/features/history.json feature and follows https://github.com/duckduckgo/privacy-configuration/blob/main/features/html-new-tab-page.json naming convention.

Feature change process:

• I have added a schema to validate this feature change
• I have tested this change locally
• This code for the config change is ready to merge
• This feature was covered by a tech design

Additional info:

• I have tested this change locally in all supported browsers
• This change will be visible to users
• This code for the config change is ready
• This change was covered by a ship review

Site breakage mitigation process:

Brief explanation

• Reported URL:

• Problems experienced:

• Platforms affected:

  • iOS
  • Android
  • Windows
  • MacOS
  • Extensions

• Tracker(s) being unblocked:

• Feature being disabled:

• I have referenced the URL of this PR as the "reason" value for the exception (where applicable).

• This change is a speculative mitigation to fix reported breakage.

Reference

• Config Reviewer Documentation
• Config Maintainer Documentation
• Feature Implementer Documentation

[github-actions]

Don't forget to add an individual reviewer (in addition to those already added, this should create a task for them in Asana).
- The best reviewer is most likely a feature or platform owner.
- If they've got permission to approve, you're good to merge. See CODEOWNERS
- As a fallback the Global owners are:
- Breakage AOR
- Breakage triagers
- Config AOR
Please mark this as draft unless there's intention to merge this.
Click the "Merge When Ready" if you're happy for this to automatically get merged once reviewed.
- If the option isn't available to you; ensure you've signed into DuckDuckGo oauth.
Also don't forget to add schema changes to validate if you're adding/changing a feature.

• Config Reviewer Documentation
• Config Maintainer Documentation
• Feature Implementer Documentation

[github-actions]

Generated file outputs:

Time updated: Wed, 05 Feb 2025 19:41:04 GMT

legacy

trackers-unprotected-temporary.txt

⚠️ File is identical

v3/android-config.json (13 more)

• v3/android-config.json
• v3/extension-brave-config.json
• v3/extension-bravemv3-config.json
• v3/extension-chrome-config.json
• v3/extension-chromemv3-config.json
• v3/extension-config.json
• v3/extension-edg-config.json
• v3/extension-edge-config.json
• v3/extension-edgmv3-config.json
• v3/extension-firefox-config.json
• v3/extension-safarimv3-config.json
• v3/ios-config.json
• v3/macos-config.json
• v3/windows-config.json

--- v3/windows-config.json
+++ v3/windows-config.json
@@ -6371,8 +6371,12 @@
         "history": {
             "state": "disabled",
             "exceptions": []
         },
+        "htmlHistoryPage": {
+            "state": "disabled",
+            "exceptions": []
+        },
         "htmlNewTabPage": {
             "state": "disabled",
             "exceptions": [],
             "features": {

latest

v4/android-config.json (13 more)

• v4/android-config.json
• v4/extension-brave-config.json
• v4/extension-bravemv3-config.json
• v4/extension-chrome-config.json
• v4/extension-chromemv3-config.json
• v4/extension-config.json
• v4/extension-edg-config.json
• v4/extension-edge-config.json
• v4/extension-edgmv3-config.json
• v4/extension-firefox-config.json
• v4/extension-safarimv3-config.json
• v4/ios-config.json
• v4/macos-config.json
• v4/windows-config.json

--- v4/windows-config.json
+++ v4/windows-config.json
@@ -5885,8 +5885,12 @@
         "history": {
             "state": "disabled",
             "exceptions": []
         },
+        "htmlHistoryPage": {
+            "state": "disabled",
+            "exceptions": []
+        },
         "htmlNewTabPage": {
             "state": "disabled",
             "exceptions": [],
             "features": {

[greyivy]

How does this sound to you @ayoy ?

[ayoy]

LGTM @greyivy! I was considering dropping the html prefix because there's no other history page anywhere yet, but it doesn't hurt to be specific :)