Add print styles for payload and docs pages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css
- Domain
- frontend
Research direction
Start in globals.css and identify the selectors used by the header, sidebars, navigation, article, and code blocks. Emulate print media or open print preview on the SQL injection payload page to check the current layout. Done means printing shows only the article with black text on white, visible link URLs, and code blocks kept together where possible.
Written by the indexing model from the issue text.
Description
Summary
There are no print styles. Printing or saving a payload page to PDF includes the site header, the full sidebar and the contents panel, so the article loses width and wastes pages.
Steps to reproduce
- Open
/OWASP-Hunting/payloads/sql-injection/. - Emulate print media (DevTools, Rendering, Emulate CSS media type: print) or use Print preview.
Expected
Only the article is printed: no header, sidebar or contents panel, black text on white, and link URLs shown.
Actual
The layout is identical to the screen layout, with the header, sidebar and contents panel.
Suggested fix
Add an @media print block in globals.css that hides header, sidebars and navigation, resets colours, removes the max-width, and avoids page breaks inside code blocks.
Environment
website branch, Chromium print emulation.
- Dominant language
- Python
- Stars
- 22
- Forks
- 14
- Avg merge
- 14h 14m
- Merged PRs (30d)
- 29
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from OWASP/OWASP-Hunting
-
enhancement Website
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OWASP/OWASP-Hunting#96 ·
Maintainers usually reply within 1 day
-
enhancement Website
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OWASP/OWASP-Hunting#92 ·
Maintainers usually reply within 1 day
-
bug Website
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OWASP/OWASP-Hunting#91 ·
Maintainers usually reply within 1 day
-
bug Website
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
OWASP/OWASP-Hunting#90 ·
Maintainers usually reply within 1 day
-
bug Website
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OWASP/OWASP-Hunting#89 ·
Maintainers usually reply within 1 day
All issues in OWASP/OWASP-Hunting
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
FinanceFlash/unvibecode#699 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
micropython/micropython#19942 ·
Maintainers usually reply within 1 day
-
A rebuild posts "not part of this build" success to the commit's failed `nix-build` gate and effectsPossibly taken @Padraic-O-Mhuiris claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
`epoch.Integer` raises a raw OverflowError for integers too large to convert to a floatPossibly taken @arindam77 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-extra-types#479 ·
Maintainers usually reply within 1 day
-
Make the Elasticsearch request timeout of the API configurablePossibly taken @SaitejaKommi claimed this today. OpenAPI backend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openfoodfacts/search-a-licious#601 ·
Maintainers usually reply within 2 days