Some buttons don't get detected, option to add custom XPath rules?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Some desired buttons aren't detected and they might be special case for each user in here. For example, in programming competition sites, the "copy" input button of neither CodeForces nor AtCoder gets recognized.
In case those sites are exceptions/badly coded/whatnot it would be nice if each user could add rules (xpath or else) to what he/she wants to be considered a button.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing button detection on the CodeForces and AtCoder URLs linked in the issue, focusing on their copy input buttons. Define how users would supply custom XPath or other rules and how those rules interact with normal detection; the work is done when the specified buttons are recognized through a documented per-user rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100