[BUG FIX] The scanning progress overlay is fixed to be static

[Annunitha]

Before

As seen above, the progress overlay lays on top of the page footer when the user scrolls down.

After

The bug has been fixed to make sure the div stays static and does not move with scrolling.

File changed: ScanProgressPage.scss

Fixes issue: #168

[sapnilbiswas]

Thanks @Annunitha the fix looks good already. But can you try and make the scanning div as overlay along with the footer being blurred while it's scrolled?

[Annunitha]

@sapnilbiswas Alright, I'll do that. I'll keep you updated!

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ec9e4b7f-98b2-448b-8f2b-5aee8cbdcd8d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sapnilbiswas]

@Annunitha any updates?

[Stanzin7]

Thanks @Annunitha for tackling #168. The core intent is only addressed by one line here (ScanProgressPage.scss:15, position: fixed → relative), and even that leaves a now-dead inset: 0; the other ~9 edits change unrelated layout and risk regressions. More importantly, #168 itself is superseded — starting a scan now navigates to a dedicated /scan/progress/:scanId route (ScanContext.jsx:197,245) instead of overlaying the homepage, so the original overlay bug no longer exists. Recommending we close both this PR and #168.