Awesome

Infinite Scroll for Mithril

A component to handle scrolling of an "infinite" list or grid, while only drawing what is on screen (plus a bit of pre-fetching), so safe to use on mobiles.

Compatible with Mithril 1.x.

• Examples
• Features
• Installation
• Usage
  • Handling data
    • Using pageUrl for referencing URLs
    • Data file structure
    • Using pageData for server requests
      • With m.request
      • With async
      • Returning data directly
      • Returning data as a Promise
  • Handling dynamic data
  • Advanced item function example
  • Getting the total page count
  • Using images
  • Using table data
  • Pagination
  • Custom page wrapper
• Configuration options
  • Appearance options
  • Callback functions
  • Paging options
  • Options for infinite.isElementInViewport
• Styling
  • CSS classes
  • Fixed scroll and overflow-anchor
• Size
• Dependencies
• Licence

<a name="examples"></a> <a id="examples"></a>

Examples

Examples

<a name="features"></a> <a id="features"></a>

Features

• Natural scrolling using browser defaults.
• Fast and fluent (on desktop and modern mobiles).
• Can be used for lists, grids and table-like data.
• Items that are out of sight are removed, so only a fraction of the total content is drawn on the screen. This is good for speed and memory consumption.
• Support for unequal content heights and dynamic resizing of content elements.
• As more data is loaded, the scroll view increases in size, so that the scrollbar can be used to go back to a specific point on the page.
• Items are handled per "page", which is a normal way of handling batches of search results from the server.
• Pages can contain an arbitrary and unequal amount of items.
• Pre-fetches data of the current page, the page before and after (or n pages ahead).
• When there is room on the page to show more data: automatic detection of "loadable space" (so no loading area detection div is needed).
• Optionally use previous/next paging buttons.
• Supports dynamic content (for instance when filtering results).

Not included (by design):

• Special support for older mobile browsers: no touch layer, requestAnimationFrame, absolute positioning or speed/deceleration calculations.

<a name="installation"></a> <a id="installation"></a>

Installation

Use as npm module:

npm install --save mithril-infinite

or download/clone from Github.

For working with the examples, see the examples documentation.

<a name="usage"></a> <a id="usage"></a>

Usage

Note: The parent of "scroll-view" must have a height. Also make sure that html has a height (typically set to 100%).

<a name="handling-data"></a> <a id="handling-data"></a>

Handling data

Data can be provided:

• With pageUrl for referencing URLs
• With pageData for server requests

<a id="using-pageurl-for-referencing-urls"></a>

Using pageUrl for referencing URLs

An example using data files:

import infinite from "mithril-infinite"

m(infinite, {
  maxPages: 16,
  pageUrl: pageNum => `data/page-${pageNum}.json`,
  item
})

With these options we are:

• limiting the number of pages to 16
• passing a function to generate a JSON data URL
• passing a function that should return a Mithril element

A simple item function:

const item = (data, opts, index) => 
  m(".item", [
    m("h2", data.title),
    m("div", data.body)
  ])

The item function passes 3 parameters:

1. data contains the loaded data from pageUrl.
2. opts contains: isScrolling: Bool, pageId: String, pageNum: Number, pageSize: Number
3. index: the item index

<a id="data-file-structure"></a>

Data file structure

Data is handled per "results" page. You are free to use any data format.

You could use a JSON data object for each page, containing a list of items. For example:

[
  {
    "src": "cat.jpg",
    "width": 500,
    "height": 375
  }
]

Or:

[
  ["red", "#ff0000"],
]

<a id="using-pagedata-for-server-requests"></a>

Using pageData for server requests

In most real world situations an API server will provide the data. So while passing file URLs with pageUrl is a handy shortcut, we preferably use data requests.

<a id="with-mrequest"></a>

With m.request

import infinite from "mithril-infinite"

const pageData = pageNum => 
  m.request({
    method: "GET",
    dataType: "jsonp",
    url: dataUrl(pageNum)
  })

m(infinite, {
  pageData,
  item
})

Demo tip: in the example "Grid" we use jsonplaceholder.typicode.com to fetch our images:

const PAGE_ITEMS = 10

const dataUrl = pageNum =>
  `http://jsonplaceholder.typicode.com/photos?_start=${(pageNum - 1) * PAGE_ITEMS}&_end=${pageNum * PAGE_ITEMS}`

<a id="with-async"></a>

With async

import infinite from "mithril-infinite"

const asyncPageData = async function(pageNum) {
  try {
    const response = await fetch(dataUrl(pageNum))
    return response.json()
  } catch (ex) {
    //console.log('parsing failed', ex)
  }
}

m(infinite, {
  pageData: asyncPageData,
  item
})

<a id="returning-data-directly"></a>

Returning data directly

import infinite from "mithril-infinite"

const returnData = () =>
  [{ /* some data */ }]

m(infinite, {
  pageData: returnData,
  item
})

<a id="returning-data-as-a-promise"></a>

Returning data as a Promise

import infinite from "mithril-infinite"

const returnDelayedData = () =>
  new Promise(resolve =>
    setTimeout(() =>
      resolve(data)
    , 1000)
  )

m(infinite, {
  pageData: returnDelayedData,
  item
})

<a name="handling-dynamic-data"></a> <a id="handling-dynamic-data"></a>

Handling dynamic data

In situations where the Infinite component needs to show different items - for instance when filtering or sorting search results - we must provide a unique key for each page. The key will enable Mithril to properly distinguish the pages.

