Captured with warc2zim 2.3.1 via a browser recording. The page renders correctly but never becomes interactive: the theme switcher and the colour-format tabs do nothing.
What I measured, on the ZIM served bare with no other reader involved:
- Every chunk the page references is present in the ZIM and served; no request leaves for the network.
- All ten inline scripts parse.
- No console errors, no page errors, no unhandled rejections.
- The turbopack runtime registers itself exactly as it does live.
self.__next_f keeps its 8 entries, where the live page drains it to 0. The RSC payload is never consumed, so React never mounts.
It is not the block-scoped globals issue (python-scraperlib#329): rebuilt with both a local hoist patch and the full fix from python-scraperlib#335, unchanged either way.
Live for comparison: clicking Alucard moves the palette from #282A36 to #FFFBEB. In the ZIM it stays.
Reported downstream at epheterson/Zimi#64.
Captured with warc2zim 2.3.1 via a browser recording. The page renders correctly but never becomes interactive: the theme switcher and the colour-format tabs do nothing.
What I measured, on the ZIM served bare with no other reader involved:
self.__next_fkeeps its 8 entries, where the live page drains it to 0. The RSC payload is never consumed, so React never mounts.It is not the block-scoped globals issue (python-scraperlib#329): rebuilt with both a local hoist patch and the full fix from python-scraperlib#335, unchanged either way.
Live for comparison: clicking Alucard moves the palette from
#282A36to#FFFBEB. In the ZIM it stays.Reported downstream at epheterson/Zimi#64.