Autowebcompat repro agent judging by the comments whether it's a webcompat issue and doesn't attempt to reproduce
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
For a run 7027a303-24f6-4dce-9634-3f1ced884e0c and bug 2010861:
[agent] Not a webcompat issue.
The report describes broken CSS on www.altitudeplus.com in Firefox on Linux. However, the follow-up investigation in the comments establishes that the breakage only reproduces when the third-party Stylus extension is installed and injecting styles into the page (even empty rules like
foo{}). The triage team could not reproduce it in a standard Firefox configuration. Because the issue depends on a non-default browser modification rather than default Firefox behavior, it would not affect normal Firefox users accessing the site, so it does not meet the webcompat criteria.
This likely is not an issue for new bugs, but more so for backlog runs for bugs that have comments already.
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 with the handling for backlog runs in the autowebcompat reproduction agent, using run 7027a303-24f6-4dce-9634-3f1ced884e0c and Bug 2010861 as examples. Trace how existing comments lead to the webcompat judgment, then verify that backlog runs with comments still attempt reproduction before deciding; done means the agent no longer relies on comments alone in this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100