Support ShadowDOM

Open
#744 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
web-dev

Research direction

No source file, test, or entry point is named. Start by reproducing the example at https://gemjs.org/en/guide/ and inspecting how Readability receives and traverses its document; done should mean content rendered through declarative ShadowDOM is included in the extracted result.

Written by the indexing model from the issue text.

Description

has-website-testcase reader-mode-has-issues should-be-readerable

Some sites use ShadowDOM to render content:

e.g: https://gemjs.org/en/guide/

Note: ShadowDOM can be represented using declarative

Dominant language
JavaScript
Stars
11.5k
Forks
732
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/readability

All issues in mozilla/readability

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.