Separate static and dynamic parts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
For example:
webidl-clipboard.js has a part that can be static (adding clipboard copy buttons) and a dynamic UI part (adding event listeners to those added buttons). Currently respec2html removes any dynamic UI features and this causes weird situation that users cannot use the feature in respec2html-generated page.
We may separate those two parts so that we can ultimately:
- serve static parts as respec2html already does
- serve dynamic UI parts as separate modules
- avoid removeOnSave
What do you think?
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 webidl-clipboard.js and the respec2html handling described in the issue, including removeOnSave. Trace how static clipboard buttons and dynamic event listeners are currently processed. Done means the static and dynamic parts can be served separately while preserving the feature and avoiding removeOnSave.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100