Long labels in the docs left navigation now stay on one line and end in an ellipsis. Before, a word too wide for the sidebar, such as "Customizing/Extending", was clipped at the edge with no sign that text was missing. This matches the ellipsis already applied to the "In this document" panel.
The change is CSS only for the layout, so the full label stays in the HTML. A title attribute shows the full label on hover, both for items rendered by TreeTagHelper and for items that index.js adds when a lazy group is expanded. The title value is HTML-encoded so quotes in a
label cannot break the attribute.
Items without a link or sub-items are not changed and still wrap.
- Move `Volo.Abp.Account.Web.Tests` to net11.0 and reference EF Core Design next to EF Core Tools
- Run the Npgsql provider test again and note the MySQL and Oracle providers in the migration guide
- Restore the CRLF line endings of the edited csproj and App.razor files
The first truncation attempt did nothing because Bootstrap's wrapping
`.nav` made each TOC row as wide as its longest heading, so the text was
clipped with no ellipsis. Adding `flex-wrap: nowrap` to the TOC lists
fixes it. Temporary before/after screenshots are added under
.volobox-screenshots/task-1803 for review and should be removed before
merging.
Co-authored-by: Volobox Agent <agent@volobox.local>
Long table-of-contents headings in the docs right panel now stay on one
line and end in an ellipsis instead of wrapping or scrolling sideways.
The change is CSS only, so the full heading stays in the HTML for search
engines, and a title attribute shows it on hover.
Co-authored-by: Volobox Agent <agent@volobox.local>
- Parse the HTML with HtmlAgilityPack and convert GIF, WebP and unsupported JPEG images with SkiaSharp
- Keep same-page and wrapped links clickable, and load only HTTP(S) images
- Replace tabs in code blocks and document the Linux and font resolver limits
- Render PDF files with HtmlRenderer.PdfSharp instead of the AGPL licensed iText
- Use Elastic.Clients.Elasticsearch instead of the deprecated NEST client
VoloDocs only registered "pt-BR" as a supported culture in
VoloDocsWebModule, even though a "pt" localization resource file
(Localization/Resources/VoloDocs/Web/pt.json) already exists.
Any Docs project configured with a "pt" language (via its
docs-langs.json) triggers an infinite redirect loop between the
project page and /Abp/Languages/Switch, because the app never
recognizes "pt" as a valid culture and silently falls back to the
default one on every request.
- Add NavigationManager.ResolveBrandingUrl and ResolveBrandingCssUrl
- Move the url rules to Volo.Abp.Ui.Branding.BrandingUrlHelper, shared with the mvc themes
Revise translation file to match commercial modules
Adjusted keys and wording in the Account module translations so
they are consistent with the commercial module equivalents.
- Post the changed permission names from the MVC modal instead of the whole tree
- Replace the per-name list scans with dictionary lookups on the read path
- Honor DisableTracking in the permission, identity, OpenIddict and IdentityServer repositories
- Skip the feature value update when the stored value is unchanged
- One namespace no longer spans two assemblies now that they live in the domain layer
- The Data Protection purpose keeps its old string, so outstanding 2FA codes stay valid