kate522andClaude Opus 5
427968a721
The theme was renamed Zibll/子比 → AKSRT → Jio, but upstream branding survived the sweeps in CSS classes, the SVG sprite prefix, a persisted widget field ID, JS events, admin Vue class names, test infrastructure and docblocks. Renames: - zib-widget / zib-widget-wrap / zib-slider → jio-widget-box / jio-widget-box-wrap / jio-slider-box (jio-widget is taken by the modern widget shell, jio-box-* by the card primitives) - zib-partners-scroll + zps-* → jio-partners-scroll + jps-* - zib-combo-info-card + zci-* → jio-combo-info-card + jci-* - zibsvg- → jiosvg-, including the exported picker helpers and the fa-zibsvg- family-prefix guard - zibpay_type → pay_type; the dual-read fallback in PostQuery collapses to a single key - [zibajax="submit"] dropped (no PHP emitter); zib_ajax.success → jio_ajax.success - aks-* admin Vue classes → jio-* - zib_palette() → palette() User-facing vendor traces are gone: the floating "more" button default no longer ships a zibll.com link or 子比主题 marketing copy, the notice widget ships no preset promo entries, and the four 官网教程 links are removed from the post-list admin schema. Test infrastructure renamed to neutral names (docker-compose.reference.yml, Caddyfile, article-baseline.json, modern-widgets-contract.test.cjs) with their DB/volume/env/slug identifiers following. Kept intentionally, documented in tests/fixtures/README.md: the golden fixture reference fingerprint (a SHA-256 record of an external directory, read by validate-widget-golden / generate-widget-golden-fixture / audit-widget-system), the doesNotMatch guards that prove the old tokens are gone, and the reference theme's own meta key in the visual fixtures. No backward-compat or data migration: saved widget configs holding old icon keys or the old field ID silently lose them, per the project's rewrite-over-compatibility rule. Verified: 132/132 node contract tests, php tests/widget-system/run.php (146 assertions), audit-admin-contracts, audit-psr4-paths and validate-widget-golden all green; tracked bundles regenerated and in sync. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
36 lines
1.4 KiB
JavaScript
36 lines
1.4 KiB
JavaScript
'use strict';
|
|
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const test = require('node:test');
|
|
|
|
const root = path.resolve(__dirname, '..', '..');
|
|
const read = (file) => fs.readFileSync(path.join(root, file), 'utf8');
|
|
|
|
test('submit.css raises the TinyMCE fullscreen container above the fixed navbar', () => {
|
|
const css = read('assets/css/frontend/pages/submit.css');
|
|
|
|
// TinyMCE's skin injects .mce-fullscreen { z-index: 100 } at editor init,
|
|
// after core editor.css, so the fullscreen editor loses to the fixed navbar
|
|
// (.nav-fixed .header, z-index 999). The element+class selector outranks the
|
|
// skin regardless of injection order and restores core's intended 100010,
|
|
// which stays below the submit media dialog (100080).
|
|
assert.match(css, /div\.mce-fullscreen \{\s*\n z-index: 100010;\s*\n\}/);
|
|
});
|
|
|
|
test('the upstream toolbar affix rules stay removed', () => {
|
|
const css = read('assets/css/frontend/pages/submit.css');
|
|
const jsRoot = path.join(root, 'assets/js');
|
|
const js = fs
|
|
.readdirSync(jsRoot, { withFileTypes: true })
|
|
.filter((entry) => entry.isFile())
|
|
.map((entry) => read(`assets/js/${entry.name}`))
|
|
.join('\n');
|
|
|
|
// No Jio script adds .affix to .mce-top-part (that came from an old
|
|
// editor-extension script), so the affix positioning rules must not come back.
|
|
assert.doesNotMatch(css, /mce-top-part\.affix/);
|
|
assert.doesNotMatch(js, /mce-top-part/);
|
|
});
|