Note that changing this option implies that it needs to be passed to the
browser polyfill as well.
disablePolyfillReadyClass
The disablePolyfillReadyClass option determines if selectors are prefixed with an indicator class.
This class is only set on your document if the polyfill loads and is needed.
By default this option is false.
Set this to true to prevent the class from being added.
import cssBlankPseudoInit from 'css-blank-pseudo/browser';cssBlankPseudoInit();
or
<!-- When using a CDN url you will have to manually update the version number --><script src="https://unpkg.com/css-blank-pseudo@8.0.2/dist/browser-global.js"></script><script>cssBlankPseudoInit()</script>
PostCSS Blank Pseudo works in all major browsers, including Safari 6+ and
Internet Explorer 9+ without any additional polyfills.
This plugin conditionally uses MutationObserver to ensure recently inserted
inputs get correct styling upon insertion. If you intend to rely on that
behaviour for browsers that do not support MutationObserver, you have two
options:
Polyfill MutationObserver. As long as it runs before cssBlankPseudoInit,
the polyfill will work.
If you don't want to polyfill MutationObserver you can also manually fire
a change event upon insertion so they're automatically inspected by the
polyfill.
Browser Usage
force
The force option determines whether the library runs even if the browser
supports the selector or not. By default, it won't run if the browser does
support the selector.
cssBlankPseudoInit({ force: true });
replaceWith
Similar to the option for the PostCSS Plugin, replaceWith determines the
attribute or class to apply to an element when it's considered to be :blank.
This option should be used if it was changed at PostCSS configuration level.
Please note that using a class, leverages classList under the hood which
might not be supported on some old browsers such as IE9, so you may need
to polyfill classList in those cases.
Using with Next.js
Given that Next.js imports packages both on the browser and on the server, you need to make sure that the package is only imported on the browser.
As outlined in the Next.js documentation, you need to load the package with a dynamic import: