littlefoot

v4.1.2

Published

2 months ago

Footnotes without the footprint.

Downloads

12,314

0High
0Medium
0Low

goblindegook

littlefoot.js

version minified + gzip

littlefoot is a lightweight JavaScript library that creates exceptional footnotes.

Simply include the code on your pages and footnotes will be detected automatically and improved in the following ways:

Links to footnotes will be replaced with clickable/tappable buttons, making them substantially easier to hit.
Footnote content will appear in a popover directly beside the footnote button when it is clicked/tapped, which cuts out the annoying bouncing around the page that footnotes typically result in.
The active popovers will be resized and repositioned to ensure that they continue to be completely visible on-screen and aesthetically pleasing: this makes it perfect for mobile devices and responsive designs.
Supports the markup generated by MultiMarkdown by default.

This project includes the script itself and a default style to apply to the footnote buttons and popovers that are eventually generated. There are also a variety of additional styles that illustrate some of the possibilities for styling these components.

littlefoot was forked from Bigfoot.js by Chris Sauvé. Unlike Bigfoot.js, littlefoot does not require jQuery.

Installation

Install using NPM:

npm install --save littlefoot

Install using Yarn:

yarn add littlefoot

Usage

The script will work with a wide array of markup, but you will need to make sure that your footnote content/link markup at least resembles the markup shown below, which is the format generated by MultiMarkdown:

<!-- Links -->
<p>
  <sup id="fnref:1">
    <a href="#fn:1">1</a>
  </sup>
</p>

<!-- Footnote List -->
<div class="footnotes">
  <ol>
    <li class="footnote" id="fn:1">
      <p>footnote. <a href="#fnref:1" title="return to article"> ↩</a></p>
      <p></p>
    </li>
  </ol>
</div>

Once you've set up the appropriate markup, all you need to do is include the following in your code:

const { littlefoot } = require('littlefoot')

littlefoot()

You can also configure the available options by passing an object literal, and you can store the return object to make use of some of the methods it makes available:

const { littlefoot } = require('littlefoot')

const lf = littlefoot({
  activateOnHover: true,
  hoverDelay: 250,
})

You'll also want to include styles for the button and popovers, a number of which come with the script.

Usage with WordPress

Install the wp-littlefoot plugin by following the provided instructions.

Usage with Gatsby

Install littlefoot as a dependency in your Gatsby project.

At the root of the site's project, create or edit a gatsby-browser.js file and add the following:

import littlefoot from 'littlefoot'
import 'littlefoot/dist/littlefoot.css'

export function onRouteUpdate() {
  littlefoot() // Pass any littlefoot settings here.
}

Usage from a CDN

Follow these steps to add littlefoot to a plain HTML document without package management support. While this method is simpler to use, bear in mind that including files from external sources will slightly degrade the page's loading performance.

Add the required footnote stylesheet at the top of your HTML file, inside the <head> tag:
```
<link
  rel="stylesheet"
  href="https://unpkg.com/littlefoot/dist/littlefoot.css"
/>
```

Add the following script tags at the end of the document, just before the closing </body> tag:

<script
  src="https://unpkg.com/littlefoot/dist/littlefoot.js"
  type="application/javascript"
></script>
<script type="application/javascript">
  littlefoot.littlefoot() // Pass any littlefoot settings here.
</script>

See an example on CodePen.

Options

The script has many configurable options from having popovers instantiated on hover, to allowing multiple active footnotes, to setting specific timeouts for popover activation and dismissal. It also returns an object that allows you to activate and dismiss popovers.

`activateCallback`

Specifies a function to call on a footnote popover that is being activated (after it is added to the DOM). The function will be passed two arguments: the popover DOM element, and the button that was activated to show the popover. This option can be useful for adding classes or styling information on the popover.

Default: undefined

`dismissCallback`

Specifies a function to call on a footnote popover that is being dismissed (just before it is removed from the DOM). The function will be passed two arguments: the popover DOM element, and the related button. This option can be useful for removing classes on the popover.

