Skip to content

Tags

Tags

xzos-v1.18.0-3

Toggle xzos-v1.18.0-3's commit message

Verified

This tag was signed with the committer’s verified signature.
Zakkaus Zakk
xzOS theme on Remark42 v1.18.0: Termius Light and Aura Dark

xzos-v1.18.0-2

Toggle xzos-v1.18.0-2's commit message

Verified

This tag was signed with the committer’s verified signature.
Zakkaus Zakk
xzOS theme on Remark42 v1.18.0, dependency security update

xzos-v1.18.0-1

Toggle xzos-v1.18.0-1's commit message

Verified

This tag was signed with the committer’s verified signature.
Zakkaus Zakk
xzOS theme on Remark42 v1.18.0

v1.18.0

Toggle v1.18.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add the reply placeholder to the Dutch and Icelandic locales (umputun…

…#2266)

Both locales were added while the reply placeholder key was still in review, so they lacked it and the reply form showed the English text. Each gets its own comment placeholder under the reply key, as the other locales do.

The documented locale list named Icelandic but not Dutch.

backend/v1.18.0

Toggle backend/v1.18.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add the reply placeholder to the Dutch and Icelandic locales (umputun…

…#2266)

Both locales were added while the reply placeholder key was still in review, so they lacked it and the reply form showed the English text. Each gets its own comment placeholder under the reply key, as the other locales do.

The documented locale list named Icelandic but not Dutch.

v1.17.1

Toggle v1.17.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Stop capping cached responses at 64 KiB by default (umputun#2250)

* Stop capping cached responses at 64 KiB by default

Previously, cache.max.value defaulted to 65536 bytes, and the limit had
never been enforced for the byte slices remark42 caches. lcw 2.1.0 began
measuring byte slices, which activated the cutoff: a /api/v1/find
response of 64 KiB or more was rebuilt on every request while smaller
pages stayed cached, and a page with 300 comments went from 4.6 ms to
200 ms median server time.

After this change, the default is 0, unlimited per value, which is the
behaviour every earlier release had in practice. cache.max.size still
caps the whole cache at 50 MB, and an explicit CACHE_MAX_VALUE keeps its
value.

* Isolate the cache defaults test from the caller's environment

go-flags reads env tags as defaults, so a CACHE_MAX_VALUE set in the
shell running the tests would replace the built-in default the test is
about. The test clears the four cache variables for its parse and
restores them on cleanup.

backend/v1.17.1

Toggle backend/v1.17.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Stop capping cached responses at 64 KiB by default (umputun#2250)

* Stop capping cached responses at 64 KiB by default

Previously, cache.max.value defaulted to 65536 bytes, and the limit had
never been enforced for the byte slices remark42 caches. lcw 2.1.0 began
measuring byte slices, which activated the cutoff: a /api/v1/find
response of 64 KiB or more was rebuilt on every request while smaller
pages stayed cached, and a page with 300 comments went from 4.6 ms to
200 ms median server time.

After this change, the default is 0, unlimited per value, which is the
behaviour every earlier release had in practice. cache.max.size still
caps the whole cache at 50 MB, and an explicit CACHE_MAX_VALUE keeps its
value.

* Isolate the cache defaults test from the caller's environment

go-flags reads env tags as defaults, so a CACHE_MAX_VALUE set in the
shell running the tests would replace the built-in default the test is
about. The test clears the four cache variables for its parse and
restores them on cleanup.

v1.17.0

Toggle v1.17.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Correct stale configuration and contributor documentation (umputun#2248)

backend/v1.17.0

Toggle backend/v1.17.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Correct stale configuration and contributor documentation (umputun#2248)

v1.16.4

Toggle v1.16.4's commit message
fix(frontend): remove white flash on comments iframe load

on dark host pages the widget flashed an opaque white rectangle while loading.
the iframe element carries color-scheme from the theme param, but its document
had none until remark.tsx ran, and a mismatched color-scheme makes the embedded
canvas opaque instead of transparent. broken since umputun#2023 added the element-side
color-scheme to fix a firefox dark-mode bug.

set the document's color-scheme from the theme param in an inline head script,
before first paint, using the same rule as create-iframe.ts. that closes the long
window but not the surface browsers paint before the document is parsed, which
webkit renders white and chromium hides behind paint holding. so also create the
iframe hidden and reveal it when the document posts inited, with a timeout
fallback so a failed bootstrap cannot leave the widget invisible.

the reveal lives in createIframe rather than embed.ts so the profile modal, the
other caller, gets it too. that modal focuses its iframe on open, and a hidden
element cannot take focus, so focus now fires from the reveal instead of a timer.

covered by a unit test for the reveal paths and the event.source guard, and by
e2e for the document's color-scheme and the iframe's visibility before inited,
after inited, and after the fallback.