lirios / lirios/browser

Developer tools

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

Nobody has claimed this yet.

enhancement
Dominant language
QML
Stars
219
Forks
32
PR merge metrics
No merged PRs in 30d

Description

* [x] Source code view
* [ ] Web inspector

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.

Research direction

The issue provides only a checklist: Source code view is complete and Web inspector remains. No files, tests, or entry points are named, so first locate the existing source-code-view work and the browser's developer-tools entry point. Done would require a defined Web inspector scope and a way to verify it, neither of which the issue specifies.

Written by the indexing model from the issue text.

Assessment

Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.