Custom CSS is not last in order
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Description of problem
We are using ReSpec for a non-W3C guidelines document. Including a custom CSS as instructed in the ReSpec docs is working, however it seems the custom style sheet is not last in order when ReSpec populates the rest of the HTML page. This prevents custom rules to override the default styles in many cases.
What happened (e.g., it crashed)?:
Some ReSpec styles are processed after the custom CSS, so default styles takes precedence over custom styles.
Expected behavior (e.g., it shouldn't crash):
Custom CSS rules should take precedence over default styles.
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 reproducing the issue using the custom-styles instructions in the linked ReSpec documentation, then inspect the generated HTML and stylesheet insertion order. Confirm the fix by ensuring the custom stylesheet is processed after ReSpec's default styles so its rules take precedence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- documentation, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100