Use option pageKey to provide a function that returns a unique identifying string. For example:

import infinite from "mithril-infinite"
import stream from "mithril/stream"

const query = stream("")

const Search = {
  view: () =>
    m("div", 
      m("input", {
        oninput: e => query(e.target.value),
        value: query()
      })
    )
}

const MyComponent = {
  view: () => {
    const queryStr = query()
    return m(infinite, {
      before: m(Search),
      pageKey: pageNum => `${pageNum}-${queryString}`,
      // other options
    })
  }
}

<a name="advanced-item-function-example"></a> <a id="advanced-item-function-example"></a>

Advanced item function example

To enhance the current loading behavior, we:

• Load images when they are visible in the viewport
• Stop loading images when the page is scrolling. This makes a big difference in performance, but it will not always result in a good user experience - the page will seem "dead" when during the scrolling. So use with consideration.

The item function can now look like this:

const item = (data, opts) =>
  m("a.grid-item",
    m(".image-holder",
      m(".image", {
        oncreate: vnode => maybeShowImage(vnode, data, opts.isScrolling),
        onupdate: vnode => maybeShowImage(vnode, data, opts.isScrolling)
      })
    )
  )

// Don't load the image if the page is scrolling
const maybeShowImage = (vnode, data, isScrolling) => {
  if (isScrolling || vnode.state.inited) {
    return
  }
  // Only load the image when visible in the viewport
  if (infinite.isElementInViewport({ el: vnode.dom })) {
    showImage(vnode.dom, data.thumbnailUrl)
    vnode.state.inited = true
  }
el.style.backgroundImage = `url(${url})`

<a name="getting-the-total-page-count"></a> <a id="getting-the-total-page-count"></a>

Getting the total page count

How the total page count is delivered will differ per server. jsonplaceholder.typicode.com passes the info in the request header.

Example "Fixed" shows how to get the total page count from the request, and use that to calculate the total content height.

We place the pageData function in the oninit function so that we have easy access to the state.pageCount variable:

const state = vnode.state
state.pageCount = 1

state.pageData = pageNum => 
  m.request({
    method: "GET",
    dataType: "jsonp",
    url: dataUrl(pageNum),
    extract: xhr => (
      // Read the total count from the header
      state.pageCount = Math.ceil(parseInt(xhr.getResponseHeader("X-Total-Count"), 10) / PAGE_ITEMS),
      JSON.parse(xhr.responseText)
    )
  })

Then pass state.pageData to infinite:

m(infinite, {
  pageData: state.pageData,
  maxPages: state.pageCount,
  ...
})

<a name="using-images"></a> <a id="using-images"></a>

Using images

For a better loading experience (and data usage), images should be loaded only when they appear on the screen. To check if the image is in the viewport, you can use the function infinite.isElementInViewport({ el }). For example:

if (infinite.isElementInViewport({ el: vnode.dom })) {
  loadImage(vnode.dom, data.thumbnailUrl)
}

Images should not be shown with the <img/> tag: while this works fine on desktop browsers, this causes redrawing glitches on iOS Safari. The solution is to use background-image. For example:

el.style.backgroundImage = `url(${url})`

<a name="using-table-data"></a> <a id="using-table-data"></a>

Using table data

Using <table> tags causes reflow problems. Use divs instead, with CSS styling for table features. For example:

.page {
  display: table;
  width: 100%;
}
.list-item {
  width: 100%;
  display: table-row;
}
.list-item > div {
  display: table-cell;
}

<a name="pagination"></a> <a id="pagination"></a>

Pagination

See the "Paging" example.

Custom page wrapper

Use processPageData to either:

• Process content data before passing to item
• Wrap in a custom element wrapper
• Use a custom item function

Simple example with a wrapper:

m(infinite, {
  processPageData: (content, options)  => {
    return m(".my-page", content.map((data, index) => item(data, options, index)));
  },
  ...
});

<a name="configuration-options"></a> <a id="configuration-options"></a>

Configuration options

<a name="appearance-options"></a> <a id="appearance-options"></a>

Appearance options

<a name="callback-functions"></a> <a id="callback-functions"></a>

Callback functions

<a name="paging-options"></a> <a id="paging-options"></a>

Paging options

<a name="options-for-infiniteiselementinviewport"></a> <a id="options-for-infiniteiselementinviewport"></a>

Options for infinite.isElementInViewport

All options are passed in an options object: infinite.isElementInViewport({ el, leeway })

<a name="styling"></a> <a id="styling"></a>

Styling

Note: The parent of "scroll-view" must have a height. Also make sure that html has a height (typically set to 100%).

Styles are added using j2c. This library is also used in the examples.

<a name="css-classes"></a> <a id="css-classes"></a>

CSS classes

<a name="fixed-scroll-and-overflow-anchor"></a> <a id="fixed-scroll-and-overflow-anchor"></a>

Fixed scroll and overflow-anchor

Some browsers use overflow-anchor to prevent content from jumping as the page loads more data above the viewport. This may conflict how Infinite inserts content in "placeholder slots".

To prevent miscalculations of content size, the "scroll content" element has style overflow-anchor: none.

<a name="size"></a> <a id="size"></a>

Size

Minified and gzipped: ~ 3.9 Kb

<a name="dependencies"></a> <a id="dependencies"></a>

Dependencies

• j2c - for creating js stylesheets
• Mithril 1.0
• resize-observer-polyfill
• Verge - for measuring the viewport

<a name="licence"></a> <a id="licence"></a>

Licence

MIT