| 开发者 | oksigenia |
|---|---|
| 更新时间 | 2026年6月23日 00:43 |
| PHP版本: | 5.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
oksigenia-access folder to the /wp-content/plugins/ directory.flex:1 1 auto; min-height:0) while the header and footer stay pinned and reachable.prefers-reduced-motion.-font or -cursor behind on the body class attribute after every reset. Classes are now removed one by one via classList, scoped to the oks- namespace, so the body is left exactly as the plugin found it. Also aligns the internal version constant used for asset cache-busting, which had fallen behind the plugin version.aria-hidden="true" but still held focusable controls, which axe and Lighthouse flag as aria-hidden-focus (serious) — a keyboard or screen-reader user could reach controls inside something hidden from assistive tech, and it contradicted aria-modal. The closed state now uses the inert attribute instead, removing the panel from both the tab order and the accessibility tree. No change when the panel is open; the focus trap, Escape-to-close and focus return were already in place.zoom: calc(1 / level) to the plugin elements to cancel the body zoom on them only.font-size scaling on html/body to CSS zoom on body. The previous approaches (17.1: html :has() + percentage; 17.2: pin body to 1rem) only moved elements that inherited their font-size; descendants that the theme had pinned with explicit font-size: NNpx declarations stayed put. On themes that hardcode px throughout (common in many classic WP themes), the text simply didn't scale even at level 4. zoom scales the rendered size of every descendant proportionally, like the browser's own Ctrl+= zoom, which is the behaviour users expect from a text-size control. Browser support: Chrome/Edge/Safari forever, Firefox 126+ (May 2024). Side effect: the plugin's own floating button and panel also scale with the level, matching native browser zoom behaviour.body { font-size: NNpx } (common on classic WP themes), the 17.1 text-size fix scaled the root <html> and anything sized in rem (logos, gaps, etc.) but left the body and its descendants pinned to the theme's px declaration — so the visible text didn't move. Now body.oks-zoom-N also pins font-size: 1rem !important, which re-anchors body into the rem chain so descendants that inherit (no explicit font-size) scale with the level. Descendants with their own explicit font-size: NNpx declaration are still isolated, which is the trade-off vs. the exponential bug of pre-17.0 versions.body.oks-zoom-N * rules applied font-size: 1.05em / 1.10em / 1.15em / 1.20em !important to every descendant via the universal selector. Since em is parent-relative, the factor compounded at every nesting level — a heading 3 levels deep ended up at 1.20³ = 1.73× its intended size, blowing up the layout at level 3 and making the page unusable at level 4. New rules apply font-size: NN% to the root <html> via :has(body.oks-zoom-N), so em / rem descendants scale exactly once. Same fix already applied to @oksigenia/access-panel since 0.3.3.oksiac_ across all functions, options, settings group, hooks, script handles, localized JS object and localStorage key (WordPress.org Plugin Review compliance).<style> and <script> blocks to enqueued assets (assets/css/admin.css, assets/js/admin.js).OKSIAC_VERSION constant for asset cache busting.admin_enqueue_scripts hook.