Conversation
Use title and description from the rendered watch page only when its video ID matches the requested URL. Prevent the generic metadata fallback from restoring rejected values, while retaining existing fallback behavior for other extractors.
This branch has not been deployed
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.
After navigating from video A to video B in the same YouTube tab, clipping can combine B's content with A's title and description. YouTube can retain A's Open Graph tags and structured data; when the extractor rejects those values, the generic metadata fallback restores them.
This adds a fallback to the rendered watch title and description, scoped to a
ytd-watch-flexywhosevideo-idmatches the requested URL. It uses the expanded description when available, otherwise the rendered snippet. An explicit extractor opt-in prevents empty title/description values from falling back to rejected metadata; other extractors keep their existing behavior.Follow-up to #174 and #198. Related: obsidianmd/obsidian-clipper#735. Clipper's bug-report guidance directs incorrect-content issues to Defuddle.
Validation:
npm test: 585 passed.npm run test:jsdom: 585 passed.npm run build,npm run size, andnpm run lint:innerhtml: passed.