-
v1.7.49November 2026
New Input masks:
data-maskOne attribute on an ordinary
.inputformats the field as it is typed and sets the things that are easiest to forget: the numeric keypad on a phone, autofill and the validation pattern. No new classes and no CSS.- Eight shipped formats.
phone-pl,postal-pl,postal-de,nip-pl,card,card-expiry,iban,nrb-pl- plus masks of your own:data-mask="### ##-##"(#digit,Aletter,*digit or letter). - The card mask knows Amex. Cards starting 34 and 37 are 15 digits as 4-6-5, not 16 as 4-4-4-4 - the mask switches by itself. Four fixed groups of four dropped the last digit, and the symptom was a declined payment rather than a visible bug.
- Pasting with a country code.
+48 601 234 567pasted intophone-plloses the prefix, not the end of the number. The prefix is dropped ONLY when it is the sole reason the value overflows, so a nine-digit number that happens to start with 48 is left alone. - Caret, deletion and undo. Editing inside the value no longer throws the caret to the end. Backspace past a separator removes a digit, not the space the mask would instantly put back (without this the key looks broken). The value is written through
execCommand, the only path that keeps the browser's own character-by-character undo - measured, not assumed. - Not on
type="number"ortype="email". Those types cannot carry a caret: reading its position returnsnulland setting it throws. The module refuses loudly with a console warning instead of quietly dropping the caret to the start. An amount or a card number istype="text"withinputmode="numeric". - The field still works without JS. It stays an ordinary
.inputwithinputmode,autocompleteandpattern- it loses the separators, not the validation. Every preset pattern accepts the value with AND without separators, because otherwise a user without JavaScript typing bare digits would get a false error. - What reaches the server. By default what the user sees, the value with its separators - a plain
<form>works with no extra code. For the clean value,data-mask-unmasked-name="name"adds a hidden field. - Tests.
npm run test:mask- 42 checks in a real browser, every trap paired with a negative control (an unmasked field, a number the rule must not touch). The suite was also put through 12 source mutations: each breaks exactly one behaviour, and each one is caught. - Can be removed: if your project carries its own script masking a phone number, tax id, card or IBAN, you can delete it and keep
data-mask. After updating, check the fields where you keep a mask of your own - two masks on one field will fight over the caret.
- Eight shipped formats.
-
v1.7.48November 2026
Fix
grid-cols-2 grid-md-cols-4has two columns on a phoneA phone layout written next to a responsive class was silently dropped: the grid had one column, with no error.
- What was wrong. Below their breakpoint,
.grid-md-cols-*and.grid-lg-cols-*default to a single-column grid. That rule came after.grid-cols-*in the stylesheet and weighed the same, so it won andgrid-cols-2did nothing. The single-column default now applies only when there is no.grid-cols-*next to it. - Unchanged:
grid-md-cols-4alone andgrid-cols-1 grid-md-cols-3have one column on a phone, and the same as before from the breakpoint on. - Tests.
npm run test:componentscounts the columns of six combinations on a phone, a tablet and a desktop. - Safe to remove: if you forced phone columns with your own CSS or with
.grid-auto, you can go back togrid-cols-2. Check after updating: a phone, wherevergrid-cols-2or more stands next togrid-md-cols-*orgrid-lg-cols-*. There was one column there until now; there will be as many as you wrote.
- What was wrong. Below their breakpoint,
-
v1.7.47November 2026
New The whole Phosphor catalogue in motion: 85% of the icons have their own
Of the 1512 icons in the stroke weights, 587 move a part, 699 move as a whole and 226 give a short pop on purpose. This closes the work that began in 1.7.44.
- Documents. The lines of text in
list-*,article-*,receiptandchat-textwrite themselves one by one. Infile-*what is on the sheet draws itself: the letters of a format, a picture, a padlock. The sheet stays. - Lids and flaps. The flap of
envelope, the shackle oflock-key, the lid oftrash-simpleandarchive, the bow ofgift, the tab offolder-*, the handle oftoolbox. - Signals. The arcs of
wifi-*,rss,broadcastandspeaker-*spread from the centre; the bars ofequalizerandwaveformripple. - Levels. The bars of
cell-signal-*andchart-bargrow from the ground, the levels ofbattery-*come one by one, andstairs,stepsandladderdraw themselves. - Hands.
clock-*,timerandwatchturn a hand around the dial, the needle ofgauge,speedometerandcompasstrembles on its axis, the mercury ofthermometerrises, the knobs ofslidersmove apart. - Small things. The dots of
dots-*appear in turn, the eyes ofsmiley-*blink, steam rises fromcoffeeandbowl-steam, the lights oftraffic-signalblink, thefilm-slateclaps, the top ofstacklifts and a sheet comes out ofprinter. - Neutral: 226 icons. 78 brand logos, 14 religious and serious symbols, 124 objects with no natural motion (furniture, food, clothes, screens), 9 things with a misleading name, such as
baseball-cap, androad-horizon. Any of them can takedata-icon-anim. - Size. The module weighs 105 KB minified, 10.4 KB gzipped. All the motion is in the CSS, the script has not changed.
- Tests.
npm run test:icon-catalogalso checks what must stay still: the lid of a box, the stand of a monitor, the terminal of a battery, the sheet, the rings. - Safe to remove: nothing. Check after updating: nothing, classes and attributes are unchanged. With PurgeCSS, take the new
purgecss.safelist.cjs.
- Documents. The lines of text in
-
v1.7.46November 2026
New Nearly 400 icons now move only a part
The families of the previous release get part motion, in all five stroke weights. The fill weight, the web font and flattened SVGs keep moving as a whole.
- The slash. In 35 of the 36
*-slashicons the line draws across an icon that stands still. Incalendar-slashit is melted into the outline, so the whole icon moves. - An arrow in a frame. In
arrow-circle-*,arrow-square-*andcaret-circle-*the arrow goes its way while the ring and the square stay. - Transfer. In
download,upload,tray-arrow-*,file-arrow-*,cloud-arrow-*,box-arrow-*,hand-arrow-*only the arrow moves; the tray, the sheet, the cloud and the hand stay. - The head. In
user-*,users*andperson*the head nods, the shoulders and the frame stay. - The sign. A tick, a cross, a plus and a minus in a frame draw themselves while the frame stands:
check-square,x-square,shield-check,minus-circle. - Drawing. Digits, letters, currencies, shapes, diagrams and bent arrows trace themselves. That leaves only 278 neutral icons.
- A change in six presets:
arrow-circle-up,-down,-left,-right,arrow-square-outandcloud-arrow-upmoved the whole icon while their siblings would now move only the arrow. They joined the family. The other 112 presets move as before. - Size. The module weighs 81 KB minified, 8.6 KB gzipped.
- Tests.
npm run test:icon-catalogalso guards that no animation overwrites atransformattribute and that a part moves the way the icon name says. - Safe to remove: nothing. Check after updating: the six presets above; if you relied on the whole icon moving, set
data-icon-anim="nudge-right"or similar.
- The slash. In 35 of the 36
-
v1.7.45November 2026
New More than 1000 icons now move the way they should
Instead of a short pop, an icon gets the motion of its family, with no change to your page. This covers 1018 of the 1512 icons, in the fill weight and the web font too.
- Families instead of lists. The car drives, the flame flickers, the flag waves, the ball bounces, the gear turns, an arrow goes the way its name says, and
arrow-bend-up-leftends up going left, like its head. The rules catch names by whole words, so the module only grew from 3.8 KB to 7.2 KB gzipped. - 494 icons stay with the pop on purpose. Brand logos, religious symbols and objects with no natural motion. 204 of them are signs and shapes that will draw themselves in the next release.
- Eight new
data-icon-animvalues:press,rock,flap,sway,flicker,page-turn,zoom-in,zoom-out. - The fill weight and the web font. An icon with a parts preset, such as
lockortrash, used to just pop in this weight, because it has no parts. It now moves as a whole, like its family. The stroke weights are unchanged: the 118 presets move exactly as before. - Fix: PurgeCSS removed every preset. Only the script writes
data-icon, so PurgeCSS never saw the attribute in the HTML and, with the shipped safelist, dropped all presets, leaving icons that only popped. This goes back to 1.7.38. The safelist now hasgreedy: /data-icon/. - Tests.
npm run test:icon-catalogchecks every icon in every weight in a real browser: that it moves, that no shape left the icon, that the direction matches the name, that the presets did not change. - Safe to remove: if you added
data-icon-animonly to get something other than a pop, check whether the family motion is enough. Check after updating: icons without a preset now move differently, and take the newpurgecss.safelist.cjs.
- Families instead of lists. The car drives, the flame flickers, the flag waves, the ball bounces, the gear turns, an arrow goes the way its name says, and
-
v1.7.44November 2026
New A gallery of the whole Phosphor catalogue
The Animated icons page now shows all 1512 icons instead of 118, and the search finds them in Polish, English and German. The animations have not changed: 118 icons have their own motion, the rest get a short pop.
- The whole catalogue in the gallery. The cards are generated from data at build time (
tools/gen-icon-gallery.js), like the class reference. The gallery scrolls in its own window, so the rest of the page stays within reach. - Search in Polish and German. A dictionary of 1311 words turns Phosphor names and tags into stems: "kosza", "kłódki", "samochodu", "Glocke", "Drucker" find the right icon in any inflected form. The hand-picked stems of the 118 icons stayed.
- A separate sprite file. Only this page fetches
img/icons-anim-all.svg(940 KB, 89 KB gzipped).img/icons-anim-demo.svgwent down from 74 KB to 23 KB, so the documentation page got lighter too. data-search-target: ß means ss. The search treatedßas a letter of its own, so "Strasse" did not find "Straße".- Tests.
npm run test:icon-galleryruns the real search on the generated cards, in both directions: that "koszula" finds the shirt, and that it does not bring up the bin. - Safe to remove: nothing. Check after updating: nothing, classes and attributes are unchanged.
- The whole catalogue in the gallery. The cards are generated from data at build time (
-
v1.7.43November 2026
Fix 57 icons fell apart as soon as they got
.icon-animThe bug turned up while checking the whole Phosphor catalogue. None of the 118 icons with their own animation has it, which is why the gallery and the tests never showed it.
- Shapes with a
transformattribute. Phosphor rotates some shapes with an attribute, for example<rect transform="translate(256 0) rotate(90)">. Thetransform-box: fill-boxrule applies to that attribute as well, so the rotation ran around the centre of the shape instead of the corner of the icon, and the shape ended up outside the icon. This happened at rest, with no trigger at all, in the thin, light, regular, bold and duotone weights. It hitmonitor,desktop,calculator,device-tablet,arrow-square-left,eject,diamond,alienand others. The fill weight was not affected. data-icon-anim="draw"no longer scales such shapes. Scaling overwrote the attribute, so the eyes ofalienin the bold weight jumped during the animation. They now fade in where they stand.- Tests.
npm run test:icon-animmeasures the position of such a shape at rest, including a duotone layer. - Safe to remove: if you kept these icons out of
.icon-anim, you can add them now. Check after updating: nothing, the animations of all other icons are unchanged.
- Shapes with a
-
v1.7.42November 2026
New Command palette and keyboard support in selects
A field with a list of results and full keyboard support. The same layer fixes
.select-searchand.custom-select, which did not work from a keyboard..command-palette. A search field with a list of results in a native<dialog>: groups, empty states, full screen on a phone with a close button, an optional Ctrl/Cmd+K shortcut. Items in the HTML are filtered without diacritics and by the stems indata-tags.- Server results: the
command:searchevent. Your code answers throughe.detail.respond(), with an array or a Promise. The listener can go in at any time, even before the module loads. Old queries are aborted, late answers are ignored, and results reach the page as text, so a record name cannot run code. This is the hook for global search in a panel: the endpoint and permissions stay with the project. .select-search: keyboard and ARIA. Options are plain<div>elements, so they could not be chosen from a keyboard, and despite the “combobox” name the component had no ARIA attributes at all. The arrow keys, Home/End, Enter, Esc and Tab now work, also without a search field. The markup is unchanged.- Enter in
.select-search-inputdoes not submit the form. A select inside a<form>used to submit the whole form on Enter in the search field. .custom-select-searchfilters. The field was only a look: no code read it, so typing changed nothing. It now filters options and hides categories with no match, and the arrow keys move focus between checkboxes, which stay native.- Search without diacritics. In both selects “lodz” finds Łódź. The filter goes away when the menu closes, so the next opening shows every option.
- Autoloader.
molique-combobox.jsandmolique-command-palette.jsare new, andmolique-select.jsalso loads for a.custom-selecton its own. Copy the wholejs/modules/folder. - To remove: nothing, there were no keyboard workarounds. Check after updating: forms that relied on Enter in a select-search field submitting them.
-
v1.7.41November 2026
Fix Reports from a B2B panel: menus, tiles, tooltip, autoloader
Each point gives the symptom before the fix and the workaround a project can remove after updating to 1.7.41. Every symptom was reproduced in a browser on version 1.7.40.
.with-dividers. With a[popover]menu after the last button, that button kept a divider on its right, because the last child of the group was the invisible menu. The menu now takes no divider and does not count as the last item. To remove: your own rules hiding::afteron the last button..dropdown-menu[popover]. A long menu ran off the screen (60 items are 2291 px on a 700 px screen) and its last items could not be clicked. Its height is now limited by--dropdown-max-height(45dvhby default) and the list scrolls inside. To remove: your ownmax-heightandoverflow-yon the menu..tabs-pillwithout.tabs-content. A pill used as a filter or navigation took the full width (614 px while drawing 191 px) and pushed its neighbours away. It now takes the width of the pill, with no markup change. To remove:width: max-contenton.tabs. A pill with panels works as before..badgeand.badge-light. A.badgewith no variant had white text and no background, and.badge-lightdid not exist, so such a label was invisible on a light page..badgenow looks like.badge-secondary, and.badge-lightworks in both themes. To remove:badge-secondarystand-ins used only to make a label visible.- The autoloader and AJAX components. The autoloader checked the page once, at the start, so a component added later silently stayed without its module. The module now arrives then too. To remove: loading modules by hand after replacing a fragment. The
[data-tour]and[data-onboarding]guides still work only from the start of the page. - The autoloader and a module already on the page. A module included by hand “just in case” was loaded a second time and ended in
SyntaxError: Identifier has already been declared. The autoloader now detects it and only initialises it. To remove: conditions working around including it by hand. .admin-mainon a phone. 32 px of padding on each side took close to a fifth of a 360 px screen. Up to 768 px the padding is now 12 px, and the bottom one stays large because the navigation bar sits over it. Tokens:--admin-main-paddingand--admin-main-padding-mobile. To remove: your own.admin-mainpaddingin a media query..tooltip-element-start. A new variant: the bubble starts at the left edge of the trigger. A centred bubble in the first column lost its left half with no sign of it. To remove: your ownleft: 0and--tooltip-tx: 0.- A locked
.selection-tile. The tile had no disabled state.input:disabledand<fieldset disabled>now dim it and set the not-allowed cursor, while a checked tile keeps its full colour. To remove:fieldset:disabled .selection-tilerules. .tile-content. The selected state recolours the border, and the tile had none of its own, so without.borderin the markup an unselected option had no outline at all. The border is now part of the component. To remove: the.borderrequirement, if a test or a template enforces it. The.borderclass still works..dropdown-header. A new label above a group of menu items, indented like.dropdown-item. To remove: class sets such aspx-2 pt-2 pb-1 text-1 text-muted fw-bold..text-nowrap. A new class: text that does not wrap. To remove: non-breaking spaces added only to keep a currency from dropping to a new line..flex-row,.flex-md-row,.flex-md-column..flex-rowdid not exist, and.d-flexdoes not change the column in.card-body, so such a layout stayed vertical. These classes now beat the direction of a component, includingclass="card-body flex-row". To remove: a separate child of.card-bodyadded only to get a row. A.cardwith.flex-md-rownow lays out in a row frommdup, as the class says; the class used to be ignored..flex-shrink-0. The class did not exist, yet templates used it and it silently did nothing, so a button next to a long text wrapped its label. It works now. To remove: nothing, existing uses start working by themselves..grid-expand-unchecked. A new variant, the reverse of.grid-expand: content visible while a.form-switchstanding earlier in the same parent is off. To remove:form:has(input:checked) …{ display: none }rules, if the panel is a sibling of the switch.- Check after updating. A
.cardwith.flex-md-rowbecomes a row, a menu taller than 45% of the screen now scrolls inside, a.tile-contentwithout.bordergets a border, and a.badgewith no variant gets a grey background. That includes labels coloured by your own CSS in a layer belowcomponents.
-
v1.7.40November 2026
New Search in the icon gallery, the tick stays put during a loop pause
The animated icon gallery can now be searched like the Phosphor catalogue, and
data-search-itembrings the same search to any list.- Gallery search. The field above the preset gallery filters 118 icons by name and by the tags from the Phosphor catalogue: “alarm” finds
bell, “delete” findstrash. / puts the cursor in the field, Esc clears it. data-search-item. Thedata-search-targetsearch only worked on table rows and silently did nothing on a list of cards. The new attribute names the elements to filter, e.g.data-search-item=".card". Tables work as before.- Loop pause.
data-icon-anim-loop-delayheld the icon on the first frame of the next lap, and for a drawing animation that frame is empty: the tick in the circle vanished for the whole pause. The icon now returns to its normal look during the pause, and a loop outside the viewport also stays paused after the first pause.
- Gallery search. The field above the preset gallery filters 118 icons by name and by the tags from the Phosphor catalogue: “alarm” finds
-
v1.7.39November 2026
Fix Animated icons: the spinner finally spins, new motion for confetti, heartbeat, the phone and the pencils
Fixes and suggestions from the first days of the
icon-animmodule. The main one: in v1.7.38 thespinnerpreset showed no visible motion at all.- Spinner. Eight identical ticks 45° apart turned in 45° steps, so every step drew the same picture. Now the ticks fade out and back one after another, and a dimmed tick with a tail runs round the circle. When the JS cannot split the icon into parts (web font, flattened SVG), the spinner turns smoothly.
- Confetti fires. The cone kicks back and four pieces fly out of its mouth into place. Heartbeat beats and draws its ECG line. Phone-call rings while the signal arcs pulse twice, inner one first.
- Pencils write. In
note-pencilonly the pencil writes and the sheet stays put.pencil,pencil-simpleandpenmake a writing stroke to the right instead of a wobble,pencil-linelays its line out from under the tip, andsignaturesigns itself. - Every weight. Bold orders the elements of some icons differently, so the new presets pick parts by type and shape (the closed path, the
polyline, the n-thline) rather than by number. Checked against the Phosphor source files in thin, light, regular, bold and duotone. - PurgeCSS. The safelist only protected the whole-icon animations. Part animations (
iconAnimPart*) are named through--_icon-anim-part-name, so withkeyframes: truePurgeCSS removed every one of them and the parts stood still. The safelist now covers all 40 animations of the module, andnpm run test:cssalso checks the part animation names. - Examples. The status “Final inspection approved” drew its tick once, while you were scrolling, so it looked dead. It now draws when it scrolls into view and repeats every 2.5 s. The module weighs 32 KB minified, about 3.8 KB gzipped.
-
v1.7.38November 2026
New Animated Phosphor icons: an opt-in module
A separate file,
molique-style-icon-anim.css, brings to life the Phosphor icons molique has used from the start. What moves is what the icon shows: the lid of the bin, the shackle of the padlock, the hands of the clock, and the tick draws itself. The trigger can sit on a button or a card, not only on the icon. The icons were designed by Helena Zhang and Tobias Fried (Phosphor Icons, MIT License).- Classes.
.icon-animon the icon and the triggers.icon-anim-hover,.icon-anim-tap,.icon-anim-viewand.icon-anim-play, which work on the icon or on any ancestor. The modifiers.icon-anim-loop,.icon-anim-persist,.icon-anim-fastand.icon-anim-sloware CSS custom properties, so they inherit like the text colour.data-icon-animpicks one of 20 animations instead of the default. - More than a hundred presets that move parts. The JS (
molique-icon-anim.js, loaded by the autoloader) expands<use>into real elements and numbers the parts. The numbering is shared by the thin, light, regular, bold and duotone weights. Copying a symbol lets through only basic shapes and their attributes, so a sprite cannot bring a script or an event attribute into the page. Without JS, with the flattened SVGs from npm, with the web font and in the fill weight, the whole icon moves. - Light despite a hundred presets. Presets only set variables, and the list of triggers lives in two rules for the whole module: 26 KB minified, about 3 KB gzipped. The first version, with the triggers in every rule, weighed 120 KB.
npm run test:cssnow also checks animation names passed through variables. - Accessibility. With
prefers-reduced-motion: reducethe icons stay still. Hover only works on devices with a pointer and also reacts to keyboard focus. A tap plays to the end even after a quick touch. A looping icon off screen waits. - New pages: documentation and examples with a preset gallery. The sprite generator handles several
img/icons-*.svgfiles, so the gallery icons do not weigh on the sprite every page loads.
- Classes.
-
v1.7.37September 2026
Fix Toast content is text, not HTML
Up to v1.7.36
MoliqueToast.show()pastedmessageinto a template throughinnerHTML. Any text from outside the page code - a URL parameter, a server response, a file name typed by a user - was therefore parsed as HTML. In an admin panel built on molique, a link with a parameter shown in a toast ran someone else's code for everyone who clicked it.- The message goes in through
textContent. The toast is built from elements and the content is plain text: markup shows literally and nothing runs. The look is unchanged. As a bonus, a sentence with a<sign (“value < 100”) no longer loses everything after it. - HTML only on purpose: new
html: trueoption. Only the booleantrueworks, and only on the message itself. Use it only with text written entirely by the page code - never with data from a user or a server. If you passed markup to toasts so far, add this option. durationmust be a number. Anything else falls back to 4000 ms instead of reaching the animation style. Tests:npm run test:toast.
- The message goes in through
-
v1.7.36September 2026
New Cinematic corner light: .bg-cinema
A dark background in the colours of a film poster - cool light in one corner, amber in the opposite one, a deep near-black in between. It combines the corners of
.bg-gradient-cornerswith the slow motion of.bg-blobs.- New class
.bg-cinema. Cool blue in the top-left corner, amber in the bottom-right, a subtle film grain. Both glows breathe very slowly, each at its own pace, so they do not pulse in step. The background is always dark, like.bg-blobs-deep, and sets light text. The glows are ellipses sized from width and height, which keeps them in the corners on a wide hero, a card and a tall column;.rounded-*clips them along with the corners. - Controlled by variables.
--cinema-1and--cinema-2(whole colours, hex works too),--cinema-bg,--cinema-speed(16 s) and--cinema-grain(noneturns the grain off). The classic film teal instead of blue takes three variables - see the example in the docs. The grain is an SVG tile baked into the CSS, with no extra file; it also hides the banding of long, dark gradients. The motion istransformandopacityonly and stops underprefers-reduced-motion.
- New class
-
v1.7.35September 2026
New Corner shape, entrance animations and a hiding navbar without JS
Native
corner-shapechanges the shape of the rounding instead of cutting the element out after painting, asclip-pathand masks do. That is why the border and the shadow follow the shape. On top of that, two things that neededmolique-script.jsso far are now done by CSS alone in newer Chromium - the script stays as the fallback for other browsers.- New classes
.corner-shape-squircle,-bevel,-notchand-scoop. They work on an element that already has aborder-radius: the radius sets how deep the corner goes, the class sets its shape. For subtle corners.rounded-2or.rounded-3is enough; with.rounded-5on a small element-notchturns it into a cross. A browser without support (outside Chromium) drops the declaration and the ordinary rounding stays, with no fallback code. - Entrance animations on
animation-trigger(Chrome/Edge 145+)..animate,.reveal-blurand.reveal-scalestart their entrance by themselves once 10% of the element scrolls into view - the same threshold as the observer so far.molique-script.jstests the identical@supportscondition and then creates no IntersectionObserver at all, so the two paths never run together. A side effect to watch: on this path the.is-visibleclass is not added, so your own styles built on.animate.is-visiblenow only work in Firefox and Safari. The gain: content with.animateno longer stays invisible when JavaScript does not run..delay-*now also delays the animation. - Hiding
.navbar-stickythroughscroll-state(Chrome/Edge 144+). The bar hides on scroll down and comes back on scroll up with noscrolllistener - through an@container molique-page scroll-state(scrolled: bottom)query on:root. It also works without JS. The JS still sets.is-hidden, because it computes.is-scrolledand the reading bar anyway, and support for the query cannot be detected with@supports- the two mechanisms add up. The only visible difference: CSS hides the bar from the first pixel down, the JS waits 100px. An open mobile menu keeps the bar in place in both cases. - The
.corner-cut-*description in the class list was wrong. It saidmask-image, while the cut usesclip-path(only.corner-concave-*uses a mask). The description now also says that both families cut off the border and shadow of the element, so they only fit when the cut must exist in every browser. - Roadmap: rebuilding on native
@functionandif()is on hold. As of September 2026 this only works in Chrome/Edge, and an unsupported declaration is dropped entirely, so the core would stop working in Firefox and Safari.
- New classes
-
v1.7.34September 2026
New A tooltip no table or card can clip
.tooltip-elementdraws its bubble as a pseudo-element inside the trigger, so tables, cards, accordions and modals cut it off. A pseudo-element cannot be moved out of there, by CSS or by script, so a second tooltip built on the Popover API has been added.- New class
.tooltip-popover(+.tooltip-popover-bottom). A separate element withpopover="hint"androle="tooltip"that lands in the top layer once open. The trigger points at it througharia-describedby- the only link, so the screen reader description cannot go missing. The bubble sits above the trigger, flips below or slides sideways when there is no room, and keeps 8 px off the window edge. It wraps on its own up to--tooltip-max-width. There is no arrow, because after a flip it would point the wrong way. - New module
js/modules/molique-tooltip-popover.js. Auto-loaded with.tooltip-popover, because a popover does not react to hover by itself. Opens on hover (150 ms), at once on keyboard focus and touch; closes when the pointer leaves (the bubble can be hovered to finish reading), on Esc, when focus moves away and on a tap elsewhere. Only one is open at a time. It is delegated, so rows added by AJAX need no initialisation.popover="hint"(Chrome/Edge 133+) does not close an open menu; an older browser treats it asmanual, and the module does the closing anyway. Without Anchor Positioning the module places the bubble itself. From code:MoliqueTooltipPopover.show(trigger)/.hide(). Tests:npm run test:tooltip-popover. .tooltip-elementdid not wrap. The base hadwhite-space: nowrapwith no width limit at all, so a longer description ran as one line across the whole screen (measured: 627 px for two sentences). Wrapping only existed in the-widevariant, which you had to know about. Now every bubble wraps at--tooltip-max-width(280px), and a short label stays on one line, because the bubble haswidth: max-content. Multi-line text is centred;-widestays as the left-aligned variant for full sentences..tooltip-elementin dark mode: white text on a near-white bubble. The bubble background is--dark, which inverts to#ECEDF8in dark mode, while the text was a fixed#fff. The text now uses--light, which inverts together with the background: 15:1 contrast in dark mode and 17:1 in light mode.- Docs:
.overlap-up-50/-100/-150only work frommdup. The classes are defined only from 768 px, so on a phone they do nothing, and the description did not say so. Behaviour is unchanged. For an offset on mobile too, use.overlap-container.
- New class
-
v1.7.33September 2026
Fix A modal nobody can see, and nine defects from a production B2B panel
Everything below came from B2B panel deployments on molique, where each of these already had a patch on the client side. A patch at one integrator is not a framework fix, so the causes were removed here.
- Modal on iPhone: dimmed screen, no window. Reported three times by users. The screen dimmed, no window appeared, and since
showModal()makes the page underneath inert, there was nothing to click or close. Two causes, each sufficient on its own. First: the entry started fromopacity: 0in@starting-styleand relied on thedisplay/overlayallow-discretetransition, while::backdrophas no animation of its own. When the transition did not run, the backdrop was there and the window stayed transparent. The entry now animatestransformonly, so there is no frame in which the backdrop exists and the window does not. The exit still fades. Second: the.cardin a modal was capped withmax-height: 100%of a parent that has amax-heightbut noheight. A percentage of an indefinite height is where engines disagree. The card now shrinks through the flex chain (min-height: 0), no percentages. - A safety net for modals:
.is-fallback. The fix above removes the known causes, not the next one. A new module,js/modules/molique-modal-guard.js(loaded automatically when the page has a.modal-dialog), asks the device after every opening whether the window painted: at least 40px in size, opacity above zero. The first look runs inrequestAnimationFrame, because before the first paint there is nothing to measure. If it fails, the verdict waits for a second look, because an opening animation can leave the window transparent for a moment. The wait is not fixed: the module reads the longesttransitionandanimationfrom the style of the window itself (duration × iterations + delay), with a floor of 450 ms and a ceiling of 3 s, so a project with a slower modal entrance does not get a false fallback. Only then does the window get.is-fallbackand is redrawn as a plain block, with no flex, percentages or animation. The fallback declarations carry!important, because they must also beat a project's unlayered stylesheet, which may be what broke the window. The module observes theopenattribute instead of patchingshowModal(): the declarativecommand="show-modal"opens a dialog without calling the JS method, so a patch would miss it. Only.modal-dialogis guarded. The onboarding and tour overlays are transparent by design, and the lightbox paints its own background. Tests:npm run test:modal-guard. - The welcome card cut off longer descriptions on phones. On a small screen the card is one screen tall with
overflow: hidden, and the slide had no scrolling of its own. The overflow vanished mid-sentence, with no scrollbar and no hint that more text existed. The slide now scrolls itself (min-height: 0+overflow-y: auto). Centering moved fromjustify-content: centerto two growing spacers, because center alignment in a scroll container pushes content past BOTH ends and the top part cannot be scrolled to. A long slide now starts at its first line. This also surfaced that the slide's mobilepaddingnever applied: the base rule sat after the media query in the file and overrode it. Phones now get an even 32px instead of 48/24. The tour tooltip (.tour-tooltip) got the same vertical clamp. - Header actions overlapped the title on phones.
.dashboard-header-actionshas a negativemargin-topthat the cutout effect relies on. The mobile branch reset the background, padding and radius, but not the margin, so the actions block rode up over the title. - The narrow sidebar variants also rearranged
.admin-rail. The.sidebar-md/.sidebar-smrules caught every.admin-nav-linkin the layout, including the fixed-width second column. The rail got micro text or lost its labels. Now scoped to.admin-sidebar, like the drill-down selectors in 1.7.32. - Navigation in
.admin-railwas painted in the dark sidebar's colors. The rail deliberately has no background and sits on the light--bg-body, while.admin-nav-linktook the light--sidebar-text. The rail now re-points four--sidebar-*variables for its subtree, so every nav rule works without duplication. Inactive items take--text-main, not--text-muted: muted text on--bg-bodyis 4.48:1 in light mode, just under WCAG AA. .btn-stackedbroke one-word labels into a column of letters.word-break: break-wordbroke inside words, so in a narrow column “PODGLĄD” came out as “PO / DG / LĄ / D”. Nowoverflow-wrap: break-word: wrapping between words, breaking a word only when it cannot fit at all.- A lone icon in the header actions stays on the title row. On phones the actions drop below the title at full width, which is right for a row of buttons. A single bell, though, landed on its own line, flush left, next to an empty strip. When every direct child of
.dashboard-header-actionsis a.btn-icon, the actions stay next to the title. One wider button and the header stacks as before. - New class
.tooltip-element-wide. A bubble for a full sentence: wraps, left-aligned, up to--tooltip-max-width(280px by default), never wider than the screen. The default bubble staysnowrap, because a short label should never break. - Closed onboarding, tour and lightbox dialogs are protected like the modal. Their
display: nonewas a normal declaration inside a layer, so any unlayered rule settingdisplayondialog(a project's own or a third-party plugin's) showed the closed dialog. Now:not([open])with!important, as on.modal-dialog. The closing animation survives, because a running transition outranks!importantin the cascade.
- Modal on iPhone: dimmed screen, no window. Reported three times by users. The screen dimmed, no window appeared, and since
-
v1.7.32August 2026
Fix Double-nested layers, values baked into CSS, and traps found while shipping a real service site
A note on numbering: version 1.7.31 went out on npm carrying 1.7.30 content - the package directory is generated by
tools/build-npm-molique.mjs, and that release only bumped the number inside it without regenerating the files. npm does not allow republishing a version, so this release is numbered 1.7.32 and 1.7.31 is marked deprecated. 1.7.31 was never deployed to the site.- Nested
@layerremoved from 36 files. Partials wrapped themselves in their own@layerand the entry point wrapped them again, compiling to@layer utilities { @layer utilities { … } }. The cascade broke BOTH ways depending on!important: normal declarations in the sub-layer lost to unwrapped rules of the same layer, while!importantones won. Reported from a deployment where overriding.bg-darksilently lost - navy#14162Bversus#16233C, invisible to the eye. Layers are now assigned by the entry point only. Verified by script: all 8 bundles identical once layers are flattened, zero selectors changed their winner. - Tabs had two different silent thresholds. The positional mechanism for
.tabswas written out to 10 tabs, the.tabs-pillindicator to 8. An eleventh tab produced an empty panel; a ninth pill tab showed its panel but left the indicator parked under the first label with no color change - the component looked half-broken. The failure mode was the worst part: the panel never left the HTML, the console stayed clean, the section rendered fine, so the first suspicion always went to the backend. There is now one shared$tabs-max: 16for both variants, raised via@use ... with (...)instead of forking the file. Beyond the threshold a panel does NOT vanish - it stays permanently visible, a failure you see at a glance instead of one you cannot see at all. Selectors are collected into lists and emitted as three rules rather than3 × threshold, so going from 10 and 8 up to 16 cost 439 bytes of CSS instead of duplicating every declaration. - A form in a modal no longer blows the window open. A modal is a height chain:
.modal-dialogis a flex column capped at the viewport,.cardinherits that cap viamax-height: 100%, and.card-bodyis the ONLY thing that scrolls. A plain block<form>inserted into that chain severs it -max-height: 100%then resolves against the form's auto height, i.e. against nothing,.card-bodyhas nothing to overflow, and the window grows past the screen taking the header and footer with it. A wrapping form now getsdisplay: contentsand generates no box of its own, so the chain stays intact. It covers both real positions: a form around the whole card, and a form inside the card wrapping.card-body+.card-footer- and with them all three variants (.modal-dialog,.modal-context,.modal-confirm), since each carries the base class. A plain form INSIDE.card-bodydeliberately stays a block: unwrapping it would drop its children into.card-body's flex column and space them out with itsgap. - The
hiddenattribute hides again. The UA stylesheet gives[hidden]adisplay: none, but the UA sheet is the WEAKEST source in the cascade - any author rule settingdisplaybeats it. In practice<div class="card-body" hidden>stayed visible, because.card-bodysetsdisplay: flex; likewise.card-footer,.data-row-compact,.navbarand every other component with its owndisplay. Two modal panels could show at once. The rule now lives in thebaselayer with!important- for!importantthe earliest layer wins, so it also beats.d-flexand.d-block, which carry!importantinsideutilities. A project cannot fix this on its own: an unlayered!importantis the weakest one there is, so it beats.card-bodybut silently loses to.d-flex.hidden="until-found"is excluded so find-in-page keeps working. - Always-dark surfaces finally have a token.
#14162Bsat as a literal in eight places (.bg-dark, hero, footer,.navbar-pill,.bg-gradient-corners). It is now--bg-dark-fixedand--text-on-dark-fixed, declared once and deliberately NOT flipped in dark mode. Rebranding means changing a variable instead of fighting the cascade - which matters, because utilities carry!importantinside a layer, and an!importantoutside any layer is the weakest thing in the author cascade and always loses. Footer accent separately:--footer-accent/--footer-accent-hover. - The pricing ribbon label is no longer baked into CSS.
.pricing-table.is-featured::beforehadcontent: 'Popularne'- a Polish word no other project could change without overriding the whole component. Nowvar(--pricing-ribbon, 'Popularne'). .before-after-sliderno longer blows up the layout. Sizing lived only in.before-after-img, so forgetting it was not a cosmetic slip but a layout bomb: the image kept its intrinsic 1600px, and a bare1frgrid track takes its minimum from the descendant's min-content, so the TRACK expanded despiteoverflow: hidden. The rule now sits on theimgitself; the class still works as an alias.- Checkbox grew from 20px to 24px. The control is deliberately exempt from the 44px rule, but 20px failed the Lighthouse audit, which requires at least 24px. Resize via
--form-check-size. This is a VISUAL change - check dense forms after updating. - A submenu outside the sidebar painted over the whole page. The drill-down selectors were scoped to nothing, so
.admin-nav-submenu[open]ANYWHERE on the page - a documentation demo, a nav rendered into the content column - received the full-screen drill-down panel. Two branches, both live: on mobile (≤768px) unconditionally, with no.sidebar-*class at all - the submenu list gotposition: fixed; inset: 0; z-index: 1050and a dark background, i.e. a page-wide panel for every phone visitor; on desktop it needed.sidebar-md/.sidebar-sm, but that class is put on<html>by the anti-FOUC script straight fromlocalStorage- so it was enough for someone to have collapsed the sidebar on any other page once. In that mode the submenu is forced toposition: static, so its::beforeresolved against the initial containing block and painted a dark, click-eating rectangle across the whole page. The selectors are now scoped to.admin-sidebar- the drill-down is sidebar behaviour, not something every<details>on the page inherits. This affecteddocs-adminon molique.dev. .admin-rail- an optional second column in the admin panel. Between the sidebar and the content, for sub-navigation, filters or a list of records. Deliberately without a background: it sits on--bg-body, so in floating mode it reads as the ground between two cards rather than a third card. The grid track is added by a:has()rule and only once the element exists - an empty track would generate a SECONDgapin floating mode and shift the layout of every page not using a rail. This also surfaced that.admin-main.fade-bottomcomputed the column position with its owncalc(), so a third column would have silently misaligned the bottom gradient; the offset now lives in one variable,--main-offset, read by both the grid and the gradient. On mobile the grid collapses to one column, so the rail stacks ABOVE the content - it is not hidden, because silently losing content is undiagnosable;.admin-rail-hide-mobiledrops it deliberately.- Four popover menus were losing their anchor.
.dropdown-menu[popover]and.popover-contextposition themselves withanchor()but declared noposition-anchor, relying on the oldautodefault. The initial value today isnormal, andnormalbehaves asnoneunlessposition-areais in use. Soanchor()had no anchor at all: invalid at computed-value time,topfell back toauto, and the menu landed at its static position instead of under the button. Both now declareposition-anchor: autoexplicitly - as.select-search-menuand.custom-select-dropdownalready did. - The browser requirement is no longer unwritten. The implicit anchor between a
[popovertarget]button and its popover is Chrome/Edge 133+, while CSS Anchor Positioning itself is older (Chrome 125) - two separate things. The@supports not (top: anchor(bottom))fallback only detects the latter, so the Chrome/Edge 125-132 band fell through the gap:anchor()parses, the fallback does not fire, there is no anchor, and the menu opens in the wrong place. No CSS feature query can detect this, so the band is closed by a new module,js/modules/molique-popover-anchor.js, loaded automatically when such a menu is on the page: it gives the trigger an explicitanchor-nameand points the menu'sposition-anchorat it - exactly what.mega-menudoes in pure CSS, which it can only afford because it has a wrapper to scope one shared name to. The link is made on click and delegated fromdocument, so menus rendered later need no re-initialisation and a menu shared by several triggers anchors to the one actually used. Where the implicit anchor already works this changes nothing. Ananchor-name/position-anchoryou set yourself is respected. Net effect: with the JS the floor is Chrome/Edge 125+, CSS-only it stays at 133+ - both are now stated outright inREADME(PL/EN/DE), in the "Requirements and Compatibility" section (which listed four technologies and omitted the very one that sets the floor), inllms.txtand in the global dictionary. - Six animations that never ran. Two generic keyframe names existed in no built bundle and no chunk:
fadeInDown(.dropdown-menu,.custom-select-dropdown,.select-search-menu) andfadeIn(.radial-value,.feedback-invalid,.tab-pane). Six dead references: no effect, no warning - Sass compiles it, the browser ignores an unknown animation name, the console stays clean. Same root cause both times: a shared generic name with no owning component, while chunks are built PER COMPONENT, so such a keyframe lands in none of them. Each component now has its own keyframe named after it (dropdownMenuIn,customSelectDropdownIn,selectSearchMenuIn,chartValueIn,formFeedbackIn,tabPaneIn) - liketoastEnteroradminDrilldownPanelIn. Each also gained aprefers-reduced-motionguard. To prevent a third time there is nownpm run test:css: it walks all 82 stylesheets and fails when any animation references a@keyframesthat is not in THE SAME file - deliberately stricter than "somewhere in the project", because that property is exactly what makes a chunk usable standalone.
New The classes that were missing on a marketing page
.fw-semibold(600). The--fw-semiboldtoken existed from the start, the class did not - the scale jumped frommedium(500) straight tobold(700), exactly where the most common heading weight sits..order-*:.order-first,.order-last,.order-0–.order-5plus-md-and-lg-variants. Alternating sections used to force DOM reordering, which wrecked reading order on narrow screens and for screen readers.- Responsive Flexbox alignment:
.justify-content-md-*,.align-items-md-*,.align-self-md-*,.flex-md-wrap/.flex-md-nowrap. You could already flip the axis direction (.flex-md-row) but not the alignment along it. - Spacing aliases
s/e:.ps-*,.pe-*,.ms-*,.me-*- expanding to physical left/right, like.text-start. The side variants (.pt-,.pb-,.pl-,.pr-) had existed for a long time but were absent fromllms.txtand the class reference, which made it look like only.px-and.py-existed. They are documented now. .card-overflow-visible. The card clips its content (overflow: hidden) so images respect the rounded corners - and swallows anything meant to break the edge: a "Most popular" ribbon, a badge above the top edge, a dropdown withoutpopover. The variant also restores the corner rounding on a leading/trailingimg/picture- without that it would fix the ribbon and break the photo..data-row-compact-wrap..data-row-compacttruncates the title and details with an ellipsis. Right for a dense dashboard with fixed row heights, but the name and look suggest a generic list - you reach for it there and lose content with no signal. The variant turns wrapping on. The default stays as is for now, since flipping it would break existing dashboards; the swap (with.data-row-compact-truncateas the variant) belongs in a major release.- The anti-FOUC snippet ships in
starter.html. The docs required a synchronous script in<head>that the package never provided.
New Searching by the problem instead of the class name
- Table search now reads
data-tags. A row can carry words that are not visible in the table - the ones people type when they know their problem rather than the class name. In the class list this means "centre" finally returns.justify-content-*,.align-items-*,.translate-middle,.text-centerand.mx-auto, even though none of those names contains the word. - Tag matching is not a substring test, and cannot be. Polish and German inflect on the suffix, so the tag
wyśrodkowanieis NOT a substring of what someone actually types,wyśrodkować. Tags are therefore stored as stems (wysrodk) and a term matches when the stem is a prefix of it or the other way round. Diacritics are stripped on both sides, sowysrodkowacfrom a keyboard without Polish characters finds the same rows. Visible row text is still matched as an ordinary substring. - Hiding empty section headers never worked. The module queried
tr.cheat-sheet-category, but the class sits on the<td colspan>, not on the<tr>- the selector matched nothing, the whole block was dead code, and headers only disappeared by accident, because they were being filtered as if they were data rows. The documentation described behaviour that did not exist. A header is now a<tr>that CONTAINS such a cell, and it hides once nothing is left below it. - Empty state, result counter, keyboard shortcut. With zero matches the table used to go simply blank, with no explanation. Added:
data-search-status="#id"(a "12 of 181" counter),data-search-empty(custom text; the default follows the documentlang),data-search-hotkey="/"(focus the field - opt-in, because a framework has no business claiming a key on someone else's page, and ignored while the caret is in another field), Esc to clear, and a?q=URL parameter so a result can be linked. After adding rows from JS:MoliqueTableSearch.refresh(). - Visibility via
hidden, not an inline style. A consequence of the[hidden]fix in this same release - now that the attribute finally beats components that setdisplay, the module can use it instead ofstyle.display.
Fix The class list is generated from data - and four defects it surfaced
- One table instead of three maintained by hand. The class list was rewritten separately in Polish, English and German - and had already drifted. The content now lives in
tools/cheatsheet.data.js, andtools/gen-cheatsheet.jsassembles three partials from it (the way the variable tables already work). Class names exist ONCE in the data, shared across languages, so a translation physically cannot change them. - Three broken rows nobody could see. An orphaned
<tr><td>rendered an empty row in every language; the.rounded-circlerow in EN/DE had no opening tags of its own, so its content fell out of the table; and a ghost row with no class cell duplicated a background-colour entry. Browsers repair markup like that silently, so nothing complained. - Two rows were in the table twice.
.paginationand.breadcrumbeach had two full entries, in two different sections, with different descriptions - because the sections were called "Navigation and Admin" and "Navigation and Menus". - The coverage gate immediately caught documentation that lies. The generator compares entries against the compiled CSS.
.form-pill-groupis documented in three languages while only.form-pillexists. The classes.h1–.h6are in none of the eight bundles - only the element selectors are - so the promised "force a heading style on ordinary text" never worked, including that row's own demo. - The class list is finally COMPLETE - and keeps itself that way. 1287 classes across eight bundles, 373 rows, no gaps. The gate in the generator breaks the build when a class appears in the CSS with no entry OR when an entry points at a class that is gone. Before this, 692 classes were outside the table - whole components (carousel, lightbox, onboarding, tour, footer, testimonials), every colour variant, and the entire per-side spacing scale. Two thirds of the new descriptions come straight from the
docs-*reference pages, where they were already translated - which is why this did not cost 400 translations. - Categories rebuilt from 13 to 21. Two were called "Navigation", one ("Animations and Effects") had become a dumping ground for overlays, glass and gradients, and one had five entries for two modules. Section numbers are no longer typed into the content - the generator adds them, so inserting a section no longer means renumbering three files.
- Nested
-
v1.7.30August 2026
Fix Three bugs from real deployments: a colored button in
.input-group, dividers around POST actions, the onboarding footer-
A colored button vanished under the cursor inside
.input-group. The group forcedbackground-color: var(--card-bg-subtle)on hover at a higher specificity than the color variant, but never touchedcolor- so white label text landed on a light background. The neutral paint (gray border, subtle hover) now reaches ONLY a button with no color variant: the plain magnifier/arrow it was written for. The same gap had a second half, now closed too: the group's structural rules (corners, border overlap, stacking order) also reach a color class used without.btn- exactly what.btn-grouphad already fixed for itself. -
.with-dividerslost separators around actions wrapped in<form>. The divider was hidden by a:last-childrule on the button, but a POST action needs its own form (method + nonce) - so each button was often the only child of its own<form>, and the rule fired per form instead of per group. The divider now hangs off the group's direct child: the only element that always sits at a known position, whether it's the button or a wrapper. Hardly an edge case - an admin table with POST actions is the norm. -
The onboarding and tour footer pushed "Next" out of
the card. Nothing caps the number of slides, and
the dot row grew along with them. The failure was silent:
the button stayed in the DOM, clickable and in the tab
order, and the card is
overflow: hidden, so not even a scrollbar showed up. The footer now wraps (flex-wrap), the dots are the only part allowed to shrink, and the navigation never gives way. Past a threshold (8 slides, 6 tour steps) the dots disappear entirely and the visible "Step N of M" counter takes over - the same one that used to be screen-reader-only.
New
.admin-logo-swap, plus onboarding and tooltip width as variables-
A third sidebar logo strategy: next to
"hide it" (
.admin-logo-hide) and "shrink the same thing" (.admin-logo-compact) comes "show a different file"..admin-logo-swapon.admin-brandholds two images -.admin-logo-full(wordmark) and.admin-logo-mark(logomark) - and CSS picks one per width mode. A wordmark squeezed into 32px is unreadable, and a logomark is a separate asset, not a smaller rendering of the same one. Zero JS, no extra request when toggling. -
.text-leftand.text-rightas aliases of.text-start/.text-end- along with the responsive.text-md-left/.text-md-rightvariants. Markup pasted in from another project stops silently losing its alignment. The alias adds no RTL caveat: molique's logical names already resolve to physicalleft/rightrather thantext-align: start/end, so both spellings behave identically in every writing mode. Thestart/endspelling stays the recommendation for new markup. -
New variables
--onboarding-card-width(440px) and--tour-tooltip-width(320px). Changing the width used to mean overriding a rule from outside@layerand remembering the 768px media query - otherwise you'd undo the deliberate full-screen card on phones. The variable removes both the override and that trap: it doesn't reach the mobile branch, and the tooltip's viewport clamp stays in place whatever value you set. Both are set on:rootrather than inline - JS builds both panels, so there is no markup to put astyle=""on. The framework never declares them, it only reads them with the default in the fallback; a local declaration would beat inheritance and leave the variable unsettable.
-
A colored button vanished under the cursor inside
-
v1.7.29August 2026
Fix English fallback on regional language tags (e.g.
lang="pl-PL")-
Six modules (
molique-carousel.js,molique-onboarding.js,molique-sortable.js,molique-theme-editor.js,molique-tour.js,molique-lang-suggest.js) compareddocument.documentElement.langliterally against'pl'/'de'. molique.dev itself renderslang="pl", so the bug was invisible on the live site - but WordPress (and BCP 47 generally) often renders the full tag with a region, e.g.pl-PL, so every such install silently fell back to English (e.g. the screen-reader announcement after a reorder: "Item moved to position 1 of 10" instead of the localized text). Every module now strips the tag at the hyphen before looking up the dictionary:document.documentElement.lang.split('-')[0].
-
Six modules (
-
v1.7.28August 2026
New Sortable List: examples page and mega menu
-
A new Examples:
Sortable List page - navigation menu ordering and a
file list wrapped in
.data-row-compact. Linked from the "Components" mega menu (Tables & Data group) and the "New in the library" card.
-
A new Examples:
Sortable List page - navigation menu ordering and a
file list wrapped in
-
v1.7.27August 2026
Fix Sortable List: item drifted from the cursor, edge arrows
-
The dragged item drifted away from the cursor every
time it "hopped over" a neighbor -
translateYwas a running sum ofmovementY, and that sum had no way of knowing that swapping DOM order (insertBefore) changes the item's natural position, so the offset kept compounding with every swap.translateYis now recomputed from scratch on every pointer move, straight from the item's current natural position - the grabbed point stays exactly under the cursor no matter how many times the item has changed places in the DOM. -
The first list item now hides its "up" arrow, and
the last item hides its "down" arrow (instead of
just graying them out as
disabled) -visibility: hidden, so the other button in the pair doesn't shift sideways.
-
The dragged item drifted away from the cursor every
time it "hopped over" a neighbor -
-
v1.7.26August 2026
New Sortable List: drag + up/down buttons
-
<ul data-sortable>- reorder items via two equal, parallel paths: the.sortable-handle(Pointer Events, not native HTML5 Drag&Drop - which doesn't work on touch) anddata-sortable-up/-downbuttons (reusing.btn-action) - the only path for keyboard and screen-reader users. Neighboring items "make way" with a FLIP animation ontransform(GPU-only). After every change: aCustomEvent('sortable:update')with the new order (molique has no backend - persisting it is your app's job) and an announcement through a hiddenaria-live="polite". Zero JS config -js/modules/molique-sortable.jsloads itself. Full reference in the Admin docs.
-
-
v1.7.25August 2026
Fix Mega menu links weren't tappable on mobile
-
The invisible, full-screen "click outside to close"
cover (
.mega-menu[open] .mega-menu-trigger::before) wasn't scoped to desktop. On mobile, where.mega-menu-contentdegrades to an in-place accordion (position: static, no z-index of its own), that cover rendered ON TOP of the accordion's links and swallowed every tap - it landed on the<summary>instead and just collapsed the menu instead of opening the link. The cover is now scoped to@include mq(md), where the panel actually floats above the page.
-
The invisible, full-screen "click outside to close"
cover (
-
v1.7.24August 2026
New Buttons:
.btn-iconfor square/round buttons-
A new
.btn-iconmodifier (plus.btn-icon-sm/.btn-icon-lgvariants) - fixed width and height via a--btn-icon-sizevariable instead of padding, so an icon-only button becomes a perfect square with no juggling. Add.rounded-circlefor a circle. Manages its own touch target (like.carousel-dot) - on touch it grows to the full 44px regardless of the modifier, instead of being stretched into a tall pill by the shared buttonmin-heightrule.
-
A new
-
v1.7.23August 2026
New Theme Editor: WCAG contrast checker
-
The preview panel on the right of the Theme
Editor now shows live WCAG contrast (AAA/AA, and a
3:1 non-text tier) right next to real buttons, badges,
alerts, the table, the sidebar, and the code block - the
number always sits next to what it actually measures,
not next to an abstract color picker. Alerts correctly
compute their background as a 10% color tint blended
with the card surface (matching how
_alerts.scssrenders them), not as an opaque color read directly.
-
The preview panel on the right of the Theme
Editor now shows live WCAG contrast (AAA/AA, and a
3:1 non-text tier) right next to real buttons, badges,
alerts, the table, the sidebar, and the code block - the
number always sits next to what it actually measures,
not next to an abstract color picker. Alerts correctly
compute their background as a 10% color tint blended
with the card surface (matching how
-
v1.7.22August 2026
Fix Tooltips clipped by a card's
overflow: hidden-
Two new
.tooltip-elementvariants:.tooltip-element-bottom(opens the bubble downward instead of upward) and.tooltip-element-end(right-aligns instead of centering). Fixes the tooltip on the "Fonts" switch on the Download page, which was getting clipped by the card'soverflow: hidden- the trigger sat in a corner of.card-header, with no room either above it or to its right.
-
Two new
-
v1.7.21August 2026
New Onboarding: Onboarding Slides and Spotlight Tour
-
.onboarding-dialog- full-screen welcome slides (icon/image + title + description) on a native<dialog>. Declaratively viadata-onboarding/data-onboarding-slide(shows once per browser,localStorage) or imperatively viaMoliqueOnboarding.start(slides). -
.tour-dialog- a sequence of steps over real interface elements (highlight + tooltip). The highlighted element stays visible but isn't clickable - it usesshowModal()'s nativeinertbehavior, not apointer-eventstrick. The tooltip is positioned via CSS Anchor Positioning with a 5-way@position-tryfallback chain. Declaratively viadata-tourdirectly on elements, or imperatively viaMoliqueTour.start(steps). -
Both APIs return a
Promise- they can be chained:MoliqueOnboarding.start(slides).then(() => MoliqueTour.start(steps)). Full docs: Onboarding.
-
-
v1.7.20July 2026
Fix Dropdown Popover: button reset and safe positioning
-
.dropdown-itemas a<button>(the semantically correct choice for action items like "Delete"/"Edit" that aren't navigation) picked up the browser's native look - a gray background, a2px outsetborder,appearance: auto. The reset is now complete; existing<a class="dropdown-item">usage is unaffected (it already had these values). -
.dropdown-menu[popover]now ships a default set of three@position-tryfallbacks (flip vertically, flip horizontally, and flip both at once) - a menu opened near the bottom or right edge of the screen (the last table row, the last column in a card grid) now flips itself into a safe spot instead of spilling outside the viewport.
-
-
v1.7.19July 2026
Improvement Consistent punctuation: plain "-", never "–"/"—"
-
Across the whole repository (280 files - the PL/EN/DE
site, SCSS components, tooling, docs), en/em dashes
(
–/—) that had crept in over the years were replaced with one consistent character - the plain hyphen "-".
-
Across the whole repository (280 files - the PL/EN/DE
site, SCSS components, tooling, docs), en/em dashes
(
-
v1.7.18July 2026
New Email contact in the footer
-
A new "Get in touch" link next to the author's photo in
the footer. The address never appears anywhere in the
HTML source as ready-made
user@domaintext - the browser assembles the link from two separatedata-*attributes, so a static copy of the page doesn't expose it to simple address-scanning (no JS: a readable, manually-typeable "rafal [at] rozacki.com" in<noscript>).
-
A new "Get in touch" link next to the author's photo in
the footer. The address never appears anywhere in the
HTML source as ready-made
-
v1.7.17July 2026
Fix Missing cache-busting on JS files
-
js/molique-script.jsand the modules it loads dynamically (e.g. the theme editor) had a year-longCache-Controlon the server but no?v=...in the URL - unlike CSS. Result: a returning browser could keep an old JS file on disk for years and never see new features or fixes without a hard refresh (Ctrl+Shift+R). -
Every
<script>tag loadingmolique-script.jsnow carries?v=1.7.49, exactly like CSS already did; the module autoloader appends the same parameter to every file it loads.
-
-
v1.7.16July 2026
New Theme Editor: 4 ready-made color palettes
- A new "Ready-made palettes" section at the top of the editor - Modern Premium, Eco Sage, Warm Terra, Futuristic Cyber. One click sets Primary, Secondary, backgrounds, border, and text for both themes at once (instead of manually dragging 7 sliders). Success/ Danger/Warning/Info stay shared across all palettes.
-
Works exactly like the rest of the editor - the change
is visible only on this page (saved to your browser's
localStorage), exportable with the "Copy CSS" button. It doesn't change molique.dev's default theme.
-
v1.7.15July 2026
Fix New "Slate Violet" palette - success/danger/warning/info now pass 4.5:1 with no exceptions
-
The previous
--success/--danger/--warning/--infoonly worked as a background under dark text - as a standalone text color on a light background they gave a mere 2.3-3.8:1 (below the WCAG 4.5:1 threshold), hence the separate, second set of--success-textetc. The new colors are dark/saturated enough to pass 4.5:1 both ways at once - as text on a light background and as a background under white text - so the second set became redundant.--success-textand the rest stay in the code (dozens of places use them), but are now an alias to the base (--success-text: var(--success)) - zero changes outside_root.scss. -
New token
--semantic-fg: the old success/danger/warning/info were light/pastel in BOTH themes, so buttons/badges always used a hardcoded dark text color. The new ones are dark in light mode, but still light/neon in dark mode - the opposite rule depending on the theme.--semantic-fgswitches along with the theme (_buttons.scss,_badges.scss,.bg-successetc. in_colors.scss). -
Dark-mode
--dangerisn't 1:1 from the original palette proposal - the version with dark text gave 4.30:1 (AA-large only, not full AA). Picked a slightly lighter shade from the same family - 4.84:1. -
--primarystays in the same indigo/violet family as before (a minor hue tweak),--secondaryshifts to a neutral zinc gray with no blue tint.
-
The previous
-
v1.7.14July 2026
Fix
.stat-tile: icon landed above the text instead of beside it-
The cause wasn't in
.stat-tileitself, but in the cascade layers:_stat-tile.scsswrapped its own content in@layer components { ... }, even thoughmolique-style.scssalready wraps the entire component import in that same named layer - the extra wrapping inside created a nested sub-layer with lower priority than unwrapped rules in the same scope (including.card). The result:.card'sflex-direction: columnbeat.stat-tile'sflex-direction: row, regardless of order in the file. -
Fixed by removing the unnecessary wrapper - matching most
files in
components/(including.card,.tabs), which don't self-wrap. The icon now sits on the left with the text left-aligned beside it, exactly as documented.
-
The cause wasn't in
-
v1.7.13July 2026
Fix Silent
.admin-layoutoverflow on mobile-
A bare
1fringrid-template-columns(mobile, below 768px) is short forminmax(auto, 1fr)- the track's minimum is computed from its descendants' min-content, NOT from zero, even when.admin-mainalready hasmin-width: 0+overflow-x: hidden(a different mechanism from protecting the grid track itself from overflowing). If any descendant - at any depth - has a large intrinsic size, the track grows past the screen width. Becausehtml/bodydeliberately useoverflow-x: clip(notscroll- to avoid breakingposition: sticky), the result isn't a visible scrollbar, just content silently clipped past the edge of the screen. Fixed with an explicitminmax(0, 1fr). -
The same mechanism is now guarded in
.tabs-pilltoo: the tab columns'grid-template-columnsis nowrepeat(var(--tab-count), minmax(0, 1fr)), and labels truncate with an ellipsis instead of wrapping to two lines or overflowing the column when space runs out.
-
A bare
-
v1.7.12July 2026
Improvement Closing the loop on
.stat-tiledocs-
.stat-tile(v1.7.11) added tollms.txt- it was missing there despite being added to docs-cards and the cheat sheet; the AI Instructions page regenerates from that file automatically. -
An entry in the Roadmap:
size variants (
.stat-tile-sm) as an idea to consider later.
-
-
v1.7.11July 2026
New New component:
.stat-tile(KPI card)-
A metric tile: an icon with no colored background, a
label, a number that's always the same size (regardless
of the instance), and an optional trend delta
(
-up/-down). Pairs with.card-.stat-tileonly adds the internal layout. See Cards, section 5. -
Upstreamed from a real project (a CRM panel), where it
replaced hand-rolled KPI cards with inconsistent text
hierarchy across instances - a problem
.stat-tile-valuesolves once, at the component level, instead of letting it drift with every new tile.
-
A metric tile: an icon with no colored background, a
label, a number that's always the same size (regardless
of the instance), and an optional trend delta
(
-
v1.7.10July 2026
Fix
.tabs-pillstretched to the width of the tab content-
.tabsisflex-direction: columnwith defaultalign-items: stretch, so.tabs-header(the pill) and.tabs-contentalways had exactly the same width - the segmented toggle stretched to the full width of whatever it switched (e.g. a wide table) instead of staying compact. -
.tabs-pill .tabs-headergotalign-self: flex-startandwidth: fit-content- the pill now sizes to its labels, independent of how wide the tab content below it is..tabs-contentunchanged.
-
-
v1.7.9July 2026
Improvement JIT and CLI cards on the homepage updated
-
The "For Developers" section on the homepage showed
molique JITand the CLI as "In progress" (no link) - stale since the npm publish. The cards now show an "On npm" badge, copy matching the real functionality, and buttons linking to molique JIT and CLI molique-jit.
-
The "For Developers" section on the homepage showed
-
v1.7.8July 2026
New molique-jit published on npm + 8 make:* generators
-
The
molique-jitpackage is now available on npm (npm install --save-dev molique-jit) - the install-from-source instructions on the molique JIT and CLI molique-jit pages have been replaced with realnpm install/npxcommands. -
Scaffolding grew from one generator (Modal) to eight:
make:modal,make:layout,make:nav,make:table,make:chart,make:form,make:popover,make:widget- each with a Polish and German alias and a shared-n, --countflag to skip the "how many?" prompt.make:componentno longer generates a Modal - it now lists every available generator. -
Separately: the molique framework itself now has its own
npm package too (
npm install molique) - a distribution alongside the ready-made ZIP packages on the download page.
-
The
-
v1.7.7July 2026
Improvement molique JIT and CLI docs split into two pages
-
The
docs-jitpage (v1.7.6) has been split into molique JIT (the engine: comparison with PurgeCSS, how the lookup dictionary works) and a new CLI molique-jit page (installing from source,molique.config.mjs, the full command reference, themake:componentgenerator). -
Reason: the CLI is going to grow with more commands
(e.g.
make:table) - a dedicated reference page scales better than one, ever-longer page mixing two different topics. Both pages link to each other. - Links in the navbar's "Resources" menu and the docs sidebar updated to two separate entries.
-
The
-
v1.7.6July 2026
New molique JIT and CLI documentation (preview)
-
A new
docs-jitpage describing the JIT engine (a lookup dictionary instead of calculating CSS on the fly - see the comparison with PurgeCSS) and themolique-jitCLI: theinit/build/watchcommands with Polish and German aliases, themolique.config.mjsschema, and themake:componentgenerator for ready-made HTML blocks (today: Modal, in 3 variants). -
The page is marked Preview - the engine
and CLI work and have been verified in the repository, but
the
molique-jitpackage isn't published to npm yet. Until then, the docs describe installing from source. - Links added to the navbar's "Resources" menu and the docs sidebar ("Build & Optimization" section); the completed "Built-in Just-In-Time compiler" item was removed from the Roadmap.
-
A new
-
v1.7.5July 2026
Fix The mobile "More" drawer slid in under the navbar
-
The sidebar's mobile "More" drop-up
(
.admin-nav-dropdown-menu) calculated its max height only from the bottom of the screen (subtracting the bottom nav bar), without accounting for the fixed navbar at the top (--navbar-h). With a longer list (e.g. on docs pages), the drawer would extend up underneath the navbar, hiding its top items behind it - affecting every page that combines a navbar with a sidebar. Added the missingvar(--navbar-h)subtraction to themax-heightformula.
-
The sidebar's mobile "More" drop-up
(
-
v1.7.4July 2026
Fix The "Back" arrow pointed the wrong way
-
The "Back: [page]" button at the bottom of every docs
and examples page used the
ph-arrow-righticon instead ofph-arrow-left- the arrow pointed right ("forward"), even though the button takes you to the previous page. Fixed across all 231 occurrences (PL/EN/DE). The "Next step" button (already pointing right correctly) is unchanged.
Improvement Accessibility (WCAG) - complete, 100/100 on every page
-
Closing out the accessibility audit: missing
descriptions (
aria-label) on icon-only buttons (carousel dots fixed once inmolique-carousel.js- covers every carousel on the site), theme editor fields (fixed once inmolique-theme-editor.js, reads the description from the adjacent label), insufficient spacing between carousel dots (WCAG 2.5.8), a missing<main>onblog.html, and a few more spots where a vivid color (--success/--danger) was used directly as text color (table headers, struck-through pricing items, stat card trend indicators). - Result: all 90 pages on the site now score 100/100 on the Lighthouse Accessibility audit - zero remaining issues in any category.
-
The "Back: [page]" button at the bottom of every docs
and examples page used the
-
v1.7.3July 2026
Fix Heading hierarchy (WCAG) across the entire site
-
Continuing the previous accessibility audit: nearly every
examples-*.htmlpage jumped straight from<h1>to<h3>, skipping<h2>, anddocs-*.htmlpages had their tip/callout boxes marked as<h5>instead of<h3>- in both cases screen readers reported this as a broken document structure. -
Fixed across every page (PL/EN/DE), including the entire
history of
changelog.html(74 entries going back to v0.1.0, none of which shared a common<h2>until now) - zero visual changes, just correct tags. -
Along the way:
examples-admin-layout.htmlhad its own separate copy of the sidebar markup (with the same list-structure bug already fixed in the shared partials previously) and one un-underlined link inside an.alertnotice ondownload.html- both fixed.
-
Continuing the previous accessibility audit: nearly every
-
v1.7.2July 2026
New The site has moved to its permanent home, molique.dev
-
The entire site now runs on
molique.dev(same hosting). The old domainmolique.rozacki.comnow redirects automatically (301, preserving the full path) to the matching page on the new domain. -
Fixed a hidden build bug:
sitemap.xmlandrobots.txtwere never making it into the production build automatically (generated too late in the pipeline, AFTER the root files were already copied) - now generated before the build, alongside the rest of the root files.
New Live preview in the homepage hero
-
Instead of just a code block, the hero section now shows
a WORKING segmented control - clicking
SCSS / CSS / HTML shows, in turn, the
source snippet, the compiled CSS, and how to use it in
HTML, all for the same
.hover-springeffect visible on the "Get started now" button right next to it.
Fixes Accessibility (WCAG) across the whole site
-
Text contrast.
--success,--danger,--warningand--infoare light/pastel enough in both themes that using them as plain TEXT color (.text-successetc.) didn't have enough contrast - new, darkened--success-text/--danger-text/--warning-text/--info-textvariants fix this without changing how badges, buttons, or status dots look. -
Dark mode. Found and fixed a more
serious, hidden bug along the way:
.btn-warning/.badge-warninghad only 1.58:1 contrast in dark mode (the text color variable flipped along with the theme instead of staying fixed) - now a literal--btn-text-dark. - Links in body text. Links inside paragraphs, table cells, and list items without their own class now get an underline - color alone wasn't enough of a difference from the surrounding text.
-
Sidebar menu structure. The mobile
"More" dropdown in the docs/examples sidebar had invalid
list HTML (elements sitting directly inside a
<ul>instead of inside<li>) - fixed with no visual or behavioral change.
-
The entire site now runs on
-
v1.7.0July 2026
Fixes Keyboard-accessible tabs
-
.tab-inputhaddisplay: none- that doesn't just hide the element visually, it removes it from the tab order and the accessibility tree. Tabs couldn't be switched with the keyboard or read by a screen reader, even though the framework declares WCAG 2.2 AAA compliance. -
Hiding switched to the
cliptechnique - the same one.sr-onlyis built on. The element becomes invisible but stays focusable: the radio group regains native arrow-key support, and the focus ring lands on the visible.tab-label. -
Nothing in the markup changes - the same
.tabs/.tab-input/.tab-labelstructure, just fixed behavior underneath.
New Chart navigation (
.chart-nav)- A segmented range switcher built on hidden radio inputs - no JavaScript. The component was documented and used in example markup on three pages since the first release, but the CSS rule was never written; now it works.
-
Radios hidden with the
cliptechnique, notdisplay: none- same principle as the tabs fix above, so the group is keyboard-accessible right away.
New Fewer classes to write: implications in the grid and buttons
-
.grid-md-cols-*is a single-column grid by default below its breakpoint, soclass="grid-md-cols-12"is enough. Previously you had to addgrid-cols-1, and forgetting it caused a sneaky symptom: the layout looked fine, butgapstopped working on phones - the element wasn't a grid at all at that point. -
A button color class now implies
.btn-class="btn-primary"instead ofclass="btn btn-primary". This applies to colors and their outline variants. Size and base-look modifiers don't carry it (they're add-ons, not buttons), and.btn-actiondeliberately doesn't inherit it, since it intentionally breaks the 44px rule. -
Nothing stops working. The existing
class="btn btn-primary"andclass="grid-cols-1 grid-md-cols-12"notation is still valid - the new rules only add a default behavior. Cost: +740 B in the buttons module, +62 B in the grid.
Fixes The 404 page was unstyled
-
404.htmlloadedcss/flex-ui.css- a file left over from the framework's old name, gone for months. It also used two classes outside molique (.page-404-wrapper,.max-w-600) and a deadjs/script.js. Result: a completely unstyled page. - Rewritten using only molique classes, without a single line of custom CSS. It serves both as this site's own 404 page and as a template to copy - a comment at the top of the file lists what to swap, plus config for Apache and nginx.
Change Removed
.hover-text-primaryand.hover-bg-light-
They broke the naming scheme. In
molique, hover colors are named
WHAT-hover-COLOR:text-hover-primary,bg-hover-danger,border-hover-success. These two classes had their parts reversed and were the only ones like that in the whole framework. -
They were duplicates. The counterparts
.text-hover-primaryand.bg-hover-lightalready exist in the palette, and additionally have atransitionthat the removed versions lacked - so the migration is a minor improvement, not just tidying up. -
What to do: replace
hover-text-primarywithtext-hover-primary. The class.hover-bg-lightwasn't used anywhere in the project. The rest of thehover-*classes (.hover-scale,.hover-shadow,.hover-border-draw, and the rest) don't change - they describe an effect, not a color.
New CSS variables reference (
docs-variables.html)- All 148 variables in tables - 86 theme variables (with light and dark mode values), 56 component variables, and 6 markup-driven inputs. For each: what it controls and which SCSS modules use it.
-
The tables are generated by
tools/gen-variables-doc.jsstraight from_root.scss- the values can't drift from the code. The generator fails the build if a SCSS variable appears without a description, or a description is left after a variable was removed. -
A gotchas section: why
--darkturns light in dark mode, why--x-rgbonly works insidergba(), whyvariables: truein PurgeCSS wipes out the theme, and why you can't use--light-rgbin the sidebar.
Fixes
.bg-glasswithout a gradient, and a broken sidebar-
.bg-glasswasn't rendering its tint layer. The background referencedrgba(var(--bg-surface-rgb), …), and that variable was never declared anywhere - avar()with no fallback invalidates the whole declaration, so glassmorphism was running onbackdrop-filteralone. The variable was added to both themes. -
The docs sidebar extracted into a partial.
It was duplicated across 19 files and had already
drifted: six pages didn't link to the Class Reference or
the Roadmap, and
docs-tables.htmlwas missing from eighteen menus. Now there's a singlepartials/docs-sidebar.html, and the active item is set from the URL by a new module,js/modules/molique-admin-nav-active.js. -
Verified: after the swap, the content of
all 22 documentation pages outside the
sidebar is byte-for-byte identical, and while
fixing
.bg-glass, seven of the eight CSS bundles compiled with zero change whatsoever.
New Splitting SCSS into independent modules (start)
-
_navigation.scss(968 lines) split into 8 standalone files:_navbar,_mega-menu,_dropdown,_breadcrumbs,_pagination,_topbar,_scroll-to-top,_reading-progress. Each can be skipped in a bundle without compile errors - the first step toward the package builder and themolique-nanovariant from the roadmap. - Verified that nothing was lost: comparison of the compiled CSS before and after the split, at the selector→declaration pair level - 1771 pairs, zero lost, zero added, zero changed. The other bundles (admin, shop, blog…) are bit-for-bit identical.
-
Removed a modularity leak: a single
.is-activerule tied together the navbar, dropdown, and mega menu - so a bundle without the mega menu still contained an orphaned.mega-menu-link. Each component now has its own rule. -
New generator
tools/gen-scss-context.jsrebuilds_AI_CONTEXT_scss.mdfrom source - this file is a full SCSS dump, so it drifted from reality after every split.
Change All JS files prefixed with
molique--
Modules renamed:
js/modules/carousel.js→js/modules/molique-carousel.js(and similarly the other 16). The coremolique-script.jshad the prefix from day one. This lets scripts that sync the framework into a project overwrite only molique's own files, without touching user code. -
No changes needed in your code if you
use the autoloader - the paths live in
molique-script.jsand were updated. Change something only if you're loading a module manually via<script src>.
Fixes A dead script and asset discoverability
-
Removed a dead
js/molique-script-widgets.js- 7 pages were loading a file that isn't in the package (404 in the console). Widgets are pulled in by the autoloader anyway; the docs were fixed, since they instructed you to include this file. -
llms.txtand the safelist are now served from the site. Previously the build only copied asset directories, so/llms.txtreturned a 404 - and that's the exact address AI agents fetch it from. Links were also added to the "Resources" menu, a "For Developers" section on the home page, and "Shrink the Package" on the download page.
Fixes The Background Sync carousel wasn't changing background
-
The
data-bgattribute had been documented and present in example markup since the first release, but no line of JS ever read it -.carousel-bg-syncrendered with no background, despite ready-made CSS waiting for abackground-image. -
Fixed in
molique-carousel.js: the sameIntersectionObserverthat highlights the pagination dots now also sets the container's background to thedata-bgof the currently visible slide. -
Nothing in the markup changes - the
same, already-documented
data-bgattribute now actually works.
Fixes Lightbox: no keyboard navigation despite being documented
-
The docs claimed the lightbox "natively supports
keyboard navigation (arrows, ESC)" - in reality
molique-lightbox.jsdidn't have a singlekeydownlistener. A keyboard user who opened a photo had no way to close the modal. -
Fixed: Esc closes it, ←/→
switches photos. On open, focus moves to the close
button and returns to the clicked thumbnail on close -
standard modal behavior. Missing
aria-labels were also added to the navigation and close buttons.
Improvement Docs sidebar: collapsible categories + floating everywhere
-
~21 links in 8 categories took up too much
space - the docs sidebar was a long, flat list
that needed a lot of scrolling. Six categories (the
ones with 2+ items) are now collapsible branches
(
.admin-nav-submenu) - collapsed by default, except the one you're currently in. -
molique-admin-nav.jsnow opens the branch containing the current page itself on desktop (previously it only highlighted it) - keyboard navigation and mobile drill-down unchanged. -
.admin-layout-floating(until now only on the landing page and the Class Reference) is now on every documentation page - a consistent look throughout. - The Roadmap disappeared only from the docs tree - the component reference sidebar no longer links to it, since it's an announcements page, not API documentation. The page itself and the navbar/footer links are unchanged.
Fixes File Upload: choosing a file gave no confirmation at all
-
.file-uploadis an invisibleinput[type="file"]stretched over the whole card - clicking and native drag-and-drop worked, but there wasn't a single line of JS anywhere in the repo reacting to a selection. Result: after dropping a photo, nothing happened (not even the browser's "open in a new tab" fired - the input silently captured the file). -
Added
molique-file-upload.js: achangelistener overwrites (or appends, if it's missing from the markup).file-upload-namewith the selected file's name. -
The
.file-upload-animatedvariant didn't accept drag & drop (clicking still worked). The icon, heading, and caption had the samez-indexas the hidden input, and sat after it in the code - so they won the fight for which element receives the click exactly where you visually aim while dragging a file. Fixed withpointer-events: noneon those elements.
New Switch as a
.grid-expandtrigger-
A third, zero-JS trigger for smooth expanding:
.form-switch:has(.form-switch-input:checked) + .grid-expand. A common form pattern ("Send notifications?" → an email field) without a single line of JavaScript. -
The switch must be a sibling of
.grid-expand, not wrap it in the same<label>- otherwise clicking the revealed content also toggles the switch.
Fixes Sidebar and theme "jumped" on page reload
-
molique-themeandmolique-sidebar-statefromlocalStoragewere only read onDOMContentLoadedinmolique-script.js- i.e. AFTER the browser's first paint. A returning user with a collapsed sidebar (.sidebar-md/.sidebar-sm) or dark theme would therefore see the default state (full sidebar, light theme) for a split second before it switched. -
Fix: a small, synchronous inline
<script>right at the top of<head>, settingdata-themeand thesidebar-md/sidebar-smclass directly on<html>before the first paint, backed by mirrored CSS rules (:root.sidebar-md/:root.sidebar-sm) in_admin-layout.scss. -
The existing logic in
molique-script.js(switch click, writing tolocalStorage) was left unchanged - this fix is purely additive. Verified withmolique-script.jscompletely blocked: the page still renders correctly right away.
Fixes
<hr>disappeared in cards - looked like a dot-
molique never styled
<hr>- the element relied entirely on the browser's default style, which among other things centers it viamargin-inline: auto. As a direct child of any flex container (most often.card-body, which has beenflex-direction: columnfrom the start), those cross-axis auto-margins take priority overalign-items: stretchand "eat" all the free space - the line shrank to nearly zero width, showing up as a single dot in the middle of the card. -
Fixed by adding a base style in
_base.scss:width: 100%,margin-inline: 0,border-top: 1px solid var(--border-color). Zero auto-margins, so the problem disappears in every context - not just in cards. -
The same bug had already been patched once,
locally, in
.modal-divider- this fix generalizes it to every<hr>in the project, without touching any markup.
Fixes
.form-floatingdoubled its spacing in a card-
.form-floatinghas its ownmargin-bottom(needed when several fields sit directly in a plain block without a flex wrapper). But.card-bodyhas agapby default - as its direct child, a field got the spacing twice (gap + its own margin), so the distance to the next field/button was double what it was between other elements in the same card. -
Fixed with the rule
.card-body > .form-floating { margin-bottom: 0; }- outside.card-body, the margin behaves exactly as before.
New Full-bleed on mobile (
.breakout-mobile)-
A new utility class: pulls an element out of
.container's padding on mobile (below 768px), all the way to the screen edge - a typical case is a carousel, an image gallery, or a hero photo inside an article's body that should touch the phone's edges while the rest of the content keeps a normal margin. No effect on desktop. -
The "viewport centering" technique
(
width: 100vw+margin-left: 50%+translateX(-50%)) works regardless of the parent's actual padding value - you don't need to know or calculate it. The global guardoverflow-x: cliponhtml(present in molique from the start) prevents the horizontal scroll that100vwusually triggers when a scrollbar is visible. -
Requires a direct parent centered in the
viewport (like
.container) - it works correctly as its direct child, but nested deeper (e.g. inside.card-body) it's calculated against the card's width, not the viewport's, and ends up shifted/clipped. Documented as gotcha #5 ondocs-layout.html.
Improvement Roadmap trimmed of items completed along the way
-
8 ideas were completed along the way,
as part of other work, and were removed from the list -
including the entire "Architecture and Distribution"
category (
molique-nanoas a builder preset, a full system of independent SCSS chunks), a universal.position-sticky, pill-style checkboxes/radios (.selection-tile), a typing text animation (.typewriter), CSS masking (mask-image/clip-path, already widely used), and a circular progress bar and gradient under the area chart's line (both in.chart-radial/.chart-area). -
6 more items were clarified, since they
turned out to be partially done - the description
changed from "build X from scratch" to what's actually
missing (e.g. a real checklist with checkable items
instead of decorative icons in
.list-icons, hooking up.file-upload-animatedto the shared.hover-border-*library, which already exists). -
The stats at the top of the page were updated (32 ideas
in 10 categories, down from 41/11), an audit was done
item by item against the real state of
css/scss/andjs/, not from memory.
New i18n: EN/DE pilot for this page
-
The language switcher in the navbar stopped
being decorative - until now, the links in
.language-switch-menuwerehref="#". Now the landing page and "Getting Started" have real English and German versions, and the switcher navigates between them. -
A flat suffix convention, not
subfolders:
docs.html(Polish, default),docs.en.html,docs.de.html. Subfolders (/en/) would break every relative path across the whole site (base: './'); suffixes break nothing, and Vite already auto-detects every.htmlinsrc/as a separate build entry. -
Zero per-page manual config:
vite.config.jsfigures out, from the filename alone (computeI18nLocals), which language variants exist on disk, and injects ready-made variables (__hasEn,__altEn…) into all<include>s of a page at once -head.html(hreflang) andnavbar.html(the switcher) use the same, once-computed data. -
Graceful degradation for the remaining
~86 untranslated pages: the switcher shows only Polish
(the English/German entry disappears instead of leading
to a 404), and the
hreflangtags in<head>only include the variants that exist, plusx-default. -
A gotcha caught before the commit:
posthtml-expressionsinterpolates every{{ }}in the document in a single pass, before removing<if>branches with a false condition - anullvalue for a missing translation crashed the whole build (ReferenceError), even though<if>would have hidden it anyway. Fixed with a fallback to the Polish page instead ofnull.
New i18n: 19 of 21
docs-*.htmlpages in English and German-
Continuing the pilot - using the same
mechanism and conventions as above, another 19
reference pages were translated:
docs-variables,docs-select,docs-widgets,docs-blog,docs-roadmap,docs-purgecss,docs-cards,docs-typography,docs-sections,docs-animations,docs-tables,docs-forms,docs-eshop,docs-charts,docs-admin,docs-layout,docs-components-extra,docs-buttons,docs-interactive. Deliberately deferred:docs-navbar.html(1072 lines) anddocs-classes.html(2325 lines) - two pages clearly bigger than the rest combined. -
docs-variables.htmlas a special case: its three variable tables are auto-generated bytools/gen-variables-doc.jsand rebuilt before every build - manually translating their content would get silently overwritten. The page's static prose was translated normally; the three generated<include>s stay in Polish, with a note explaining why. -
Docs sidebar updated:
docs-sidebar.en.html/.de.htmlnow link to the translated variants everywhere except the two deferred pages - the fallback to the Polish version, where a translation doesn't exist yet, stays documented with a comment in the files.
New i18n: complete - all 22
docs-*.htmlpages in English and German-
The two last, previously deferred pages
finished:
docs-navbar.html(1072 lines, no deviation from the pattern) anddocs-classes.html(2325 lines, a huge CSS class cheat-sheet table across 13 categories). The framework's entire reference documentation now has a complete set of language versions. -
docs-classes.htmlhas a different structure than the rest of the docs - it's the only one that doesn't includepartials/navbar.html, so it has no language switcher in the top bar; kept identical in PL/EN/DE, this is a pre-existing feature of the page from before i18n, not something to fix. Translation covered only the descriptive content of table cells and the text in live component previews - CSS class names (.btn-primaryetc.) and the code in<code>were left unchanged, same as everywhere else in the docs. -
Docs sidebar closed out: the last two
links in
docs-sidebar.en.html/.de.html, which deliberately pointed to the Polish pages, were switched to.en.html/.de.html- zero deliberate exceptions left, the entire sidebar now links in the page's own language.
New License page (
docs-license.html)-
The full Apache License 2.0 text in a readable form,
plus a short
NOTICEsummary at the top. Available in Polish, English, and German. - The license text itself stays in English on all three versions - it's the only legally binding form; an unofficial translation could introduce ambiguity. Only the page chrome (title, intro, navigation buttons) is translated.
New AI Instructions in English and German
-
docs-llms.html(the human-readable version ofllms.txt) now has a full set of language versions, matching the rest of the reference docs.
Change Pretty URLs across the whole site
-
Every internal link dropped
.html(docs.html→docs, the homepage →/) - 2,310 links across 270 files, rewritten by a one-off script,tools/migrate-pretty-urls.js. The server (.htaccess) already supported this from an earlier release; the site just wasn't using it yet. -
A trap along the way: hreflang in
<head>is a<link>tag, and Vite scanshrefon every<link>as an asset reference (unlike<a>, which it ignores) - the first pass, withhref="./"for the homepage, tried to read thesrc/directory as a file and crashed the entire build. -
sitemap.xmlandrobots.txtnow carry the real production domain (not a placeholder) and cover every PL/EN/DE page - generated by a newtools/gen-sitemap.js, run automatically after every build.
Fixes CSS variables instead of hardcoded values
-
Full-screen overlays (lightbox,
offcanvas, popover) got a shared
--backdrop-rgb- but only as a color source, not one shared opacity. Each component had a deliberately different value (0.95 / 0.5 / 0.6); forcing one shared value would have genuinely changed how the lightbox looks. -
The footer got local
--footer-muted-rgb/--footer-white-rgb- not the global--light-rgb, since that one flips in dark mode while the footer is always dark. -
Spacing and radii in pagination, the pricing list,
pill tabs, the carousel, the admin sidebar, and the
code preview now compute from
--spacing-unit/--border-radius- no visual change (same resulting values). -
New transition-speed tokens
(
--transition-speed-fast/-slow/-slower/-chart) instead of individual numbers scattered across components. While at it,_accordion.scssand_charts.scssalso gainedprefers-reduced-motionsupport, which they didn't have at all before.
New Configurable download (
download.html)-
The Production package used to bundle both full and
minified CSS at once - 425 KB of dead weight for
anyone who only needed one. Now you pick the format (a
.tabs-pillsegmented control) and optionally the fonts (a.form-switchin the card header) - the default package dropped from ~363 KB to ~90 KB. -
Six static variants built by an extended
tools/build-packages.ps1, switched client-side with zero new JS dependencies.
Change Lightbox on a native
<dialog>-
A real accessibility gap: the old
version, built on a manually controlled
<div>, didn't trap focus - pressing Tab could take you out of the open lightbox and onto the page behind it. NativeshowModal()/close()handles that (plus restoring focus to the trigger element and closing on Escape) automatically. -
::backdrop+@starting-styleinstead of manually toggling classes and asetTimeout(10ms)hack to force a reflow before the fade-in. -
View Transitions API for the image-swap
animation - tried, then reverted. In testing,
document.startViewTransition()'sfinishedpromise could simply never settle, and a subsequent call after that happened would stop firing its callback at all - a real risk of permanently freezing the gallery's arrows. Reverted to a manualtransform/opacityanimation with a time-based throttle (always self-releasing), and addedprefers-reduced-motionsupport, which was missing before. - Adjacent gallery images are now preloaded in the background, so arrows and swipe feel instant.
-
-
v1.7.1July 2026
Fix
.table-cardson mobile - text wrapping into single letters-
A cell with "rich" content (several
<code>tags at once, a longer description) in the card variant useddisplay: flex- every child element became its OWN flex item, and instead of wrapping as one paragraph when space ran out, each one individually shrank toward zero width: the text broke into single letters. -
The label (
data-label) is back to plaindisplay: blockABOVE the value (via::before) instead of beside it via flex - plain block-flow is immune to this issue regardless of how many inline elements the cell's value contains.
New Code comments in EN/DE packages now translated
-
Packages downloaded from
download.en.htmlanddownload.de.htmlshipped the exact same files as the Polish site - comments in.scss/.css/.jsstayed in Polish regardless of the page language the user came from. -
Fix: one source of truth (the repo code, unchanged) + a
translation dictionary (
tools/i18n-comments/, ~1,050 unique phrases translated to EN and DE) + comment text substitution in a temporary copy, applied only when the ZIP is packaged bytools/build-packages.ps1. Code, CSS classes, variables, and file names stay untouched in every language - only the surrounding prose is translated. -
18 packages instead of 6 (language × CSS format × fonts).
download.jspicks the right variant based on the page's<html lang>.
New Version number from a single source of truth
-
The version number kept getting lost at release time -
typed by hand in a dozen-plus places (pages,
download.js,build-packages.ps1, the README). Now the only source is theversionfield inpackage.json. -
HTML pages get
{{ __version }}(an extraposthtml-expressionspass over the whole document invite.config.js, not just inside partials), JS gets the__MOLIQUE_VERSION__constant injected by Vite, andbuild-packages.ps1plus the newtools/sync-version.js(README.md, wired intopredev/prebuild) read the same field.
Roadmap Built-in Just-In-Time compiler
-
New idea on the list: a JIT engine scanning real markup
for classes actually used from the
@layer utilitieslayer, emitting only the needed combinations from the Sass maps instead of the full set + PurgeCSS. Details on the roadmap page.
-
A cell with "rich" content (several
-
v1.6.2July 2026
New Navbar "Pill" (
.navbar-pill)-
A third navbar variant: navigation as a
pill floating off the edge, sitting on
top of the content - so the hero photo starts
right from the top of the page, instead of below the
bar. Once scrolled (
.is-scrolledfrom JS), the pill unfolds into a regular bar at the edge and returns to the theme colors. -
Six variables - separate for each state:
--navbar-pill-bg/--navbar-pill-color/--navbar-pill-padding-xover the hero, and their-scrolled-suffixed variants after scrolling. Separate, rather than overriding the base one - since an inline style (the way they're set) beats a class rule and would block the other state. -
The pill's default background is a
literal, not
var(--dark)- that variable lightens in dark mode, so a pill sitting over a photo would turn white and the white text would vanish. After scrolling, the defaults are the normal theme colors. -
Fixed a misleading example:
docs-navbar.htmlandexamples-navbar.htmlshowednavbar-transparent navbar-stickytogether - andstickywins the cascade and returns to the document flow, which made the overlay effect disappear. Snippets fixed + a note about pushing the content down byvar(--navbar-h).
New PurgeCSS support - a ready-made safelist
-
New file
purgecss.safelist.cjsin the package - a ready-made safelist of classes PurgeCSS can't see, because JS adds them at runtime (.is-*states, carousel, lightbox, and toast markup). Usage:safelist: molique.runtime. -
A second level for dynamic names:
molique.merge('status','grid')for projects where the backend assembles class names (e.g.badge-<?= $status ?>). Groups:colors,grid,spacing,status. -
A generator instead of a hand-written list:
tools/gen-safelist.jsrebuilds the safelist from source (css/*.css+js/), so it won't drift when a new module is added. -
Verified with a real build: 277 KB →
68 KB (−75%) while keeping everything that JS adds. The
@layerdeclaration (cascade order) survives purging - the layer architecture is safe. - New subpage docs-purgecss.html: step-by-step instructions (install → configure → verify), ready-made configs for plain HTML, Vite and WordPress, a safelist-group table, and troubleshooting for the most common symptoms.
Fixes Accordion and toasts
-
Accordion: no scrolling once expanded.
.accordion-item::details-contenthasoverflow: hiddenby default (part of theheight: 0 → autoanimation trick). The[open]state only overrode the height, so when the content was taller than the height computed by the animation, it stayed permanently clipped - and a scrollable parent (overflow-y: auto) couldn't tell there was anything to scroll. Now[open]removes the clipping, but only after the animation finishes (overflow 0s 0.3s allow-discrete) - otherwise the content would spill outside the growing box and overlap its neighbors. On collapse, the clipping returns immediately. -
MoliqueToastno longer builds class names from a template (toast-${type}) - it uses a literal map instead. This makes every toast class visible to PurgeCSS and tooling, and an unknowntype/positiongets a safe fallback instead of an unstyled class. Behavior unchanged (verified: 4 types × 6 positions).
-
A third navbar variant: navigation as a
pill floating off the edge, sitting on
top of the content - so the hero photo starts
right from the top of the page, instead of below the
bar. Once scrolled (
-
v1.6.1July 2026
New Active item in the navbar (auto from the URL)
-
New module
js/modules/molique-navbar-active.js(auto-loaded when.navbar-menuis present): reads the URL and adds the.is-activeclass to the current page's link, as well as to the trigger of the dropdown/mega-menu it lives inside. The highlight style (primary color + heavier weight) is incomponents/_navigation.scss. - A shared navbar with no manual marking: you don't write the active state into the markup - one navbar shared across pages, with the current item derived from the address. When a page appears in several menus, all its occurrences get highlighted. Zero dependencies, zero jQuery.
Fixes Release cleanup
-
Unified sourcemaps: all CSS bundles now
compile without
--source-map- no moresourceMappingURLfooters pointing at nonexistent.mapfiles (previously inconsistent between bundles).
-
New module
-
v1.6.0July 2026
New Theme Editor - a live CSS variable editor
-
New page
theme-editor.html:
an interactive tool for controlling the theme live -
colors (with automatic sync of the
-rgbpairs and-hoverdarkening), surfaces, sidebar, border radius, spacing, focus ring, and base text size. Controls on the left, a live component preview on the right. -
Correct light/dark handling: changes
are written to a
<style>tag (not inline), so you edit the active theme separately - the palette goes to:rootor[data-theme="dark"], while "always dark" variables (sidebar) and dimensions always go to:root. "Copy CSS" exports ready-to-paste blocks; state is kept inlocalStorage, and there's also a Reset. -
Architecture: the module
js/modules/molique-theme-editor.js(auto-loaded after.theme-editor), chrome styling incomponents/_theme-editor.scss(docs bundle). Control config lives indata-te-*attributes - zero dependencies, zero jQuery. -
Default button hover: new classes
.btn-hover-spring/.btn-hover-lift/.btn-hover-glowon<body>give a shared hover effect to every.btn(buttons with their ownhover-*class take priority). Also selectable in the theme editor (Buttons section). GPU: transform/box-shadow, respectingprefers-reduced-motion.
Fixes Module autoloader + searchable select
-
Modules now load from an absolute address:
the autoloader was including modules via a relative
path (
modules/x.js), which resolved against the current page's address, notmolique-script.js's - on subpages (e.g./clock/) this caused 404s. The base is now computed fromdocument.currentScript.src. The bug had been in the repo since the first commit; spotted by a user embedding molique in their own plugin. -
Searchable Select on event delegation:
select.jsnow handles options added to the DOM after the page loads (e.g. via AJAX), the hidden input gets achangeevent on selection, and a new API,MoliqueSelectSearch.setValue(hiddenInput, value), sets the value from JS. Full backward compatibility (Popover API + the old<details>).
New Download subpage + downloadable packages
-
Two packages:
download.html offers
Production (compiled min+full CSS, JS with the
autoloader, fonts, flags,
starter.html) and Source (everything in Production + thecss/scss/sources for your own compile). -
A packaging script:
tools/build-packages.ps1minifies the bundles (sass --style=compressed) and builds both ZIPs intodist/. Also added:README.md,starter.html,LICENSE, andNOTICE. -
Apache 2.0 license (Copyright 2026
Rafał Różacki) - full text in
LICENSE, attribution inNOTICE. -
Fonts restored: the
@font-facerules (Inter + Poppins) had gone missing somewhere along the way - the site was falling back tosystem-ui. They're back as_fonts.scss, built intomolique-style.css(font-display: swap;fonts/folder next tocss/).
Improvement Global navbar on every subpage
-
Consistent navigation everywhere: the
same top navbar (light/dark
<picture>logo, mega-menu, language switch, theme toggle) now appears on every documentation and examples page - previously they only had the left sidebar. The admin layout's sidebar now sits BELOW the navbar (the same pattern as Bootstrap's docs). -
CSS coordination: a new
--navbar-hvariable; when a navbar sits above.admin-layout(body:has(> .navbar)), the sidebar starts below it and fills the rest of the window, and the navbar doesn't hide on scroll (otherwise it would reveal an empty bar). Also fixed the logo onindex.html(text →picture). -
Layout overhaul (everything in a single row):
Blog moved into the Examples dropdown,
Documentation/Changelog/Roadmap grouped into the
Resources dropdown, a Download molique
button (
download.html) withhover-spring, and the language and theme switches arranged vertically next to each other. The same navbar refreshed across all ~82 pages.
Breaking Change New typography scale - the base text is now .text-3
-
The middle of the scale shifted: the
base (paragraph) size is now
.text-3, not.text-1. Below the base sit.text-1(12px) and.text-2(13px) - for metadata, timeline dates, and captions..text-4–.text-8correspond to headings H5–H1, and.text-9–.text-12are hero sizes (up to 9rem). -
Microcopy: the classes
.text-sm(11px) and.text-xs(10px) are now smaller than.text-1- for captions and legal fine print. The--text-sm/--text-xstokens used internally by components stayed unchanged (13/12px). -
Migrating existing HTML: classes shift
up by two steps - the old
.text-1is the new.text-3, the old.text-4is the new.text-6, and so on; the old.text-sm→.text-2, the old.text-xs→.text-1. Every documentation and examples subpage was remapped automatically, so their appearance didn't change. -
Documentation: the class reference was
updated (including the previously missing
.col-start-*/.offset-*offsets), the Typography pages (docs + examples), and thellms.txtandmolique.mddictionaries.
New Fade Bottom - content fading at the bottom edge
-
The
.fade-bottomclass: a gradient covering the bottom edge of a scrollable container - content "fades out" instead of being sharply cut off. Color via--fade-color(defaults to--bg-surface), height via--fade-height(80px). The effect used to exist as a hardcoded fragment of an unloaded_admin.scssfile - it's now back as an official, optional class available for any element. -
Admin integrations: on
.admin-sidebar, the gradient automatically picks up the sidebar's background color and disables itself on mobile (Bottom Nav); on.admin-main, a fixed variant aligned to the content column works via layout variables (supports.admin-layout-floatingmode). Demo on the Admin Layout page.
Documentation Class reference completeness audit
-
Filled in the gaps in the cheat sheet:
the class reference got rows for previously
undocumented utilities - icon lists
(
.list-icons), background overlays (.overlay), hover colors (.bg-hover-*/.text-hover-*/.border-hover-*),.overlap-up-*,.align-self-*, positioning micro-utilities (.top-0….inset-0),.bg-image,.hover-scale/.hover-shadow,.filter-none. Component sub-parts (e.g..tab-pane,.step,.timeline-node,.pricing-header) are described alongside their parent elements. -
Fixed a hover class name error: the
cheat sheet incorrectly listed
.hover-bg-*/.hover-text-*instead of the correct.bg-hover-*/.text-hover-*- which meant the live example didn't work. Names and the demo fixed, dictionaries (llms.txt,molique.md) updated with all of the above.
Fixes Admin submenu as a mobile drill-down (with "Back")
-
Drill-down instead of a dead submenu:
until now
.admin-nav-submenuwas completely hidden on mobile (display: none) - in the horizontal bottom bar there was no way to expand it. Now clicking the trigger swaps the view to a full-screen panel: the<summary>becomes a Back bar at the top, and a link list fills the rest - identical to the drill-down in the-sm/-mdvariants. The "Back" transformation was extracted into a shared mixin (admin-drilldown-back), so desktop and mobile share one piece of code. The same markup works everywhere. -
New module
admin-nav.js: a bit of vanilla JS around the native<details>(auto-loaded after.admin-nav-submenu). Highlights the active item from the URL and its branch (.is-active) - without needing[open], which used to auto-open the panel on mobile as soon as you landed on a subpage. Additionally: mutual exclusion of open submenus, closing on Esc and on breakpoint changes. -
Enter/exit animation (touch feedback):
the panel slides in from the bottom with a slight
bounce (
cubic-bezierwith overshoot; the overshoot is masked by a solidbox-shadow, so the page doesn't flash), and the "Back" label appears with a slight delay. The exit (sliding back down) is handled by the module: native<details>hides content instantly, so JS adds an.is-closingclass, waits for the animation to finish, and only then removes[open]. Motion only ontransform/opacity(GPU), respectingprefers-reduced-motion. -
Clarified the "More" drop-up: the
dictionaries and class reference incorrectly suggested
the
.admin-nav-dropdownclass on<details>. In reality it's a separate pattern (Checkbox Hack:.mobile-more-toggle+.mobile-more-label+.admin-nav-dropdown-menu) - it's meant for bar overflow, not a nested submenu. -
The "More" drawer no longer slides under the
bar:
.admin-nav-dropdown-menuhad a hardcodedbottom: 70pxwithoutenv(safe-area-inset-bottom), so on phones with gesture navigation, the bottom items hid behind the bar (unreadable). It now uses the same formula as the bottom-sheet submenu (calc(70px + env(safe-area-inset-bottom))).
-
New page
theme-editor.html:
an interactive tool for controlling the theme live -
colors (with automatic sync of the
-
v1.5.1July 2026
New Selects and dropdowns on the Popover API (Top Layer)
-
No more clipping in modals: the
.select-searchand.custom-selectcomponents were rebuilt from<details>to the native Popover API + CSS Anchor Positioning. The menu renders in the browser's top layer - above an open<dialog>and outside containers withoverflow. Esc and clicking outside the menu close it natively (light dismiss), no JS. -
New markup:
<button popovertarget="ID">as the trigger + a menu with apopoverattribute and a uniqueid. The old<details>-based markup is still supported byselect.js(backward compatibility). -
Plain select: the search box
(
.select-search-input) is now officially optional - without it,.select-searchworks like a classic select. The docs got a new demo of a select opened inside a scrollable modal. -
Dropdown Popover: a new
.dropdown-menu[popover]variant - any existing button withpopovertarget="ID"opens a menu in the top layer, automatically anchored to the button (implicit anchor - no.dropdownwrapper and noanchor-nameneeded). The classic<details>-based variant remains recommended in the navbar. -
Language Switch + SVG flags: the
language switcher was moved to the popover variant, and
emoji flags were replaced with individual SVG files
(
img/flags/*.svgvia<img>) - emoji flags don't render on Windows (Chrome/Edge show letter pairs instead of flags). The folder only contains the languages offered in the project, and each file (~200 B) is cached once for the whole site. The active language's checkmark is now an SVG icon instead of a text character.
New Smooth theme switching (View Transitions)
-
GPU cross-fade: switching light/dark
now happens through
document.startViewTransition()- the browser cross-fades two page snapshots (pure opacity), without animating colors on individual elements. The transition duration is controlled by CSS (::view-transition-old/new), and older browsers plusprefers-reduced-motionswitch instantly, as before.
New Stock Bar - segmented stock level
-
New component
.stock-bar: a five-segment level indicator (stock levels, limits, quotas) in-success/-warning/-dangervariants. Zero JS and zero extra markup - the segments are drawn by an SVG mask, and the fill level is passed from the backend viastyle="--stock-filled: 3"(0-5). Empty segments are a tint of the variant color, correct in dark mode too.
Documentation Examples, SEO and dictionaries
- New example sections: a plain select without a search box, a select opened inside a scrollable modal, and a Dropdown Popover attached to any button.
-
SEO and AI:
sitemap.xmlgenerated from the real list of 81 subpages (previously template addresses), updatedllms.txtdictionaries and class reference.
Fixes Bugfixes
-
File Upload (animated): in the
.file-upload-animatedvariant, the invisibleinput[type="file"]had its positioning overridden (relativeinstead of the baseabsolute), which pulled it into the page layout and pushed the card's content down. The base.file-uploadvariant was unaffected. -
Admin panel dark mode: the sidebar's
light accents (logo, link hover, active submenu item,
dividers, scrollbar) were based on
--light/--light-rgb, which dark mode deliberately inverts - on the always-dark sidebar they turned dark and unreadable. The sidebar now has its own theme-independent variables (--sidebar-text-active,--sidebar-highlight-rgb). -
The "Back" button and modal closing: in
the narrow sidebar's drill-down mode, the "Back" button
(a transformed
<summary>) inherited its color from.is-active(--btn-text-light), which made it disappear on a dark background in dark mode - it now has an explicit color from the sidebar's palette. Additionally, the close button in a modal's header no longer shows a full focus ring right after the dialog opens (showModal()focuses it automatically) - the keyboard indicator remains, in a subtler form. -
Black headings in modals (dark mode): a
native
<dialog>getscolor: CanvasTextfrom the browser (black, absent a scheme declaration), which breaks color inheritance frombody- headings (color: inherit) turned black on a dark card. Modals and popovers now have an explicit theme color, and the framework declarescolor-scheme: light/dark- which also makes native scrollbars, form controls, and the date picker follow the theme. -
Mega Menu - "featured" card (dark mode):
the background gradient used
--dark/--primary, which invert in dark mode, so in the dark theme it turned nearly white under white text. The card is intentionally always dark (like the sidebar), so the gradient is now built on fixed colors. -
An "always dark" surfaces audit (dark
mode): the same family of bugs as above -
inverted
var(--dark)under light text - fixed en masse in:.overlay-dark(the hero overlay was lightening instead of darkening),.bg-dark(footers with.text-whitelost contrast),.bg-gradient-corners(a glow on a light background), and.scroll-to-top(the icon vanished on hover; its color now follows the theme like in.btn-primary). -
Modal backdrops (dark mode): the
darkening behind an open
<dialog>used an inverted--dark-rgband turned into a light haze in dark mode. The backdrop now uses a fixed, dark color in both themes. -
Product card (dark mode):
.product-image-wrapperhad a literal white background - on a dark card that made a jarring block, showing through semi-transparent placeholders too (e.g.--card-bg-subtle). The background now follows the theme (var(--bg-surface); in light mode it's still pure white). -
Number input without a native spinner:
the system's
input[type="number"]arrows doubled up with the+/-buttons of the.qty-inputcontrol (only the.qty-valclass hid them). The spinner is now hidden for every number input inside.qty-input, and globally forinput[type="number"].input- stepping is handled by the buttons, the keyboard (up/down), and the scroll wheel. -
Data Rows and contrast on primary (dark
mode):
.data-rowhad a literal white background (nowvar(--bg-surface)- unchanged in light mode), and the carousel arrows and the active.list-group-itemused a literal#fffagainst--primary, which lightens in dark mode - the text color now follows the theme like in.btn-primary.
-
No more clipping in modals: the
-
v1.5.0July 2026
Rebrand r-style → molique
-
A new brand: a complete renaming of the
framework to prepare it for its public debut - the
files
r-style.css/r-script.jsand their module variants (blog, shop, contact, speed dial, share, before/after) were replaced with a consistentmolique-style*.cssandmolique-script.jsfamily. - Repository cleanup: removed the outdated distribution package and orphaned files based on the old brand, no longer imported by any subpage.
Architecture Modular Sass in @layer layers
-
Explicit layer order: the main file
molique-style.scssnow defines an explicit@layer reset, base, layout, components, modules, utilitiesorder and pulls in individual partials viasass:meta.load-css()- zero accidental specificity conflicts. -
Split into topical folders: components
were broken up into
components/(cards, navigation, modals, forms, charts, dashboard, feedback),layout/(the admin panel layout), andutilities/(typography, colors, spacing, borders, animations) - easier to find and override a single style fragment. -
Separate bundles per module: shop,
blog, admin panel, and documentation now compile into
independent files
(
molique-style-shop.css,-blog.css,-admin.css,-docs.css) - you enqueue viawp_enqueue_styleonly what a given subpage actually needs.
New JS autoloader expansion
-
10 new micro-modules loaded
asynchronously from
js/modules/only when their component exists on the page:carousel,context-menu,counters,filters,lightbox,parallax,select,shop,table-search, andtext-effects. -
Refreshed widgets: a review and minor
fixes in the existing modules
before-after.js,magnetic.js,share.js, andtilt.js.
Documentation Split into topical subpages
- One subpage = one topic: instead of a single, long document, the docs were split into separate pages (Layout, Navigation, Sections, Typography, Buttons, Cards, Interactions, Carousels and Lightbox, Charts, Forms, Select, Animations, Widgets, Store, Blog, Admin Panel, Class Reference) - faster loading and easier navigation.
-
New Roadmap page
(
docs-roadmap.html) - the framework's public development plan as a timeline, including Container Queries, native<picture>, PurgeCSS, and a custom CLI.
Infrastructure Production, SEO and performance
-
Production files: added
manifest.json(PWA),robots.txt,sitemap.xml, and.htaccessrules. -
Visibility for AI: added
llms.txtto help language models find and correctly interpret the documentation. -
Local fonts: Inter and Poppins are now
hosted locally in the
fonts/folder and loaded via<link rel="preload">instead of an external CDN - faster first render and no dependency on external servers.
-
A new brand: a complete renaming of the
framework to prepare it for its public debut - the
files
-
v1.2.0June 2026
Architecture Smart JS Autoloader
-
DOM-based Lazy Loading: the monolithic
JS file was split into a dozen or so micro-modules (in
the
js/modules/folder). The main script scans the page and asynchronously pulls in only the scripts whose components are physically present in the HTML. -
Local variables: implemented dynamic
computation of negative margins for grouped buttons and
forms, based on the
--btn-border-widthvariable.
New Data Viz & Advanced UI
-
Charts (Data Viz): added the
_charts.scssmodule with charts built on Progressive Enhancement (Sparklines, a Radial Bar with CSS Houdini, Heatmaps, an SVG Area Chart, and a Donut Chart). -
Advanced Inputs: implemented dedicated,
visually consistent styles for
type="range"(with a filled track),type="color", andtype="date". -
Grouped Elements: added support for
.btn-groupand.input-groupwith perfectly overlapping borders. -
Interactive Icons: added the
.status-icon-togglecomponent (a Plus → Checkmark animation), which can also function as a fully native form checkbox.
Fixes Bugfixes & UX
-
Grid Blowout: resolved a grid-breaking
issue on mobile devices by globally forcing
min-width: 0on grid children. -
Lightbox Pointer Events: replaced touch
events with universal
pointerdown/up, allowing photos to be "swiped" using a mouse on desktop as well. - Mega Menu: added an "invisible bridge" (pseudo-element) preventing the menu from closing while moving the cursor down away from a link.
- Mobile Bottom Nav: rebuilt the admin panel's mobile sidebar into a modern, horizontal navigation bar pinned to the bottom of the screen.
Documentation A Complete Handbook
- Expanded the documentation to 14 topical subpages.
- Added instructional blocks (Pro Tips, Requirements, Options) to every component, explaining the architecture and implementation best practices.
-
DOM-based Lazy Loading: the monolithic
JS file was split into a dozen or so micro-modules (in
the
-
v1.1.0June 2026
New Data Viz & Charts
- Progressive Enhancement: implemented a charts module (Sparklines, Radial Bar, Heatmap, Area Chart) built 100% on plain CSS/SVG. Charts load instantly, preventing CLS, and can optionally be overridden by JS libraries.
-
CSS Variables: chart data is passed
safely from the backend via the
style="--val: X%;"attribute.
Expansion Modules and Widgets
- E-commerce & Blog: added complete, independent modules for stores (Star Ratings on SVG masks, Swatches, Grid/List toggle) and blogs (Post Cards, Author Box).
- Widgets (Opt-in): implemented independent scripts and styles for: Before/After Slider, Speed Dial, Magnetic Buttons, and the Web Share API.
- GPU Microinteractions: added advanced text effects (Color Wipe, Animated Underline) and interactive status icons (Plus → Checkmark) working as native checkboxes.
Documentation A Complete Handbook
- Created 12 new documentation subpages with interactive demos, instructional blocks, and a copy-to-clipboard feature.
-
The docs use the
admin-layoutmodule with a responsive sidebar (Bottom Nav on mobile).
-
v1.0.0May 2026
Revolution The molique 2026 Architecture
-
Zero JS for UI: complete removal of
JavaScript from Accordions, Tabs, Dropdowns, and
Modals. A move to native
<details>,<dialog>tags, and the powerful CSS:has()selector. -
Smart Grid (RAM): replaced the old
Flexbox (
.row,.col-*) with native CSS Grid. The new.grid-autoclass arranges elements automatically without Media Queries. -
Fluid Typography: implemented
clamp()and a Major Third scale. Fonts scale smoothly between mobile and desktop.
New Accessibility and Performance
- B2B Target Size: enforced a minimum height of 44px for all interactive elements (WCAG 2.2 AAA compliance).
-
Native Validation: forms now use the
:user-invalidpseudo-class, showing errors only after user interaction (no JS). - GPU Acceleration: rebuilt the Parallax and animated Blob effects. Moved calculations to the graphics card (60 FPS on mobile).
-
Zero JS for UI: complete removal of
JavaScript from Accordions, Tabs, Dropdowns, and
Modals. A move to native
-
v0.3.0April 2026
Revolution A New Architecture
-
Cascade Layers: rebuilt the
framework's main file on a native layer system
(
@layer). Eliminated specificity wars. -
The end of
!important: removed hundreds of!importantdeclarations from the_utilities.scssand_layout.scssfiles. Utility classes now win thanks to the layered architecture.
New Native Components
-
Native Modals: completely dropped divs
in favor of the native HTML
<dialog>element. Built-in focus trap, ESC key support, and the::backdroppseudo-element with no heavy JS scripts.
-
Cascade Layers: rebuilt the
framework's main file on a native layer system
(
-
v0.2.0March 2026
Added New Components
-
Modals: added a responsive modal
window component built on plain flexbox and a solid
background darkening (
.modal-backdrop). - Alerts: added an alert notification system in every color variant.
-
Dynamic Utilities: added SCSS loops
generating background and text classes (e.g.
.bg-primary,.text-white) that respond to contrast.
Change Refactoring
-
Grid System: rebuilt the grid code.
Replaced hundreds of lines of hardcoded declarations
with efficient
@forand@eachloops in SCSS. -
Variables: moved structural CSS
variables (shadows, sizes, weights) from the
[data-theme="dark"]block into the main:root. -
Dart Sass: updated the math in SCSS
(
math.percentage(),math.div()) to remove compile errors, preparing the codebase for version 3.0.0.
Fix Bugfixes
-
Removed hardcoded pixels and HEX colors from the base
files (
_base.scss,_components.scss) in favor of system variables. -
Fixed an unwanted color inversion issue for the
<code>tag and elements using.overlay-darkin dark mode. -
Removed duplicate
:focus-visibleclasses between the base file and the accessibility file (_a11y.scss).
-
Modals: added a responsive modal
window component built on plain flexbox and a solid
background darkening (
-
v0.1.0Project start
Initialization Baseline Version
-
Created the SCSS file structure (
_variables,_mixins,_base,_layout,_grid). - Implemented the basic 12-column Grid system (Flexbox).
- Created the basic components (Buttons, Forms, Cards).
-
Added dark mode support via the
data-theme="dark"attribute.
-
Created the SCSS file structure (