Default: undefined

`activateDelay`

Sets a delay between the activation of the footnote button and the activation of the actual footnote content.

Default: 100

`activateOnHover`

Specifies whether or not the footnote content will be activated when the associated button is hovered over.

Default: false

`allowDuplicates`

Determines whether or not a footnote can be used as the content for multiple footnote buttons. Many content management systems will, on a blog's main page, load every article chronologically without any adjustments to the article markup. This can cause issues if multiple footnotes have the same ID: the footnote content is identified by the fragment identifier in the href attribute of the footnote link, so multiple identical IDs can result in the same footnote content being used for different footnote links. This option prevents this by using a footnote as the content for at most one footnote button.

Default: true

`allowMultiple`

Specifies whether or not multiple footnote popovers can be active simultaneously.

Default: false

`anchorPattern`

Specifies the pattern that must be matched by the anchor element's href attribute for it to be considered a footnote link. This is used in filtering all links down to just those with a footnote.

Default: /(fn|footnote|note)[:\-_\d]/gi

`anchorParentSelector`

The selector for the parent of the footnote link. This is really only necessary when you want to get rid of that element --- for instance, when the link is inside a sup tag. This tag and the link itself will be joined together for attribute from which you can drawn in your markup for footnotes/buttons.

Default: sup

`dismissDelay`

When the footnote content is being removed this option specifies how long after the active class is removed from the footnote before the element is actually removed from the DOM.

Default: 500

`dismissOnDocumentTouch`

Determines whether touching the document will dimiss all active footnotes. When false, footnotes can be dismissed by touching the button again.

Default: true

`dismissOnUnhover`

Determines whether footnotes that were presented when hovering on a footnote button are dismissed once the footnote button or footnote popover is un-hovered.

Default: false

`footnoteSelector`

The element that contains the footnote content. This element will be hidden and given a littlefoot--print class once littlefoot has finished with it.

Default: 'li'

`hoverDelay`

If dismissOnUnhover is true, this specifies the amount of time (in milliseconds) that must pass after the footnote button/content is un-hovered before the footnote is dismissed.

Default: 250

`numberResetSelector`

A string representing the selector at which you would like the numbering of footnotes to restart at 1. For example, you may be using the numbered style of footnote and wish to have the numbers restart for each <article> on your main page with a class of 'article-container' In this case, you would set this option to 'article.article-container' (or an equivalent CSS selector). Leaving the option undefined will simply number all footnotes on a given page sequentially.

Default: undefined

`scope`

If any truthy value is provided, only the footnotes within the scope you define will be affected by the script. The scope should be a selector string, as you would typically use in jQuery. For example, setting a scope of '.littlefoot-active' would work only on those elements with an ancestor that has a class of littlefoot-active.

Default: undefined

`contentTemplate`

A template for the markup of the footnote content popovers. It's best not to change this too much; the library relies on the class names and hierarchy of the default markup to do its work. However, you can add information to the rendered markup by adding string literals or one or more of the following variables:

content: The HTML markup of the original footnote.
number: The footnote number (sequential ordering of all footnotes within an element matching the numberResetSelector option).
id: The footnote identifier (sequential ordering of all footnotes on the page, starting from 1).

Variables should be added between interpolation delimiters. For example, <% content %>.

Default:

<aside
  alt="Footnote <% number %>"
  class="littlefoot__popover"
  id="fncontent:<% id %>"
>
  <div class="littlefoot__wrapper">
    <div class="littlefoot__content"><% content %></div>
  </div>
  <div class="littlefoot__tooltip"></div>
</aside>

`buttonTemplate`

A template for the markup of the footnote button. Again, try not to remove any elements from the markup, but add as much as you like.

content: The escaped HTML markup of the original footnote.
id: The footnote identifier (sequential ordering of all footnotes on the page, starting from 1).
number: The footnote number (sequential ordering of all footnotes within an element matching the numberResetSelector option).
reference: The footnote reference used to populate the ID attribute.

