eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
Chrome and Firefox debugger seem to be non-functional with Flatpak
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Chrome and Firefox debugger seem to be non-functional with Flatpak
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
The report names Chrome, Firefox, and Flatpak but provides no files, tests, or entry points. Start by reproducing debugger behavior for both browsers in a Flatpak environment and trace the Eclipse debugger integration. Done means identifying the cause and confirming that debugging works for Chrome and Firefox with Flatpak.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100