fix: detect LinkedIn 2026 feed DOM promoted posts (v1.3.5)#2
Merged
Conversation
Second uninstall feedback reported promoted posts not hidden. Root cause: LinkedIn's 2026 feed rewrite (main-feed-card articles, actor line in p[componentkey]) was invisible to the v1.3.4 detector, which skipped all <p> content as body copy and only covered ~15 of 28 locales. - new-DOM containers: article[data-id='main-feed-card'], li.feed-item - structural sponsored markers: data-sponsored-tracking-url, data-view-tracking-scope (quoted-token, root-only), promoted URNs - strict-equality matching for <p> metadata texts; loose word-boundary matching stays limited to the shipped v1.3.4 keyword list - promoted/suggested keywords expanded to ~40 languages; token matching inside LinkedIn-generated sub-description lines covers 2-char CJK - NFKC + zero-width stripping before comparison - hiding via injected CSS rule on marker attribute (survives re-renders) plus static pre-hide rules on LinkedIn's own sponsored attrs (no flash) - leading+trailing 250ms throttle replaces starvable resetting debounce - poll filter uses structural selectors, not innerHTML text scan - label collection excludes elements containing body copy (fixes organic posts mentioning 'sponsored' being hidden in div containers) Council-reviewed (Consilium 20260612T092359). Tests 33/33, typecheck, build, zip OK (manifest 1.3.5). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
📝 WalkthroughSummary by CodeRabbit
WalkthroughExtension version 1.3.5 promotes promoted-post hotfix improvements. The detector gains expanded DOM selectors, stronger text normalization, and multi-tier keyword matching. The content script switches to stylesheet-based element hiding with refined mutation scheduling and selective observer filtering. ChangesLinkedIn Feed Filter Enhancement v1.3.5
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
2gelbuy
added a commit
that referenced
this pull request
Jun 12, 2026
docs: AI_STATUS — v1.3.5 landed via PR #2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Second uninstall feedback (2026-06-12): promoted posts not hidden. LinkedIn's 2026 feed rewrite (
article[data-id="main-feed-card"], actor line inp[componentkey]) was invisible to the v1.3.4 detector — it skipped all<p>content as body copy and covered only ~15 of 28 locales.What
main-feed-card,li.feed-item) + LinkedIn's own structural sponsored markers (data-sponsored-tracking-url, quoted-token root-onlydata-view-tracking-scope)<p>metadata; loose word-boundary matching stays limited to the shipped v1.3.4 keyword list (avoids hiding organic posts with promoted-like headlines)Verification
npm test33/33,npm run typecheck,npm run build,npm run zip(manifest 1.3.5)PENDING_REVIEW1.3.5, AMO published (0 errors), Edge submitted🤖 Generated with Claude Code