Variables should be added between interpolation delimiters. For example, <% content %>.

Default:

<button
  class="littlefoot__button"
  id="<% reference %>"
  title="See Footnote <% number %>"
>
  <svg
    role="img"
    aria-labelledby="title-<% reference %>"
    viewbox="0 0 31 6"
    preserveAspectRatio="xMidYMid"
  >
    <title id="title-<% reference %>">Footnote <% number %></title>
    <circle r="3" cx="3" cy="3" fill="white"></circle>
    <circle r="3" cx="15" cy="3" fill="white"></circle>
    <circle r="3" cx="27" cy="3" fill="white"></circle>
  </svg>
</button>

Numerical footnotes

To display the footnote number instead of an ellipsis, provide the following buttonTemplate instead:

<button
  aria-label="Footnote <% number %>"
  class="littlefoot__button"
  id="<% reference %>"
  title="See Footnote <% number %>"
/>
  <% number %>
</button>

Methods

Running the function will return an object that can be stored and used to manipulate the footnote buttons/content. The following methods are available in this return object:

`dismiss([footnoteId[, timeout]])`

This function will close the popover matching the footnote ID. If omitted, all popovers are dismissed. timeout specifies the amount of time after the footnote's active class is removed before the element itself is removed. If excluded, timeout will default to the dismissDelay option.

`activate(footnoteId[, timeout])`

This will activate the footnote button (and its associated popover) matching the footnote ID. timeout specifies the amount of time before the footnote's active class is applied. If excluded, timeout will default to the activateDelay option.

`getSetting(key)`

Returns the instance setting matching the provided string key.

`updateSetting(key, value)`

Updates the littlefoot instance settings for the provided string key with a new value.

`unmount()`

This will disable littlefoot and restore the document to its original structure, clearing event handlers. Once unmount() is called, all other methods provided in the littlefoot instance will stop working, requiring you to call the littlefoot() function again.

Theming

littlefoot supports theming through CSS custom properties. The following custom properties are available in browsers or CSS precompilation tools that support them, and are scoped to the .littlefoot class.

Example

Customise littlefoot's appearance by overriding its custom properties in your site's CSS, like so:

.littlefoot {
  --button-active-background-color: #d2b450;
  --button-text-color: #fff;
}

Buttons

Popovers

Backwards compatibility

Browsers that don't support CSS custom properties will receive the default values. The appearance of elements may still be overridden through normal CSS definitions as in previous versions of littlefoot.

Changes from Bigfoot.js

Consult the changelog.

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme

littlefoot.js

Installation

Usage

Usage with WordPress

Usage with Gatsby

Usage from a CDN

Options

activateCallback

dismissCallback

activateDelay

activateOnHover

allowDuplicates

allowMultiple

anchorPattern

anchorParentSelector

dismissDelay

dismissOnDocumentTouch

dismissOnUnhover

footnoteSelector

hoverDelay

numberResetSelector

scope

contentTemplate

buttonTemplate

Numerical footnotes

Methods

dismiss([footnoteId[, timeout]])

activate(footnoteId[, timeout])

getSetting(key)

updateSetting(key, value)

unmount()

Theming

Example

Buttons

Popovers

Backwards compatibility

Changes from Bigfoot.js

License

`activateCallback`

`dismissCallback`

`activateDelay`

`activateOnHover`

`allowDuplicates`

`allowMultiple`

`anchorPattern`

`anchorParentSelector`

`dismissDelay`

`dismissOnDocumentTouch`

`dismissOnUnhover`

`footnoteSelector`

`hoverDelay`

`numberResetSelector`

`scope`

`contentTemplate`

`buttonTemplate`

`dismiss([footnoteId[, timeout]])`

`activate(footnoteId[, timeout])`

`getSetting(key)`

`updateSetting(key, value)`

`unmount()`