A minimal, responsive, style-agnostic CSS framework!

  • By Angelos Chalaris
  • Last update: Dec 27, 2022
  • Comments: 16

mini.css

A minimal, responsive, style-agnostic CSS framework

npm license website

Logo

mini.css is a lightweight CSS framework (under 7KB gzipped) designed with mobile devices and modern browsers in mind. Responsiveness, ease of use and customization are some of the main features of the framework, while accessibility and extensive documentation are some of the secondary focuses of the project. The framework is written using Sass, while most of its components are based on Flexbox.

Setup & usage

You have 4 options when it comes to setting up mini.css:

  1. Use a package manager (recommended)
  2. Use GitCDN
  3. Use Rawgit
  4. Use cdnjs (preferred for older releases)

For instructions on how to use, best practices, templates and other usage information, please visit the framework's documentation.

Method 1: Use a package manager (recommended)

  1. Install mini.css using npm, yarn or bower.
npm install mini.css
yarn add mini.css
bower install mini.css
  1. Pick one of the available flavors and use its CSS file.

  2. Start working on your project. Detailed documentation is available on the framework's website, so be sure to check it out.

Method 2: Use GitCDN

mini.css is also hosted on GitCDN, an open-source service, so you can easily grab the latest release's distributables. Simply link to your preferred flavor inside your HTML page's <head> tag:

<link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/{mini-flavor}.css" />

Remember to replace {mini-flavor} with the flavor's name (e.g. mini-default or mini-default.min for the default flavor).

Method 3: Use RawGit

mini.css is also hosted on RawGit, another open-source service, so you can easily grab a specific release's distributables. Simply link to a release and your preferred flavor inside your HTML page's <head> tag:

<link rel="stylesheet" href="cdn.rawgit.com/Chalarangelo/mini.css/{release-tag}/dist/{mini-flavor}.css" />

Remember to replace {release-tag} with a release from the Releases page and {mini-flavor} with the flavor's name (e.g. mini-default or mini-default.min for the default flavor).

Method 4: Use cdnjs (preferred for older releases)

If you would rather use an older version of the framework, you should head over to cdnjs for a list of releases and flavor files supplied with them.

Flavors & customizaton

Flavors are one of the key features of mini.css, allowing you to customize your website's design and make your project stand out. We provide you with a few pre-defined flavors that might suit your needs and will help you figure out how to use the framework and create websites and apps with it.

But you can easily build you own flavors by using our flavor generator tool, which allows you to customize almost everything. Take your time and create the perfect flavo to suit your needs.


Contributing

  • Have you found a bug in the framework? Do you want to request a new feature or suggest a new flavor? Maybe found some documentation that is unclear or incomplete? Open an issue and we will be with you shortly.

  • Have you developed a new flavor and want to share it with the world? Open an issue about it, so that we can link to your repository from the framework's documentation and let the world know. We will try to keep you posted on any new releases coming, so that you can update your flavor as necessary.

  • Have you developed a module for the framework? Well, we don't really accept new modules right now, but if it works, we will certainly tell people that it's available. Open an issue about it and we will figure it out together.

Maintainers & contributors

The team behind mini.css is as follows:

  • Angelos Chalaris (@chalarangelo) - Sass archmage, project manager

Special thanks to these fine folks for helping in the development of mini.css:

License

mini.css is an open-source framework and is licensed under the MIT License.

Github

https://github.com/Chalarangelo/mini.css

