npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@financial-times/o-squishy-list

v2.4.6

Published

`o-squishy-list` has been deprecated. There are no direct alternatives; please [contact](#contact) the team if you would like to use this component.

Downloads

19

Readme

o-squishy-list

o-squishy-list has been deprecated. There are no direct alternatives; please contact the team if you would like to use this component.

Hides lowest priority items when space does not allow.

Usage

Markup

Given a root HTML element, o-squishy-list will assume each immediate element child is a content item.

Declaring content item priorities

The content items should be given a data-priority attribute containing a positive integer to indicate its priority with regard to display. The lower the number the higher the priority. Low-priority items will be hidden first, high-priority items will be hidden last.

Priority numbers do not have to start from 1 or be consecutive: the values 20, 34, 80 are valid and express the same relative priorities as 1, 2, 3.

Where multiple items share the same priority number, they will be hidden or shown at the same time. This allows declarative configuration of the behaviour - either all items hiding and showing at once, or each item hiding and showing individually - or a combination of the two.

If an item doesn't have a data-priority attribute, then it will be treated as lower priority than the lowest explicitly-set priority. Therefore if no items have the attribute, they will all hide and show together.

An example with four items using three levels of priority (the last item will be assumed to be priority 3):

<ul>
    <li data-priority="2">Medium priority item</li>
    <li data-priority="1">High priority item</li>
    <li data-priority="2">Medium priority item</li>
    <li>Low priority item</li>
</ul>

Sometimes you might want a particular content item to never be hidden. You can do this by setting its priority to -1 to remove it from the priorities list.

More

If some cases you might want a 'more' item which will only show when content has been hidden due to insufficient space. Simply add another <li> with a data-more attribute. It should also have a aria-hidden="true" attribute:

<ul>
    <li data-priority="2">Medium priority item</li>
    <li data-priority="1">High priority item</li>
    <li data-priority="2">Medium priority item</li>
    <li>Low priority item</li>
    <li data-more aria-hidden="true">More</li>
</ul>

When a More item element is present, sufficient content items will be hidden to make space for it to show. The width of the More item should not be allowed to change, as only the initial width is used for the content filtering calculations.

The More item will not be hidden, even if there is not sufficient space for it to show.

Hiding items manually

If you need to hide a list item manually via CSS or JS, you need to add the data-attribute data-o-squishy-list--ignore to that item. This way, o-squishy-list will stop adding that item to its item list.

<ul class="drop-off">
    <li data-priority="2" data-o-squishy-list--ignore="true">Ignore me</li>
    <li data-priority="1">Priority 1</li>
    <li data-priority="3">Priority 3</li>
    <li>No priority</li>
</ul>

Sass

The root element should have minimum and maximum widths set.

Items are hidden using aria-hidden=true. Adding [aria-hidden="true"] { display: none; } to your CSS will ensure your nav items appear and disappear as expected.

In order to calculate the total width required, items must be set to display: inline-block or float: left.

Primary and core experience

When the JS has run, a data-o-squishy-list-js attribute will be set on the root element. This can be used in CSS selectors to target primary or core.

For core experience, it is recommended to style content items so that they can all be accessible when they are shown - e.g. via wrapping or scrolling.

The data-priority attributes could also be used in CSS selectors if you wanted to only show high-priority items in the core experience:

nav li:not([data-priority='1']) {
    display: none;
}

Javascript

Construction

No code will run automatically.

An o-squishy-list object must be constructed for each container you want to filter.

var oSquishyList = require('o-squishy-list');

var nav = new oSquishyList(document.getElementsByTagName('ul'));

A optional second argument can be passed, containing a configuration object, with the following possible properties:

  • filterOnResize (boolean, default true) - if true will listen for the window.resize event and automatically call .squish()

Methods

  • squish() Hide items of lowest priority that don't currently fit into the available width.
  • getHiddenItems() Returns a list of the currently hidden item elements.
  • getRemainingItems() Returns a list of the currently remaining item elements.
  • destroy() Unbind events, un-hide items etc.

Events

This module will dispatch the following events on its root element:

  • oSquishyList.ready - when the object has constructed.
  • oSquishyList.change - when the item(s) in view change - e.g. items have been hidden or shown. The event object will contain the following properties:
    • detail.hiddenItems - array of the hidden item elements. This will be an empty array when all items are shown. The more item will not be included in this array.
    • detail.remainingItems - array of the remaining item elements. This will be an empty array when all items are hidden. The more item will not be included in this array.

A common use-case for this module is a variable-width navigation, where as the available space narrows, navigation items 'drop off' and are added to an expanded 'drop-down' menu.

To achieve this, products should listen to the oSquishyList.change event, and use the included list of hidden items to determine what to add to the expandable drop-down menu.

For example:

document.getElementsByTagName('ul')[0].addEventListener('oSquishyList.change', function(ev) {
    if (ev.detail.hiddenItems.length > 0) {
        // Loop through ev.detail.hiddenItems array
        // Extract the useful data from each element & add it to the More Menu
    }
}, false);

Contact

If you have any questions or comments about this component, or need help using it, please either raise an issue, visit #ft-origami or email Origami Support.


Licence

This software is published by the Financial Times under the MIT licence.