fix: docs sidebar header, background color issue

[nishu-murmu]

Overview

Added a class in custom.css for sidebar header

Manual Testing

1. run locally bun docs:dev.
2. Check for this path http://localhost:5173/guide/resources/how-wxt-works.html

Related Issue

This PR closes #2503

[netlify]

✅ Deploy Preview for creative-fairy-df92c4 ready!

Name	Link
🔨 Latest commit	aa832f3
🔍 Latest deploy log	https://app.netlify.com/projects/creative-fairy-df92c4/deploys/6a65bb21a32b350008498044
😎 Deploy Preview	https://deploy-preview-2504--creative-fairy-df92c4.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pkg-pr-new]

Open in StackBlitz

@wxt-dev/analytics

npm i https://pkg.pr.new/@wxt-dev/analytics@2504

@wxt-dev/auto-icons

npm i https://pkg.pr.new/@wxt-dev/auto-icons@2504

@wxt-dev/browser

npm i https://pkg.pr.new/@wxt-dev/browser@2504

@wxt-dev/i18n

npm i https://pkg.pr.new/@wxt-dev/i18n@2504

@wxt-dev/is-background

npm i https://pkg.pr.new/@wxt-dev/is-background@2504

@wxt-dev/module-react

npm i https://pkg.pr.new/@wxt-dev/module-react@2504

@wxt-dev/module-solid

npm i https://pkg.pr.new/@wxt-dev/module-solid@2504

@wxt-dev/module-svelte

npm i https://pkg.pr.new/@wxt-dev/module-svelte@2504

@wxt-dev/module-vue

npm i https://pkg.pr.new/@wxt-dev/module-vue@2504

@wxt-dev/runner

npm i https://pkg.pr.new/@wxt-dev/runner@2504

@wxt-dev/storage

npm i https://pkg.pr.new/@wxt-dev/storage@2504

@wxt-dev/unocss

npm i https://pkg.pr.new/@wxt-dev/unocss@2504

@wxt-dev/webextension-polyfill

npm i https://pkg.pr.new/@wxt-dev/webextension-polyfill@2504

wxt

npm i https://pkg.pr.new/wxt@2504

commit: aa832f3

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.35%. Comparing base (5bd36e9) to head (aa832f3).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2504      +/-   ##
==========================================
- Coverage   79.40%   79.35%   -0.05%     
==========================================
  Files         134      134              
  Lines        4005     4005              
  Branches      910      910              
==========================================
- Hits         3180     3178       -2     
- Misses        735      736       +1     
- Partials       90       91       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[PatrykKuniczak]

What?

It doesn't solve #2503 and why this background?
It doesn't look good

[nishu-murmu]

What?

It doesn't solve #2503 and why this background? It doesn't look good

My bad, I only checked in Guides page.

[nishu-murmu]

@PatrykKuniczak Now can you check, a prefix class was missing, now it only applies to that particular part.

[PatrykKuniczak]

@nishu-murmu

Background changed there also.

But why are you changing background to fix #2503 ??

[nishu-murmu]

@PatrykKuniczak applying z-index isn't causing anything.
Do you propose anything else?

I've added more specific header class for that.
Now it will only reflect in sidebar header.

Selection_009.bmp

[PatrykKuniczak]

@nishu-murmu There's no bug for me, at all, i don't know what are you're trying to fix guys.

[nishu-murmu]

@PatrykKuniczak The text is overlapping.
Selection_010.bmp

[PatrykKuniczak]

@nishu-murmu I can't see your .bmp files, let's attach it directly there in other format.

[nishu-murmu]

@PatrykKuniczak I'm talking about the sidebar header, when you scroll the sidebar, those texts gets overlapped.

[PatrykKuniczak]

@nishu-murmu Ok, now i see.

But still there's a problem:

(You can see it on smaller window)

There shouldn't be dark bg, it should be only on sidebar.

[nishu-murmu]

@PatrykKuniczak which page?, can you please provide entire page screenshot?

[PatrykKuniczak]

@PatrykKuniczak which page?, can you please provide entire page screenshot?

https://deploy-preview-2504--creative-fairy-df92c4.netlify.app/guide/installation.html

[nishu-murmu]

@PatrykKuniczak
Fixed the appropriate z-index.

I was looking completely else where for the fix 😅 .

[PatrykKuniczak]

Now LGTM 😄

[github-actions]

Thanks for helping make WXT better!

[PatrykKuniczak]

Thanks for helping make WXT better!

@nishu-murmu If you won't have that messages in next PRs, you can add yourself there:

wxt/.github/workflows/pr-closed.yml

Lines 25 to 32 in eb93fa4

	- name: Post Thank You Comment
	if: >-
	github.event.pull_request.user.login != 'aklinker1' &&
	github.event.pull_request.user.login != 'Timeraa' &&
	github.event.pull_request.user.login != 'PatrykKuniczak' &&
	github.event.pull_request.user.login != 'dependabot[bot]' &&
	github.event.pull_request.user.login != 'copilot-swe-agent[bot]'
	uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0

[nishu-murmu]

@PatrykKuniczak cool, thanks for letting me know.

[aklinker1]

This should be docs: not fix:, this doesn't fix a bug in a package's production code.

Also, this isn't a bug in vitepress by default, we introduced it in some custom style. That means the solution should have been to remove the style causing the issue, not add another one. At least, that was my initial thought, I didn't investigate and could be wrong.

Neither of these is a big deal, just an FYI for the future.

[nishu-murmu]

@aklinker1 Thanks for pointing it out! Will make sure of that next time.

[PatrykKuniczak]

@aklinker1 OOO yeah

This should be docs: not fix:, this doesn't fix a bug in a package's production code.

My fault, i've seen that in the start and i've plan to change it.
But i've missed it after a couple of reviews.

[PatrykKuniczak]

@aklinker1 If we'll change title now, on release this PR goes into "dosc" section, or it's basing on merge commits?