Comments(16)

  • 1

    v3.0.0 Roadmap

    Logo

    Overview

    v3.0.0 (Gluon) is going to be a step in a different direction from Fermion, as it will be built from the ground up, with certain differences in focus and scope. Many breaking changes will be present, however some core concepts and ideas will be staying the same.

    Some of the key features that will be present in the new Gluon branch are support for CSS3 variables, which will impact most aspects of the current codebase, possible support for CSS3 grid, additional components and replacement components, as well as many UI/UX improvements, which will be the focus of the next major release. To meet these goals, the framework will be rebuilt with a focus on better aesthetics, easier customization and better user experience, even if this impacts adoption rates, due to the discontinuation of support for legacy and proxy browsers, as Gluon will be built with a focus on the future. There is also the slight possibility that Gluon will be a bit larger than 7KB in certain of its flavors, however there will always be some light flavor meeting the core goal of 7KB.

    That being said, the current Fermion branch will be supported actively, with fixes and possibly updates rolling out regularly, while Gluon is in development. After Gluon is released (estimated release date is Q1 2018 for now - this is subject to change), Fermion will be considered a legacy branch, but it will still be supported and its documentation will be available for a long time. On a side note, if you are reading this and use a Fermion build in production, make sure to point to a link with v2.x.x in its name and not the default one which loads from the last commit of the master branch.

    Finally, the Neutrino branch will not be supported any further, as it is hereafter considered a legacy version.

    Gluon - List of changes, updates, features

    Note that all of this is subject to change and that it is very importan to get as much feedback as possible to provide the best possible experience for everyone. The lists below will be populated as progress is being made in each module.

    • Updated core module, featuring less legacy fixes, along with restyling of multiple elements.
      • [x] Revamped font stack, less legacy OSes supported (current opinion leans towards -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Ubuntu, "Helvetica Neue", Helvetica, sans-serif).
      • [x] Less legacy support code, focus on future features and modern browsers.
      • [x] No support for proxy browsers (sorry Opera mini and UC Browser, it was fun while it lasted).
      • [x] Revamped color palettes for code, pre, kbd and blockquote.
      • [x] Use of CSS variables for colors and certain universal properties.
      • [x] Improved styling of pre elements.
      • [x] Fully reworked blockquote elements.
      • [x] Updated link element styling.
      • [x] Restyled, more minimal hr element styling.
      • [x] Updated code fonts to use native code-font stack. uncertain
      • [x] Optimized conditionals and code.
      • [x] Default value definitions for all variables.
      • [x] Slight simplification of the variables to allow for easier customization.
      • [x] Recheck if padding-left in lists should be based on --universal-margin or if it should use --universal-padding instead.
      • [x] Deal with links and inlined elements being broken in headings (#114).
    • A cleaner, leaner and legacy-free flexbox-based grid module. There might be something like a tile system as well, utilizing CSS grid.
      • [x] Remove legacy browser support.
      • [x] Cleaner code. - a mixin is used to simplify the maintenance of the module.
      • [x] Some use of CSS variables. - just for some basic padding needs.
      • [x] The new grid will not support the legacy xs screen size, it will now be three sizes only.
    • Better navigation elements, with focus on mobile usability.
      • [x] Make sure nav element's margin etc. are optimized to work with .drawer component.
      • [x] Revamped .drawer component.
      • [x] Reworked header styling and padding.
      • [x] Use SCSS conditional to make header links uppercase.
      • [x] Clean up and rebuild footer element.
    • Clean rebuild of input_control to allow for easier customization and better user experience.
      • [x] Clean up form styling (form, fieldset, legend).
      • [x] Recheck margin values for label and reevaluate to work with UX and icons (customized variants).
      • [x] Rework radio and checkbox. The next iteration will style the inputs directly, instead of labels, making it significantly more accessible and less complex in the coding behind it.
      • [x] Remove legacy code.
      • [x] Make .input-groups included by default as a whole, not as individual pieces, use a hidden variable.
      • [x] Use universal color and spacing options for all elements.
      • [x] Implement CSS variable variants for elements that need it (such as buttons).
      • [x] Rework .button-groups and figure out if pagination can be added to the whole thing (possibly just as examples).
    • Rebuilt table module, utilizing flexbox and infinitely scrollable tables for a better user experience.
      • [x] Make tables scrollable by default.
      • [x] Remove legacy support.
      • [x] Add .hoverable tables.
    • Improved card layout, allowing for more versatile layouts.
      • [x] Merge card module into layout, which will include it, alongside grid.
      • [x] Reevaluate padding in .double-padded .sections.
    • Rebuilt tab systems or even removal of tabs in favor of a better, easier-to-use system.
      • [x] Remove the tab module entirely, move the vertical version into contextual to be used as a spoiler component. Tabs are not going to be part of the Gluon release, as their use-cases are reasonably limited and cause a whole lot of problems. Javascript examples with proper navigation will be provided, instead.
    • Extended contextual module with more components that are easier to use and customize.
      • [x] Revamped and updated mark elements.
      • [x] Updated .modal, .tooltip and .toast elements. No legacy support and variables, as well as some changes (possibly) to make sure the are easy to use and maintain.
      • [x] Removed alerts, as they are now officially a legacy component.
    • Improved progress module, mainly removing legacy support and slightly improving on the aesthetics of components.
      • [x] Removed legacy support and prefixed animations.
      • [x] Added default (gray) styles for both progress and .spinner-donut and a .primary variant to replace the old default.
    • Updated utility module.
      • [x] Removed unnecessary elements, such as .breadcrumbs and close.
      • [x] Removed helper classes that are only useful as legacy helpers.
      • [x] Moved all helpers from mixins to the main module file.
      • [x] Cleaner, variable-based styling for as many classes as possible.
    • Utilization of CSS variables.
    • Small icon pack (20 - 50 essential icons) for a better UI/UX experience.
    • Improved and updated documentation.
      • [x] Add search functionality.
      • [x] Add SSL to the documentation.
      • [x] Include customization alongside the element documentation.
      • [x] Improved getting started section.
      • [x] Generate Codepens from code samples.
      • ~~Javascript examples and support scripting, allowing users to get more bang for their buck, if they need in specific components (e.g. table sorting).~~
    • Tools that allow for a flavor build on-the-fly, altering CSS variables in certain parts of the framework.
      • [x] New flavor generation page with variable customization.
      • [x] ~~Dynamic mixin addition for each module (up to a specific limit)~~ Predefined mixins customization.
      • [x] Toggle modules on or off.
      • [x] Generate flavor files.
      • [x] Provide links to website with color palettes and box shadows, as well as other useful tools.
    • [x] Port all original flavors to new version, add some more.

    Compatibility

    As stated in the Overview section, the Gluon update will be a brand new framework, meaning a lot of the existing conventions and semantics will be changed. If you are using a previous version of Fermion, remember to point to a version-specific link.

    Migrating to Gluon might take a little bit of effort, but I will try to make it as smooth as possible, by providing guidelines and help every step of the way.

    Release date

    It's too soon to tell, but the aim is to release sometime in the first quarter of 2018.

  • 2

    Add support for CSS custom properties

    Many of the variables used in the framework can be changed from SCSS variables to CSS variables.

    However this feature is not well-supported yet, thus it will be some time until the framework changes to CSS variables. This is a planned change and it will take place sometime later, when support for the feature is over 85% (currently at 66% as of October 2016).

  • 3

    Use ARIA roles to designate semantic markup with behaviour

    Instead of using classes, mini.css could make any site that uses it more accessible CSS by default if you use ARIA roles to identify tabs, buttons, alerts, menus and navbars, etc.

    The CSS selectors then change from class selectors, to attribute selectors like [role~="tab"] { ... }. This is CSS 2.1 IIRC, so it already has broader browser support than mini.css's latest version.

  • 4

    Broken Links in documentation

    Hey there,

    let me first say that I really love your project. I have downloaded your latest release and was ready to read the documentation but the links on the navbar do not link to the respective html files. I think that the links are made so that they work only for your minicss.org domain but not for offline reading. Would it be ok if a create a pull request and change the links so that they will work offline ?

  • 5

    Empty breaks table layout

    I noticed that when the <td> is empty and we have specified a data-label then the table layout breaks at that point. In the attached screenshot the "td 3' is empty. 2017-10-15_14h21_24

  • 6

    Support for more [colour] icons

    Hi there,

    is it possible to add more feather icons ?

    I would like some icons like delete and add which are helpful when creating forms etc.

    Also is it possible to add colour to the icons ?

  • 7

    Problem when php code embedded

    • Framework Version: 2.3
    • Flavor used: none
    • Operating System/Browser: W10 64 bits
    • Bug description: when embedding php code in the navbar, the menu does not collapse when screen size gets lower.

    `

    Home
     <?php
    // if admin access to admin menu
    if ( isset($_SESSION['admin']) && $_SESSION['admin']=='1' )
    {
    	echo"<a href='apaguard_adminusers.php' role='button'>Gestion utilisateurs</a>";
    	echo"<a href='apaguard_adminapaguard.php' role='button'>Gestion Apaguards</a>";
    	echo"<a href='apaguard_adminruchers.php' role='button'>Gestion ruchers</a>";
    	echo"<a href='apaguard_adminruches.php' role='button'>Gestion ruches</a>";
    }
    
    // if logged, access to user menu	
    elseif ( isset($_SESSION['proprietaire_id']) )
    		{
    			echo"<a href='apaguard_edituser.php' role='button'>Mon compte</a>";
    			echo"<a href='change_password.php' role='button'>Password</a>";
    			echo"<a href='apaguard_editruche.php' role='button'>Ruches</a>";
    			echo"<a href='apaguard_editrucher.php' role='button'>Ruchers</a>";
    			echo"<a href='apaguard_editapaguard.php' role='button'>Apaguards</a>";
    			echo"<a href='apaguard_datas.php' role='button'>Données</a>";
    		}
    	else
    {
    echo"
    <a href='apaguard_graph.php' role='button'>Demo</a>
    <a href='apaguard_tech_infos.php' role='button'>Techniques</a>
    
    ";
    }		
    // dynamic login menu
    		if ( !isset($_SESSION['proprietaire_id']) )
    			{
    				echo"<a href='login.php' role='button'>Login</a>";
    			}
    		else 
    		{
    			echo "<a href='logout.php' role='button'>Logout</a>";
    		}
    	// if not logged, display visitor menu
    ?>
    
  • 8

    v2.3.0 Roadmap

    Overview

    ~~v2.2.1~~v2.3.0 is going to contain a host of new features and additions, as well as bug fixes and updates, dealing with problems in all modules and polishing up most of the components provided. Due to the fact that v2.2.1 was delayed a lot, I decided to drop the minor patch update and merge it with v2.3.0, so that more things can be added and fixed in one single release.

    New features & components

    • [x] A modal component will be added, as requested in the past (see the discussion in #46).
    • [x] An Android-style switch component will be added. Mainly targeted at PWAs and mobile-centric flavors.
    • [x] .scrollable tables, allowing a better view for data. Bear in mind this might be pushed back to the next update, as it is certainly unstable so far.
    • ~~Some atomic CSS classes might be added to help make layouts and other things easier for beginners.~~ (See comments)

    Bug fixes/updates/polishing up

    • [x] Reworked color palette, especially the gray tones, making buttons and code markup easier on the eyes.
    • [x] Slight update to the progress module's bars to make them look more modern (rounded edges and a bit less thickness are what I'm thinking of).
    • [x] Updates to the input_control module, especially .input-group components for convenience. This might actually happen either under the hood or not at all, based on internal tests and use-cases. Please report any trouble you had with the module and/or layout ideas that you had trouble implementing with the specific components.

    Documentation

    N/A yet.

    Miscellaneous

    • [x] Updates to the package.json file, removing the doc folder to minimize download size, as well as updating the structure etc.
    • [x] .npmignore should now ignore the docs folder.
    • [x] Any and all work for updates will move to the next branch from now on.
    • [x] Add a $_1px variable to calculate the rem value of 1px whenever possible.
    • It is possible that variable mapping might make it into this update, but 99% it will be pushed back to the next one, as it will require a lot of creative thinking and changes to existing code.

    Release date

    There is no solid estimate yet, but this update will be releasing sometime this month. I will take as much time as required to make this update stable and content-rich, so that later updates build upon it and start addressing #19, which is becoming a reasonably pressing matter.

  • 9

    v2.1.1 (Fermion) Roadmap

    Overview

    The next release of Fermion will mostly deal with codebase cleanup and minor changes to the way the framework works. It's a pretty behind-the-scenes patch that should pave the way for the next few patches, that will slowly but steadily introduce new features and minor changes to the framework's inner workings.

    Estimated release

    v2.1.1 has no release date set in stone yet, but it will be out mid-to-late April, depending on how development goes. There is a very slight chance that the release date will be early April.

    List of upcoming changes

    Codebase cleanup and restructure:

    • [x] Certain changes will be made to the .scss files to make their stucture more usable and less confusing to newcomers.
    • [x] More default values will be introduced wherever possible to make the framework less dependent on user-specified values and less prone to mistakes.
    • [x] @media queries will be updated to explicitly work on screens and not printers, so that the print styles that are coming later down the line can be implemented more easily.
    • [x] More flags might be introduced to modules, so that it is easier to tweak what features are on or off. Some flags will be hidden so that inexperienced users do not accidentally break their flavors.
    • [x] Mixins might get their own files, so that they are easier to call, extend and include.

    Documentation changes:

    • [x] Add documentation for new flavor, responsive hiding.
    • [x] Parts of the documentation will be clarified and either the wiki will be rebooted (#38) or new pages will be introduced to the documentation of the site, so that developers can get a more advanced understanding of how to tweak the framework.
    • [x] Templates for common designs will be introduced both via Codepen links and demo pages, as well as downloadable starter sites.
    • [x] Change preferred CDN from rawgit to gitcdn (#64).

    New features:

    • [x] Possible new flavor (barebones is the current codename I am using) that will be smaller, easier to use and cut out all the fat of certain features that are not widely used in websites.
    • [x] Possible addition of figure and figcaption styles - might be pushed back to next release.
    • [x] Possible introduction of screen-specific .hidden classes (both accessible and normal) to deal with a common enough problem (#61).

    Bug fixes:

    • [x] Deal with the problematic rendering of .button-group under smaller screens (vertical grouping) on Chrome (#63).
  • 10

    fix background styles for select in Safari

    Fixed issue #80 where the styling in Safari for select weren't working properly.

    Only adding -webkit-appearance: none won't suffice since it not only removes the gloss in Safari, but also removes the arrows.

    Here's a screenshot with this fix in both Chrome & Safari:

    Safari safari

    Chrome chrome

  • 11

    v2.2.0 Roadmap

    Overview

    The release of v2.2.0 will change a lot of things around and it will also bring about some breaking changes. A list of changes, along with their progress is shown below.

    Upcoming changes

    • [x] Introduction of a .drawer (name is not finalized) component in navigation, allowing for slide-in menus and responsive navigation.
    • [x] Introduction of fluid typography, effectively scaling the root element of the document, based on the screen size (uses calc()). This feature will most likely be opt-in, meaning that old flavors will not be affected, as the feature will be turned off by default.
    • [x] The ordering of modules will be changed (input_control should come before navigation at least) to improve style cascading and gzip compression.
    • [x] Re-evaluation of all padding and margin values, making sure that no oddities and artifacts exist and that everything works quite well with fluid typography.
    • [x] The responsive margin and padding classes of the utility module will be revisited to make sure their padding and margin values are useful and !important declarations will be added to make sure they are applied (found a bug where they do not apply properly).
    • [x] The .alert classes of the contextual module will be retired (I will either move them to their own component module as an extra or flag-disable them). A .toast class will take their place, making it easier to show toast messages on mobile devices.
    • [x] Classes similar to the .urgent and .critical alerts will be added as .card classes.
    • [x] The .inverse .card class will be removed, as it serves no practical purpose except to showcase the specific card mixin.
    • [x] The .nano class will be removed from the progress module, as it serves no real purpose right now.
    • [x] The .close icon class will be revisited and redesigned to utilize a textual ::before pseudo-element with simpler rules, making it more lightweight. Also, extra rules might be added to make it compatible with <label> elements and the new .drawer component.
    • [x] Generic shadow classes will be revisited, most likely removing most of them and adding a single generic shadow class for elements (the .shadow-none class will be probably gone as well).

    Compatibility

    v2.2.0 will introduce a few new components and remove some older ones, in order to improve functionality and de-bloat the framework somewhat. Refer to the above list of changes for more details.

    Release date

    Worst case scenario is that v2.2.0 will take until mid-June, but that is highly unlikely. The most likely scenario is that it will be available sometime towards the end of May. Stay tuned for more updates!

  • 12

    Bump node-sass from 4.9.2 to 7.0.0

    Bumps node-sass from 4.9.2 to 7.0.0.

    Release notes

    Sourced from node-sass's releases.

    v7.0.0

    Breaking changes

    Features

    Dependencies

    Community

    • Remove double word "support" from documentation (@​pzrq, #3159)

    Misc

    Supported Environments

    OS Architecture Node
    Windows x86 & x64 12, 14, 16, 17
    OSX x64 12, 14, 16, 17
    Linux* x64 12, 14, 16, 17
    Alpine Linux x64 12, 14, 16, 17
    FreeBSD i386 amd64 12, 14

    *Linux support refers to major distributions like Ubuntu, and Debian

    v6.0.1

    Dependencies

    Misc

    Supported Environments

    ... (truncated)

    Changelog

    Sourced from node-sass's changelog.

    v4.14.0

    https://github.com/sass/node-sass/releases/tag/v4.14.0

    v4.13.1

    https://github.com/sass/node-sass/releases/tag/v4.13.1

    v4.13.0

    https://github.com/sass/node-sass/releases/tag/v4.13.0

    v4.12.0

    https://github.com/sass/node-sass/releases/tag/v4.12.0

    v4.11.0

    https://github.com/sass/node-sass/releases/tag/v4.11.0

    v4.10.0

    https://github.com/sass/node-sass/releases/tag/v4.10.0

    v4.9.4

    https://github.com/sass/node-sass/releases/tag/v4.9.4

    v4.9.3

    https://github.com/sass/node-sass/releases/tag/v4.9.3

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 13

    Bump jszip from 3.1.5 to 3.7.0

    Bumps jszip from 3.1.5 to 3.7.0.

    Changelog

    Sourced from jszip's changelog.

    v3.7.0 2021-07-23

    • Fix: Use a null prototype object for this.files (see #766)
      • This change might break existing code if it uses prototype methods on the .files property of a zip object, for example zip.files.toString(). This approach is taken to prevent files in the zip overriding object methods that would exist on a normal object.

    v3.6.0 2021-02-09

    • Fix: redirect main to dist on browsers (see #742)
    • Fix duplicate require DataLengthProbe, utils (see #734)
    • Fix small error in read_zip.md (see #703)

    v3.5.0 2020-05-31

    • Fix 'End of data reached' error when file extra field is invalid (see #544).
    • Typescript definitions: Add null to return types of functions that may return null (see #669).
    • Typescript definitions: Correct nodeStream's type (see #682)
    • Typescript definitions: Add string output type (see #666)

    v3.4.0 2020-04-19

    • Add Typescript type definitions (see #601).

    v3.3.0 2020-04-1

    • Change browser module resolution to support Angular packager (see #614).

    v3.2.2 2019-07-04

    • No public changes, but a number of testing dependencies have been updated.
    • Tested browsers are now: Internet Explorer 11, Chrome (most recent) and Firefox (most recent). Other browsers (specifically Safari) are still supported however testing them on Saucelabs is broken and so they were removed from the test matrix.

    v3.2.1 2019-03-22

    • Corrected built dist files

    v3.2.0 2019-02-21

    • Update dependencies to reduce bundle size (see #532).
    • Fix deprecated Buffer constructor usage and add safeguards (see #506).
    Commits
    • e5b3f0d 3.7.0
    • e88ba4b Update for version 3.7.0
    • 9046487 Disable proto assert that fails in browsers
    • 6d029b4 Merge pull request #766 from MichaelAquilina/fix/files-null-prototype
    • bb38812 Ensure prototype isn't modified by zip file
    • d024c22 test: Add test case for loading zip filenames which shadow method names
    • 2235749 fix: Use a null prototype object for this.files
    • b7f472d Merge pull request #757: Update license to be valid spdx identifier
    • a311039 update license to be valid spdx identifier
    • 112fcdb 3.6.0
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

  • 14

    Added .nojekyll file to the docs folder

    This should fix #140

    The problem was that all files in /mini begin with underscore (ie: _core.scss). By default github pages ignores them, because of Jekyll's ignore rules. Adding a .nojekyll file at /docs solves the problem, as the site does not use Jekyll.

    More on the topic: https://github.blog/2009-12-29-bypassing-jekyll-on-github-pages/

    Also I've published the fix here for testing: https://sigmasoldi3r.github.io/mini.css/flavors

  • 15

    Getting a table to not wrap

    • Framework Version: 3.01
    • Flavor used: dark
    • Operating System/Browser: windows/chrome
    • Code to reproduce:
    • Screenshots:
    • Bug description:
    • Additional information (Optional):

    I've got a simple php calendar on my page but I don't want it to change on a narrow mobile display. Any way to remove this from happening for a single table? It seems the behavior applies to any table in Mini.

  • 16

    How to add an item to the documentation notes of modal dialogs ?

    Hi,

    I just want to add to the notes of modal dialogs that this dialogs can be automatically open when the page is loaded by adding the checked attribute to checkbox input.

    Which file I add to modify in the /docs folder, docs.html ?