Skip to content

chore: Sync the vendored UI with upstream antora-ui-default, part 1: clean ports - #906

Draft
lfrancke wants to merge 64 commits into
mainfrom
phase3/clean-ports
Draft

chore: Sync the vendored UI with upstream antora-ui-default, part 1: clean ports#906
lfrancke wants to merge 64 commits into
mainfrom
phase3/clean-ports

Conversation

@lfrancke

@lfrancke lfrancke commented Jul 29, 2026

Copy link
Copy Markdown
Member

We based our UI on the Antora default UI but have not caught up with fixes that have landed there for four or so years 🥳

So, this is PR basically takes a lot of the missing commits (some come later in separate PRs due to conflicts etc.) and integrates them here.

Most of these are just "fixes" for stuff we don't see, but there are a few things that are user-visible here:

  1. Smooth scrolling: Clicking an entry in the right-hand "on this page" TOC or any in-page anchor link now animates to the target instead of jumping (loading a URL with a #fragment still positions instantly).
  2. Copy-to-clipboard: The "copied" toast fades faster, and stacking fixes mean the copy button/toast can no longer be overlapped by other elements on code blocks.
  3. Description-list spacing: the margin around descriptions is slightly tidier.
  4. tab-size: 4 code samples containing literal tab characters render 4 wide instead of 8, not sure if we have this anywhere

We skipped a few upstream commits which are relevant only for other fonts or styles where we diverged on purpose.

* float-group establishes a block formatting context (without affecting margin collapsing)
* float-gap adds side and bottom margin to a floating element
mojavelinux and others added 25 commits July 29, 2026 10:39
…oth scroll

Manual port of upstream antora-ui-default commit aac2ae9 (the patch does not
apply verbatim because our load handler signature drifted). Belongs with
f51a4e0 (enable smooth scroll by default), which this batch also ports:
without it, the on-load fragment jump animates from the top of every page.
@netlify

netlify Bot commented Jul 29, 2026

Copy link
Copy Markdown

Deploy Preview for stackable-docs ready!

Name Link
🔨 Latest commit d1de84e
🔍 Latest deploy log https://app.netlify.com/projects/stackable-docs/deploys/6a69c80d22b0c00008ca80fc
😎 Deploy Preview https://deploy-preview-906--stackable-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@stackable-cla

stackable-cla Bot commented Jul 29, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 3 committers have signed the CLA.

❌ nintendoeats
❌ mojavelinux
❌ Nadreck
You have signed the CLA already but the status is still pending? Let us recheck it.

Upstream's breadcrumb-truncation script arrived as 07-breadcrumbs.js; our
search script already used the 07- prefix. The bundle concatenates the
numbered scripts in sorted order and the two are independent, so this only
restores the one-number-one-script convention.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lfrancke
lfrancke force-pushed the phase3/clean-ports branch from 2c4cea5 to 12a5ec0 Compare July 29, 2026 08:47
…e CLA

The vendored UI is a fork of the MPL-2.0-licensed Antora Default UI and
periodically ports upstream commits with their authorship preserved. Those
authors have not signed the Stackable CLA; their code is included under the
MPL-2.0 alone. Document this in ui/NOTICE and ui/README.adoc so provenance
is clear for anyone doing due diligence, and note that the CLA check on
port PRs (like this one) fails by design and needs an admin override.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants