Skip to content

Fallback for the interactive details element, emulating Chrome's behaviour in older browsers

License

Notifications You must be signed in to change notification settings

emilbayes/dom-details-fallback

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

dom-details-fallback

Fallback for the interactive details element, emulating Chrome's behaviour in older browsers

Install

npm install dom-details-fallback

Usage

require('dom-details-fallback')(null, true)

To create the open/close marker the ::before pseudo element is used. This is normally styled with a vendor specific pseudo element, eg. ::-webkit-details-marker, so consider this if you want to change this:

summary::before, summary:before {
  /* Custom closed marker */
}

details[open="open"] summary::before,
details[open="open"] summary:before {
  /* Custom open marker */
}

API

applyDetailsFallback(parent, injectCss)

Will only polyfill if the open property is not present on a newly created <details> element.

parent

Type: Element|Document Default: window.document

Parent of the <details> elements that should be polyfilled.

injectCss

Type: Boolean
Default: true

Inject default CSS into <head>.

License

ISC

About

Fallback for the interactive details element, emulating Chrome's behaviour in older browsers

Resources

License

Stars

Watchers

Forks

Packages

No packages published