iodide-project / iodide-project/iodide
should user-specified reps use the Chrome custom object formatter protocol?
Open
client UX
output reps
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
in particular, the use of a restricted subset of html tags seems quite sensible. it also feels sensible to take cues from chrome's devtools team in general -- learn from the people who have thought about a problem most, ya know?
https://docs.google.com/document/d/1FTascZXT9cxfetuPRT2eXPQKXui4nWFivUnS_335T3U/edit
https://medium.com/@tomsu/devtools-tips-day-10-custom-formatters-58ee46e640f9
Contributor guide
Research direction
Start by reviewing the linked Google Doc and Medium article about Chrome custom formatters. The issue names no file or test entry point; work is complete only after the protocol choice and required scope for user-specified reps are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100