Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Style problem in docs with banners

Open
#480 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start at the banners documentation page and reproduce both issues using the listed checkbox, hover, and navigation steps. Inspect the banner example and its behavior across documentation-page navigation; done means the close icon remains distinguishable on hover and no empty space remains after leaving a pinned banner.

Written by the indexing model from the issue text.

Description

bug docs

Actually there are 2 bugs:

  1. When hovering on close button in the example of important banner, the cross icon stays white and becomes undistinguished from hovered background
  2. Navigating to another page with opened Pinned banner leaves empty space

Steps to reproduce the behaviour:

  1. Go to banners doc page
  2. Scroll down to the end
  3. Select checkboxes "Important?" and "Pinned?"
  4. Click on "Show example"
  5. Hover over close button of the banner
  6. See error of white icon on white background
  7. Navigate from left sidebar to another page of the docs
  8. Scroll down a bit
  9. See error of blank space left behind the banner

Expected behavior
I'd expect to not have this bugs:)

Screenshots
1.
image
2.
image

Desktop (please complete the following information):

  • OS: macOS
  • Browser chrome
  • Version 81
Dominant language
TypeScript
Stars
672
Forks
107
Avg merge
2d 12h
Merged PRs (30d)
26

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StackExchange/Stacks

All issues in StackExchange/Stacks

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.