LivelyKernel / LivelyKernel/lively.next
Firefox Support
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
We currently recommend for lively.next to be used in Chromium based browser.
For, partially ideological, reasons, I think we should:
- [ ] investigate the current state of lively in Firefox
- [ ] try to fix major bottlenecks if any
- [ ] "officially" recommend firefox as well
It might make sense to begin a list in the wiki which lists known browser specific issues (like the cursor chrome bug).
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 investigating lively.next in Firefox and compare its behavior with the currently recommended Chromium-based browsers. Identify any major bottlenecks and browser-specific issues, then document known issues in the wiki. Done means major problems are addressed where practical and Firefox can be officially recommended if the investigation supports it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100