Skip to content

Release 1.1.0: consumer scripts and mobile export improvements - #16

Merged
cudoment merged 13 commits into
mainfrom
release/1.1.0
Nov 13, 2026
Merged

cudoment merged 13 commits into
mainfrom
release/1.1.0

Conversation

@cudoment

Copy link
Copy Markdown
Owner

Release 1.1.0 adds consumer scripts and configurable request destinations to HTML export, improves mobile navigation and scrolling, and introduces an achromatic export palette with underlined prose links.

Single-page exports preserve JavaScript source in deferred data URLs. Browser regressions cover raw templates, regular expressions, HTML delimiters, global scope and execution order. Word output preserves marked code lines, and Docusaurus lockfiles use patched dependency releases. The reference, guides and export samples describe the resulting behavior in English and Korean.

Validation covers six example builds and both Next.js bundlers. Type checking, formatting and 2,766 strict tests pass. Packed consumers, guide consumers, rebuild freshness and export sample comparison also pass. Remaining upstream host advisories are recorded in examples/README.md.

At 768px or narrower the sidebar lifted its max-height but kept the base
rule's overflow-y: auto and overscroll-behavior: contain, so it stayed a
scroll box that could not scroll. A touch swipe that started on it moved
neither the sidebar nor the page, and a long navigation, shown above the
text in 1.0.0 and opened from the menu button since, left no place on
the screen to scroll from.

The narrow sidebar now has overflow: visible, so it is part of the
page. It also takes overflow-wrap: anywhere: nothing clips it any more,
and a group named by one long word would otherwise widen the page,
where the scroll box used to hide it as a sideways scroll. Wide screens
keep the sticky sidebar that scrolls inside itself.

A structure test checks the narrow rule, and a browser test opens the
menu at 390px, swipes on a long nested navigation and expects the page
to scroll without growing wider; it also checks at 1280px that the
sidebar stays sticky and takes the wheel. The release notes, the export
guide and the adapters reference describe the behaviour in English and
Korean. The export samples that carry the stylesheet are rebuilt; their
PDF and Word files differ only in timestamps and generated ids, so they
stay as committed.
The sticky sidebar and contents beside the text set
overscroll-behavior: contain, so a column with nothing left to scroll
took a wheel turn or a touch swipe that started on it and moved nothing.
With a three-page navigation the page stayed still under the wheel at
1280px and under a swipe at 900px, and a long column scrolled to its end
held the page the same way.

The base rule no longer contains their overscroll. A long column still
takes the gesture first and scrolls inside itself, and once it is at its
end the next turn scrolls the page. On a screen 768px wide or narrower
the open sidebar stays part of the page; its comment now says what that
rule still does, which is to let a long word wrap rather than hide
behind a sideways scroll.

The structure test checks that a table's sideways containment is the
only overscroll rule left. The browser test wheels over a short and a
long sidebar and contents at 1280px, swipes on a short sidebar at 900px,
and on a phone checks that the open sidebar scrolls nothing sideways.
The release notes and the adapters reference describe the behaviour in
English and Korean. The export samples that carry the stylesheet are
rebuilt; their PDF and Word files differ only in timestamps and
generated ids, so they stay as committed.
On a screen 768px wide or narrower the sidebar opened from a menu
button in the header and appeared in the page flow above the text. It
now opens as a panel fixed to the left edge, over the page, from a
floating button at the bottom right, so the navigation is in reach
wherever the reader has scrolled and a long navigation no longer
pushes the text down.

The button, a backdrop and a close line at the top of the panel are
labels for the existing hidden checkbox, so the default output stays
script-free. The checkbox moves between the header and the layout,
named with the button's word, so Tab goes on from it into the panel,
and the button or the close line shows its focus ring. It is written
autocomplete="off", so Back does not bring the panel back open over a
locked page. The open panel lies over the header and the review
runtime, scrolls inside itself with its overscroll contained, and keeps
a wheel or a swipe from scrolling the page behind where :has() is
supported. It slides in over --ease, which reduced motion shortens to
1ms. Print hides all of it and wider screens draw none of it. A new
UiStrings word, close, names the close line in English and Korean, and
on a hosted review the button stands left of the notes button.

Structure tests cover the markup and the rules. Browser tests open and
close the panel at 390px by touch, backdrop, close line, keyboard and
Back, check the scroll lock, reduced motion and print, check that 769px
and 1280px draw none of it, and place the button beside the notes
button. The release notes, the export guide and the adapters reference
describe the panel in English and Korean; the reference lists the hooks
a script of one's own can use, with an Escape handler as an example.
The export samples are rebuilt; their PDF and Word files differ only in
timestamps and generated ids, so they stay as committed.
… icon

The button shows the menu bars alone in a round 3rem button, its word kept in the page out of
sight, at the bottom left: on the side the panel opens from and clear of the review runtime's notes
button, so the rule that moved it aside in review pages goes.
The button shows the menu bars alone, so its name is now Menu (메뉴 in Korean), a new ui word a
locale can replace; the panel it opens keeps the documents word as its title.
connect lists Content-Security-Policy sources ('self', a secure origin, a loopback address) that
replace connect-src 'none' on every page loading the caller's scripts. It needs scripts, a review
page refuses it, and an entry with a quote, space, comma or semicolon is an error, so it cannot add
a directive; form-action 'none' stays.
A caller that adds its scripts to the pages after the build gets the policy from themeSwitch, and
needs connect there too; a page with neither option has no policy to widen.
Both READMEs open with seven badges above the language line: CI on main, the npm version, monthly
downloads, the Node.js range and the license of @cudoment/cudoc, and two fixed ones naming the five
hosts and the three export formats. The line holds links alone, so the page's description stays
the lead sentence.
The theme menu's summary showed the theme's word beside its sun or moon;
it now shows the icon alone and keeps the word as its accessible name.

On a narrow screen the sidebar opened only from the floating button at
the bottom left. The same bars now stand before the header's title as
another label for the checkbox, hidden from assistive technology since
the checkbox carries the name. The floating button stays.

The header's first child is now those bars on a site page with a
sidebar, so the showcase's brand mark selects the title directly, and
the release notes say so for any css file that used :first-child.
Use an achromatic export palette with underlined prose links and marked code lines in HTML, PDF and Word. Preserve standalone consumer script source and deferred execution order with embedded data URLs, backed by browser regressions. Update the English and Korean references, rebuild the export samples and refresh patched Docusaurus dependencies.
Dispatch touch start, move and end events after compositor frames instead of relying on the platform-specific synthesized scroll gesture. Keep tablet drags inside the viewport and verify that restoring overscroll containment blocks the same input before checking propagation to the page.
@cudoment
cudoment merged commit f7fb4a2 into main Nov 13, 2026
6 checks passed
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.

1 participant