@duckduckgo/autoconsent 16.42.0 → 16.43.0

package/dist/types/eval-snippets.d.ts

@@ -60,6 +60,7 @@ export declare const snippets: {
     EVAL_SHOPIFY_TEST: () => boolean;
     EVAL_SKYSCANNER_TEST: () => boolean | null;
     EVAL_SIRDATA_UNBLOCK_SCROLL: () => boolean;
+    EVAL_SOURCEPOINT_RESTORE_SCROLL: () => boolean;
     EVAL_STEAMPOWERED_0: () => boolean;
     EVAL_TAKEALOT_0: () => boolean;
     EVAL_TARTEAUCITRON_0: () => any;

package/lib/eval-snippets.ts

@@ -207,6 +207,26 @@ export const snippets = {
         });
         return true;
     },
+    EVAL_SOURCEPOINT_RESTORE_SCROLL: () => {
+        // Sourcepoint scrolls back to this saved position when it unlocks; we unlock instead, so restore and clear it
+        const root = document.documentElement;
+        const saved = root.dataset.previousScrollY;
+        if (saved && saved !== 'null') {
+            root.dataset.previousScrollY = 'null';
+            const y = -parseInt(saved, 10);
+            if (y > 0 && window.scrollY === 0) {
+                const behavior = root.style.scrollBehavior;
+                root.style.scrollBehavior = 'auto';
+                window.scrollTo(0, y);
+                root.style.scrollBehavior = behavior;
+            }
+        }
+        // Sourcepoint re-locks after a bfcache restore, which autoconsent does not re-run for
+        window.addEventListener('pagehide', () => {
+            if (root.dataset.previousScrollY) root.dataset.previousScrollY = 'null';
+        });
+        return true;
+    },
     EVAL_STEAMPOWERED_0: () =>
         JSON.parse(
             decodeURIComponent(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@duckduckgo/autoconsent",
-  "version": "16.42.0",
+  "version": "16.43.0",
   "description": "",
   "types": "./dist/types/web.d.ts",
   "exports": {

package/readme.md

@@ -83,6 +83,16 @@ There are currently two ways of implementing a CMP:
 
 For more details on rule types, see [Rule Syntax Reference](docs/rule-syntax.md).
 
+## AI agent setup
+
+The agent skills in `.agents/skills/` need a few environment variables.
+
+1. Copy the contents from [`.claude/user-settings.json.TEMPLATE`](.claude/user-settings.json.TEMPLATE) to your user settings (e.g. `~/.claude/settings.json`), in addition to your existing config. If your settings already have an `env` block, merge the entries into it: a second `env` key would silently override the first.
+2. Replace the values in the template. Proxy values must be complete URLs with an `http://`, `https://`, or `socks5://` scheme, and without embedded credentials. `REGIONAL_PROXY_USERNAME` and `REGIONAL_PROXY_PASSWORD` are optional: they are only used for `https://` proxies, so remove them if your proxies don't need authentication.
+3. Start a new Claude Code session: settings are only read at startup.
+
+For other agents or plain shell use, `export` the same variables in your shell profile instead.
+
 ## License
 
 MPLv2.

package/rules/autoconsent/sourcepoint-top.json

@@ -1,7 +1,7 @@
 {
     "name": "sourcepoint-top",
     "vendorUrl": "https://www.sourcepoint.com/",
-    "comment": "Top-frame companion to Sourcepoint-frame. The message UI lives in a cross-origin iframe, so the top frame cannot tell an ordinary notice from a 'consent or pay' wall that Sourcepoint-frame has to bail on; hide it either way and undo the scroll lock. Hiding uses visibility rather than display so the iframe keeps its layout and the frame rule can still complete a real rejection underneath, with z-index and pointer-events mirroring the built-in hide step. The scroll lock is undone twice over: removeClass restores each site's own layout in the normal case, and the stylesheet neutralises the lock declarations if Sourcepoint re-adds the class later (it does so on pageshow after a back/forward restore, which autoconsent does not re-run for).",
+    "comment": "Top-frame companion to Sourcepoint-frame. The message UI lives in a cross-origin iframe, so the top frame cannot tell an ordinary notice from a 'consent or pay' wall that Sourcepoint-frame has to bail on; hide it either way and undo the scroll lock. Hiding uses visibility rather than display so the iframe keeps its layout and the frame rule can still complete a real rejection underneath, with z-index and pointer-events mirroring the built-in hide step. The scroll lock is undone twice over: removeClass restores each site's own layout in the normal case, and the stylesheet neutralises the lock declarations if Sourcepoint re-adds the class later (it does so on pageshow after a back/forward restore, which autoconsent does not re-run for). Sourcepoint also saves the scroll position before locking and scrolls back to it when it unlocks: the eval step restores that position (the lock can clamp it to the top when a back navigation reloads the page) and clears it, so Sourcepoint does not later scroll to a stale value such as the top after a back/forward restore.",
     "minimumRuleStepVersion": 3,
     "runContext": {
         "main": true,
@@ -20,6 +20,7 @@
             "stylesheet": "html.sp-message-open { height: auto !important; width: auto !important; } html.sp-message-open body { position: relative !important; overflow: auto !important; margin-top: 0 !important; top: auto !important; left: auto !important; right: auto !important; }",
             "stylesheetId": "sourcepoint-top-scroll-unlock"
         },
-        { "removeClass": "sp-message-open", "selector": "html", "optional": true }
+        { "removeClass": "sp-message-open", "selector": "html", "optional": true },
+        { "eval": "EVAL_SOURCEPOINT_RESTORE_SCROLL", "optional": true }
     ]
 }