fix: blazor <AbpStyles>/<AbpScripts> lose PathBase for WebAssembly files#25340
Merged
fix: blazor <AbpStyles>/<AbpScripts> lose PathBase for WebAssembly files#25340
<AbpStyles>/<AbpScripts> lose PathBase for WebAssembly files#25340Conversation
…mblyStyleFiles`/`WebAssemblyScriptFiles` Resolve `WebAssemblyStyleFiles` and `WebAssemblyScriptFiles` through `IComponentBundleUrlBuilder` so they receive the same `PathBase` prefixing as the prerender bundle files.
Contributor
There was a problem hiding this comment.
Pull request overview
Follow-up to #25336 to ensure Blazor <AbpStyles> / <AbpScripts> also preserve PathBase when switching/appending WebAssembly-specific files, by routing WebAssemblyStyleFiles / WebAssemblyScriptFiles through IComponentBundleUrlBuilder like prerender bundle files.
Changes:
- Resolve
WebAssemblyStyleFilesviaResolveAsync(...)when appending to prerendered styles. - Resolve
WebAssemblyStyleFilesviaResolveAsync(...)when switching to WebAssembly styles after render. - Resolve
WebAssemblyScriptFilesviaResolveAsync(...)when running in the browser.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| framework/src/Volo.Abp.AspNetCore.Components.Web.Theming/Bundling/AbpStyles.razor | Routes WebAssembly style file URLs through IComponentBundleUrlBuilder so leading-/ paths don’t drop PathBase. |
| framework/src/Volo.Abp.AspNetCore.Components.Web.Theming/Bundling/AbpScripts.razor | Routes WebAssembly script file URLs through IComponentBundleUrlBuilder for the same PathBase correctness. |
EngincanV
approved these changes
Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #25336.
WebAssemblyStyleFiles/WebAssemblyScriptFiles(the WebAssembly switch / append branches) skippedIComponentBundleUrlBuilder, so leading-/URLs were rendered as-is and dropped thePathBaseunder a virtual application. Resolve them through the builder, same as the prerender bundle files.