refactor(PdfReader): add z-index value

[ArgoZhang]

Link issues

fixes #824

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Enhancements:

• Set an explicit z-index on the PdfReader view progress bar to improve its visual stacking order relative to other UI elements.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a z-index to the PDF reader's top progress bar to ensure it renders above overlapping content; no functional changes are made to the project file.

File-Level Changes

Change	Details	Files
Ensure the PDF reader's top progress bar visually overlays other content by adjusting its stacking order.	Set a z-index value on the top progress bar element to control stacking context when overlapping other UI elements Retain existing positioning and sizing styles for the progress bar without modification	src/components/BootstrapBlazor.PdfReader/wwwroot/css/pdf_reader.css

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#824	Add a z-index value to the relevant PdfReader component styles to resolve layering/stacking issues.	✅

Possibly linked issues

• refactor(PdfReader): add z-index value #824: PR updates PdfReader CSS to add the requested z-index, directly implementing issue refactor(PdfReader): add z-index value #824’s refactor.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Consider documenting why z-index: 10 was chosen or aligning it with any existing z-index scale/tokens in the project to avoid future stacking conflicts.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider documenting why `z-index: 10` was chosen or aligning it with any existing z-index scale/tokens in the project to avoid future stacking conflicts.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This PR fixes a z-index layering issue in the PdfReader component by ensuring the progress bar appears above other UI elements. The change addresses issue #824 with a simple CSS addition and corresponding version bump.

Key Changes:

• Added z-index: 10 to the .bb-view-progress CSS class to fix layering issues
• Bumped component version from 10.0.16 to 10.0.17

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/components/BootstrapBlazor.PdfReader/wwwroot/css/pdf_reader.css	Added z-index property to progress bar to ensure it displays above other content
src/components/BootstrapBlazor.PdfReader/BootstrapBlazor.PdfReader.csproj	Incremented patch version to reflect the CSS fix

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.