@txstate-mws/svelte-components 1.0.2 → 1.0.3

package/dist/ts/tests/Modal/ModalTest.svelte

@@ -1,58 +0,0 @@
-<script lang="ts">
-  import Modal from '../../components/Modal.svelte'
-  let shown = true
-</script>
-
-{#if shown}
-<Modal on:escape={() => shown = false}>
-  <form>
-    <div class="formfield">
-      <label for="firstname">First Name:</label><input id="firstname" type="text" name="firstname">
-    </div>
-    <div class="formfield">
-      <label for="middlename">Middle Name:</label><input id="middlename" type="text" name="middlename">
-    </div>
-    <div class="formfield">
-      <label for="lastname">Last Name:</label><input id="lastname" type="text" name="lastname">
-    </div>
-    <input type="submit" value="Submit">
-  </form>
-</Modal>
-{/if}
-<div class="content">
-  <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer tempus nulla ut nulla auctor, quis sodales massa laoreet. Duis erat lacus, gravida vitae massa vel, semper accumsan urna. Morbi gravida dui sit amet sodales luctus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Vestibulum eget pulvinar dui. Vivamus quis eros eu ex semper consectetur nec at elit. Praesent faucibus arcu a nisi semper, eu tempus felis vehicula. Suspendisse potenti.</p>
-
-  <p>Donec luctus nulla mattis ipsum aliquam imperdiet. Vestibulum nec finibus enim. Proin et arcu arcu. Quisque feugiat leo velit, vitae mollis felis ornare sed. Suspendisse sollicitudin, libero sed ullamcorper finibus, diam turpis eleifend velit, ut suscipit orci mauris id purus. Donec dapibus facilisis mauris a venenatis. Maecenas gravida velit maximus nibh tincidunt, eget auctor tellus efficitur. Aenean varius tristique lacus, sit amet placerat sem tempor at. Sed imperdiet fermentum nibh, sit amet tempor est cursus ac.</p>
-  <button data-testid="button" on:click={() => shown = true}>Show Modal</button>
-  <p>Praesent augue magna, maximus at mattis eget, euismod nec neque. Phasellus ut dolor a turpis molestie fermentum. Phasellus condimentum, ipsum sed rutrum maximus, diam ex ultrices sapien, quis iaculis nisi arcu at turpis. Morbi aliquam mattis posuere. Integer pretium diam diam, non lobortis quam consectetur laoreet. Sed posuere blandit venenatis. Nulla gravida maximus arcu non consectetur.</p>
-
-  <p>Cras egestas massa mattis dictum imperdiet. Nulla bibendum nisl ipsum, ut scelerisque arcu consectetur vitae. Integer convallis id nunc sit amet faucibus. Maecenas suscipit diam orci, ac suscipit dolor convallis sed. Mauris vel tellus eget nunc mattis faucibus sit amet sed lorem. Cras lobortis, massa at vestibulum dignissim, quam tellus sagittis purus, eget dictum dolor quam in leo. Aliquam condimentum, ante sit amet semper laoreet, lacus est scelerisque mi, nec mollis diam massa et massa. Donec sagittis massa quis diam dictum, sit amet convallis mauris tincidunt. Nam vulputate ligula quis ex condimentum, in sollicitudin dolor accumsan. Donec volutpat dui in faucibus tempus. Proin vitae tincidunt ex. Proin ut ultricies diam. Praesent sed purus in purus efficitur fermentum vulputate quis dolor. Morbi viverra quam ac dolor facilisis consectetur.</p>
-
-  <p>Phasellus convallis congue mi, at auctor neque facilisis vestibulum. Maecenas tincidunt eros nec ornare vehicula. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Aenean odio erat, efficitur sit amet neque ut, condimentum scelerisque enim. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Duis sagittis nisl aliquam, rutrum eros eget, luctus augue. Praesent sollicitudin facilisis nisi, eget tincidunt dolor vestibulum sed. Nullam auctor consequat est, sit amet convallis sem fermentum vitae. Pellentesque tempor, turpis vel tristique imperdiet, tellus nunc blandit lorem, et tristique velit dui sed ante. Praesent tempor, sem at vulputate porta, dolor lacus condimentum augue, non tincidunt magna sapien ultrices massa. In consequat, ligula ac elementum ornare, enim dui semper metus, a vehicula arcu odio at sapien. Donec et sodales dui, sed tempus turpis.</p>
-
-  <p>Donec quis elit dolor. Proin rutrum lorem sapien, eu tempor urna commodo facilisis. Nunc at est eu purus mattis auctor eget et libero. In auctor dictum massa, nec hendrerit augue facilisis a. Vestibulum sit amet accumsan dolor, sit amet porta ante. Nam fringilla, velit eu tempus pulvinar, magna nibh iaculis dolor, a rutrum nibh turpis vel metus. Mauris quis lorem et nunc blandit feugiat. Phasellus vitae luctus turpis, id blandit nulla. Aliquam imperdiet mattis ante laoreet ullamcorper. Vivamus in laoreet purus, id fermentum velit. Phasellus eleifend libero in velit feugiat rhoncus.</p>
-
-  <p>Maecenas et mattis erat. Fusce volutpat urna tortor, sed lobortis sapien dignissim nec. Morbi id aliquet nunc. In hac habitasse platea dictumst. Mauris in lobortis dolor. Nunc orci urna, vehicula et turpis a, sagittis gravida est. Sed quis sem sapien. Morbi finibus neque lorem, non lobortis magna sodales vitae. In feugiat metus purus, ac rhoncus lorem tristique id. Nulla volutpat ex ac nulla ultrices, nec pellentesque urna semper. Donec a neque finibus, faucibus mi ac, viverra diam. Nullam a nisi vel enim gravida semper. Nam a ante nisi. Fusce tempor odio diam, vel commodo odio tempor et. Praesent sagittis consequat leo, eu efficitur justo finibus dignissim. Suspendisse in commodo sapien.</p>
-
-  <p>Pellentesque varius dui mauris, eget commodo lectus aliquet quis. Nulla vehicula vitae est ut euismod. Vivamus tempus tempus volutpat. Etiam cursus in leo et pulvinar. Vestibulum interdum porttitor efficitur. Morbi vestibulum dignissim massa nec molestie. Nullam eu sodales leo, nec pharetra arcu. Proin accumsan ligula ac lorem ullamcorper lacinia. Duis ut mi quis augue auctor tempor. Duis volutpat elit nec venenatis pharetra. Suspendisse luctus placerat tincidunt. Cras interdum interdum felis id vehicula. Aenean quis erat nec urna gravida tristique id in turpis. Integer dapibus placerat enim, vitae vehicula elit.</p>
-
-  <p>Fusce lorem magna, molestie euismod tincidunt et, hendrerit nec nibh. Duis id nibh nisl. Cras lectus sapien, hendrerit vitae dui eu, tincidunt tristique magna. Pellentesque molestie in velit in volutpat. Morbi egestas lacus neque, sit amet pulvinar sem volutpat ut. Aenean congue bibendum nisl ut malesuada. Donec mattis laoreet commodo. Nulla accumsan maximus porttitor.</p>
-
-  <p>Phasellus vel mi nec sapien pharetra mattis quis nec orci. Praesent eu suscipit nisi, a euismod nisi. Sed id dolor quis nisl tincidunt accumsan. Aliquam aliquam sed erat eu vehicula. Sed vestibulum felis egestas, pharetra nisi vel, fringilla sem. In maximus dui in hendrerit vulputate. Quisque lobortis iaculis lacus, sit amet lacinia sapien interdum sed. Vivamus congue neque fringilla tellus pellentesque blandit. Sed nec sapien at nisl molestie sollicitudin. Etiam a nulla tortor. Ut non tellus turpis. Curabitur ultrices pharetra velit, sed ultricies magna viverra sed.</p>
-
-  <p>Nunc in vehicula diam, ac molestie est. Aliquam efficitur at neque nec tristique. Nullam elementum arcu quis dolor sodales pulvinar. Phasellus pretium, ex at hendrerit rhoncus, orci diam mattis purus, a tempor nisi mauris vitae lectus. Aenean eget vulputate diam. Ut ultrices, nunc id hendrerit mattis, mi felis sagittis sapien, eget euismod massa risus eu risus. Morbi euismod vulputate ultrices. Etiam et pretium elit. Suspendisse potenti. Proin scelerisque convallis purus, at viverra massa fermentum a. Curabitur nunc orci, accumsan sodales massa a, dignissim luctus lorem. Praesent tincidunt augue eget tempus auctor.</p>
-
-  <p>Nam rhoncus tincidunt lorem, ac vehicula mauris luctus sit amet. Donec bibendum semper ex, quis condimentum eros elementum id. Morbi id commodo libero, id euismod ipsum. Nullam ante tellus, dapibus ut accumsan ac, pellentesque ut turpis. Quisque ligula nisi, pulvinar id urna id, aliquam laoreet enim. Fusce nec lorem malesuada, dapibus ipsum vel, rhoncus odio. Cras risus tortor, laoreet at odio ac, eleifend rutrum sapien. Sed scelerisque, urna ac iaculis condimentum, odio elit consequat leo, vitae ultricies mi felis eu nibh. Fusce condimentum id diam quis bibendum. Aliquam eget auctor nisi. Suspendisse eleifend sit amet libero at gravida. Cras libero enim, vulputate a nunc non, vulputate bibendum tellus.</p>
-</div>
-
-<style>
-  form {
-    background-color: white;
-    padding: 10px;
-    border-radius: 5px;
-  }
-  .content {
-    font-size: 18px;
-    line-height: 2;
-  }
-</style>

package/dist/ts/tests/PopupMenu/PopupMenu.stories.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/ts/tests/PopupMenu/PopupMenu.test.d.ts

@@ -1 +0,0 @@
-import '@testing-library/jest-dom';

package/dist/ts/tests/PopupMenu/PopupMenuBody.svelte

@@ -1,34 +0,0 @@
-<script lang="ts">
-  import PopupMenu from '../../components/PopupMenu.svelte'
-  let button: HTMLElement
-
-  export let items = [
-    { value: '0', label: 'Sunday', disabled: true },
-    { value: '1', label: 'Monday' },
-    { value: '2', label: 'Tuesday' },
-    { value: '3', label: 'Wednesday' },
-    { value: '4', label: 'Thursday', disabled: true },
-    { value: '5', label: 'Friday' },
-    { value: '6', label: 'Saturday', disabled: true }
-  ]
-</script>
-
-<div class="topspacer"></div>
-<div class="container">
-  <div class="container">
-    <button data-testid="button" class="ui gold button" bind:this={button}>Popup Menu</button>
-  </div>
-  <div class="topspacer"></div>
-  <div class="container">
-    <PopupMenu buttonelement={button} {items}></PopupMenu>
-  </div>
-</div>
-
-<style>
-  .topspacer {
-    height: 20px;
-  }
-  .container {
-    position: relative;
-  }
-</style>

package/dist/ts/tests/PopupMenu/PopupMenuButtonIsParent.svelte

@@ -1,36 +0,0 @@
-<script lang="ts">
-  import PopupMenu from '../../components/PopupMenu.svelte'
-  let button: HTMLElement
-
-  export let items = [
-    { value: '0', label: 'Sunday', disabled: true },
-    { value: '1', label: 'Monday' },
-    { value: '2', label: 'Tuesday' },
-    { value: '3', label: 'Wednesday' },
-    { value: '4', label: 'Thursday', disabled: true },
-    { value: '5', label: 'Friday' },
-    { value: '6', label: 'Saturday', disabled: true }
-  ]
-</script>
-
-<div class="topspacer"></div>
-<div class="container">
-  <div class="ui gold button" bind:this={button}>
-    Popup Menu
-    <PopupMenu buttonelement={button} {items}></PopupMenu>
-  </div>
-</div>
-
-<style>
-  .topspacer {
-    height: 20px;
-  }
-  .container {
-    margin-left: 12px;
-  }
-  .button {
-    position: relative;
-    margin-left: 12px;
-    width: 210px;
-  }
-</style>

package/dist/ts/tests/PopupMenu/PopupMenuComplex.svelte

@@ -1,34 +0,0 @@
-<script lang="ts">
-  import PopupMenu from '../../components/PopupMenu.svelte'
-  let button: HTMLElement
-
-  export let items = [
-    { value: '0', label: 'Sunday', disabled: true },
-    { value: '1', label: 'Monday' },
-    { value: '2', label: 'Tuesday' },
-    { value: '3', label: 'Wednesday' },
-    { value: '4', label: 'Thursday', disabled: true },
-    { value: '5', label: 'Friday' },
-    { value: '6', label: 'Saturday', disabled: true }
-  ]
-</script>
-
-<div class="topspacer"></div>
-<div class="container">
-  <div class="container">
-    <button data-testid="button" class="ui gold button" bind:this={button}>Popup Menu</button>
-  </div>
-  <div class="topspacer"></div>
-  <div class="container">
-    <PopupMenu usePortal buttonelement={button} {items}></PopupMenu>
-  </div>
-</div>
-
-<style>
-  .topspacer {
-    height: 20px;
-  }
-  .container {
-    position: relative;
-  }
-</style>

package/dist/ts/tests/PopupMenu/PopupMenuSimple.svelte

@@ -1,36 +0,0 @@
-<script lang="ts">
-  import { hashify } from 'txstate-utils'
-  import PopupMenu from '../../components/PopupMenu.svelte'
-
-  export let showSelected = false
-  export let items = [
-    { value: '0', label: 'Sunday', disabled: true },
-    { value: '1', label: 'Monday' },
-    { value: '2', label: 'Tuesday' },
-    { value: '3', label: 'Wednesday' },
-    { value: '4', label: 'Thursday', disabled: true },
-    { value: '5', label: 'Friday' },
-    { value: '6', label: 'Saturday', disabled: true }
-  ]
-
-  let button: HTMLElement
-  let value: string
-  $: itemsByValue = hashify(items, 'value')
-  $: selected = itemsByValue[value]
-</script>
-
-<div class="topspacer"></div>
-<div class="container">
-  <button data-testid="button" class="ui gold button" bind:this={button}>Popup Menu</button>
-  <div>selected: {#if selected}{selected.value}, {selected.label}{:else}none{/if}</div>
-  <PopupMenu bind:value buttonelement={button} {items} {showSelected}></PopupMenu>
-</div>
-
-<style>
-  .topspacer {
-    height: 20px;
-  }
-  .container {
-    position: relative;
-  }
-</style>

package/dist/ts/tests/stores/deepstore.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/ts/types/index.d.ts

@@ -1,2 +0,0 @@
-export * from './CollapsingTable';
-export * from './PopupMenu';

package/dist/types/CollapsingTable.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=CollapsingTable.js.map

package/dist/types/CollapsingTable.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"CollapsingTable.js","sourceRoot":"","sources":["../../src/types/CollapsingTable.ts"],"names":[],"mappings":""}

package/dist/types/PopupMenu.js

@@ -1,3 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-//# sourceMappingURL=PopupMenu.js.map

package/dist/types/PopupMenu.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"PopupMenu.js","sourceRoot":"","sources":["../../src/types/PopupMenu.ts"],"names":[],"mappings":""}

package/dist/types/index.js

@@ -1,15 +0,0 @@
-"use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    Object.defineProperty(o, k2, { enumerable: true, get: function() { return m[k]; } });
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __exportStar = (this && this.__exportStar) || function(m, exports) {
-    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-__exportStar(require("./CollapsingTable"), exports);
-__exportStar(require("./PopupMenu"), exports);
-//# sourceMappingURL=index.js.map

package/dist/types/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/types/index.ts"],"names":[],"mappings":";;;;;;;;;;;;AAAA,oDAAiC;AACjC,8CAA2B"}

package/docs/CollapsingTable.md

@@ -1,79 +0,0 @@
-# Collapsing Table
-
-This component is meant to help make tables responsive by eliminating columns (from the right) as the screen width reduces. When there are hidden columns, the last column header becomes a dropdown button allowing the selection of another column to be displayed instead.
-
-# Usage
-
-The only required prop is an `items` array of objects. Column headers will automatically be detected from object keys if no column configuration is present.
-
-## Column Configuration
-
-A `config` prop allows you to pass an array of column definitions. If passed, only these columns will appear, other keys in your `items` objects will be ignored.
-
-### Variables accepted for each column
-
-* `key: string` corresponds to object key in your `items` objects
-* `title?: string` a display name for this column's header
-* `width?: number` a guess at how wide in pixels this column will be; helps decide when to hide
-                   columns, default 150
-* `neverhide?: boolean`<br>
-  setting to make sure this column is never hidden; good to set on
-  the column that is most identifying for each row, like a name.
-  by default the leftmost column will stick around as identifying
-* `bodyCellClass?: string` CSS class to set on `td` elements in the body area
-* `headerCellClass?: string` CSS class to set on `td` elements in the header row
-
-## Optional Props
- * `tableClass` CSS class for the `table`
- * `bodyRowClass` CSS class for `tr` in the body area
- * `bodyCellClass` CSS class for `td` in the body area, additional to the one set in column config
- * `headerRowClass` CSS class for `tr` on the header row
- * `headerCellClass` CSS class for `th` in the header row, additional to the one set in column config
- * `menuClass` CSS class for the `ul` dropdown menu
- * `menuItemClass` CSS class for `li` in the dropdown menu
- * `menuItemHilitedClass` CSS class for `li` in the dropdown menu when they are currently hilited/active
- * `defaultCellWidth`, guess for any column width in pixels, allows you to hide columns earlier/later, default 150
-
-## Slots
-Lots of slots are provided for extra configuration.
-
-### Default Slot
-The default slot is used for each table cell in the body area. It is optional and falls back to {value}.
-Because of the way slots work, your slot content will be executed in every cell. So if you need to do
-something special for just one cell, you have to use an if/else block to identify the special cell,
-falling back to {value} for everything else:
-```svelte
-<CollapsingTable items={myItems} let:item let:key let:value>
-  {#if key === 'myspecialkey'}
-    <MySpecialComponent>{value}</MySpecialComponent>
-  {:else}
-    {value}
-  {/if}
-</CollapsingTable>
-```
-The slot props are `item`, `key`, and `value`.
-### Header Cell Slot
-A slot named `headercell` allows you to do the same thing for cells in the header row that the
-default slot allows for body cells.
-```svelte
-<CollapsingTable items={myItems} let:column let:key let:title>
-  <div slot="headercell">
-    {#if key === 'myspecialkey'}
-      <MySpecialComponent>{title}</MySpecialComponent>
-    {:else}
-      {title}
-    {/if}
-  </div>
-</CollapsingTable>
-```
-The slot props are `column`, `key`, and `title`. `column` is the configuration object for the
-current column, `title` is `column.title || column.key`. The title/key will be used as fallback
-content if you do not specify a header slot.
-### Dropdown Icon Slot
-A slot is provided for you to provide a custom icon for the column header that is serving as the
-dropdown button.
-```svelte
-<CollapsingTable items={myItems}>
-  <i type='fa caret-down' slot="dropicon" aria-hidden="true"></i>
-</CollapsingTable>
-```

package/docs/ConditionalWrapper.md

@@ -1,35 +0,0 @@
-# Conditional Wrapper
-Sometimes you want to wrap a complex bit of HTML in a certain element based on a condition,
-and not wrap it at all if the condition isn't met. Without help, this situation results in a
-lot of duplicate code because you have to have an if/else block outside the whole thing, and
-the complex HTML goes in both branches:
-```svelte
-{#if shouldwrap}
-  <div class="wrapper">
-    ... a whole bunch of html ...
-  </div>
-{:else}
-  ... a whole bunch of html, again ...
-{/if}
-```
-With this component, you can de-duplicate like this:
-```svelte
-<ConditionalWrapper class="wrapper" condition={shouldwrap}>
-  ... a whole bunch of html ...
-</ConditionalWrapper>
-```
-Any props you provide (except the ConditionalWrapper props like `condition`) will pass through
-to the wrapper element/component, if it gets inserted.
-
-## Props
-* `condition: boolean|undefined` (required) - Whether or not to wrap the element. Accepts `undefined`
-  for convenience when evaluating presence of an optional variable.
-* `component?: SvelteComponent` (optional) - The wrapper will be a svelte component instead of a DOM
-  element. Props all get passed through.
-* `a: boolean` (optional) - The wrapper will be a link element.
-* `span: boolean` (optional) - The wrapper will be a span element.
-* `element?: HTMLElement` (for binding) - If the wrapper is a DOM element, bind this prop to get a
-  reference to wrapper element (if it exists). If the wrapper is a svelte component, this will be
-  passed to it as a prop so that the wrapper component can bind it to a DOM element.
-
-If none of `a`, `span`, or `component` props are specified, the default is to create a `div` wrapper.

package/docs/Modal.md

@@ -1,63 +0,0 @@
-# Modal
-The Modal component is designed to block out the screen and focus the user on the content inside the Modal.
-
-It provides only the backdrop and a scrollable container for your content. If your content should have a background color, be sure to add it yourself.
-
-Any time the Modal is in the DOM, it will take over the screen. You make it go away by removing it from the DOM.
-
-## Example Usage
-```svelte
-<script>
-  let showMyModal = false
-</script>
-<button on:click={() => showMyModal = true}>Show Modal</button>
-{#if showMyModal}
-  <Modal on:escape={() => showMyModal = false}>
-    This is a modal dialog!
-  </Modal>
-{/if}
-<style>
-  :global(.modal-container) { background: white; }
-</style>
-```
-## Custom Events
-* `on:escape` - dispatched when the user does something that would normally dismiss a modal, such as clicking in the darkened backdrop or pressing the Escape key. You should listen for this and dismiss your modal. If you do not listen for this event, users will only be able to escape by some other means provided within your content. Be careful not to trap them!
-
-## Props
-* `opaque: boolean` (default `false`) - Make the backdrop completely opaque so that it cannot be seen through. This is a more jarring experience for users but sometimes you don't want background content to be visible at all.
-* `containerClass: string` (default `''`) - A class to be added to the scrollable container inside the backdrop. This container will always have the `.modal-container` class regardless of this prop.
-* `escapable: boolean` (default `true`) - Let screen readers know that they can escape the modal by pressing the Escape key. If you are not listening for `on:escape` then you should set this `false` to avoid giving screen reader users false information.
-* `hidefocus: boolean` (default `true`) - Focus must be moved to the modal when it opens, in order to maintain accessibility. This component avoids making the focus visible to users by default as it might be visually disconcerting. So on mount, focus is moved to an invisible element above your content. If you prefer focus to be visible to users, set this to `false` and focus will automatically be moved to the first element in your content that has a tabindex and therefore be visible to users. This prop is overridden if you provide an `initialfocus`.
-* `hidefocuslabel: string` (default `focus is above modal dialog, start tabbing`) - The message that will be read out to users using a screen reader when the focus is on the invisible element created by the `hidefocus` prop.
-* `initialfocus: string` (default `undefined`) - A selector to be used to locate and set focus on an element in your content, on mount. Use if you want focus on a specific element when the modal opens. Overrides `hidefocus`.
-* `returnfocusto: HTMLElement` (default element that had focus was when modal opened) - Use to control where focus moves when the modal closes. If not provided, component automatically saves the element that had focus on mount. Usually it's the button that triggered the modal.
-
-# FocusLock
-The FocusLock component is for creating accessible modal dialogs that do not have a darkened backdrop. It shares many props and behaviors with Modal because the Modal component uses a FocusLock itself.
-
-Any time the FocusLock is in the DOM, it will lock screen readers inside it. You release them by removing it from the DOM. Regular users are NOT trapped and may interact with other screen elements. When they do, the `escape` event will be fired, allowing you to remove the dialog.
-
-FocusLocks can be nested. The user will be trapped inside the deepest FocusLock present in the DOM. When it goes away, they'll be trapped inside the previous FocusLock, and so on.
-
-## Custom Events
-* `on:escape` - dispatched when the user does something to dismiss the dialog, such as pressing the Escape key or clicking outside the dialog area. You should listen for this and remove the FocusLock. If you do not listen for this event, users will only be able to escape by some other means provided within your content. Be careful not to trap them!
-
-## Example Usage
-```svelte
-<script>
-  let showMyDialog = false
-</script>
-<button on:click={() => showMyDialog = true}>Show Dialog</button>
-{#if showMyDialog}
-  <FocusLock on:escape={() => showMyDialog = false}>
-    Screen readers cannot escape this!
-    <button on:click={() => showMyDialog = false}>Collapse Dialog</button>
-  </FocusLock>
-{/if}
-```
-## Props
-* `escapable: boolean` (default `true`) - Controls whether the focus lock can be easily escaped by pressing the Escape key or clicking the invisible focus (see `hidefocus`). If you set this `false` you must provide a way to dismiss the lock inside your content or screen readers will be trapped.
-* `hidefocus: boolean` (default `true`) - Focus must be moved to the modal when it opens, in order to maintain accessibility. This component avoids making the focus visible to users by default as it might be visually disconcerting. So on mount, focus is moved to an invisible element above your content. If you prefer focus to be visible to users, set this to `false` and focus will automatically be moved to the first element in your content that has a tabindex and therefore be visible to users. This prop is overridden if you provide an `initialfocus`.
-* `hidefocuslabel: string` (default `focus is above modal dialog, start tabbing`) - The message that will be read out to users using a screen reader when the focus is on the invisible element created by the `hidefocus` prop.
-* `initialfocus: string` (default `undefined`) - A selector to be used to locate and set focus on an element in your content, on mount. Use if you want focus on a specific element when the lock mounts. Overrides `hidefocus`.
-* `returnfocusto: HTMLElement` (default element that had focus was when focuslock mounted) - Use to control where focus moves when the lock ends. If not provided, component automatically saves the element that had focus on mount. Usually it's the button that triggered the dialog.

package/docs/PopupMenu.md

@@ -1,31 +0,0 @@
-# PopupMenu
-
-This component is meant to display a menu of options to the user, activated by clicking
-any element. It can also be controlled from the parent, by binding the `menushown` boolean.
-
-## Props
-* `buttonelement: HTMLElement` (required) - The DOM element that will act as the "button" for this menu. The menu will be placed next to the button and be controlled by the button. Keyboard access will be enabled when the button has focus. This component adds all appropriate attributes (tabindex, roles, and aria) automatically.
-* `items: PopupMenuItem[]` (required) - The list of menu items to be shown. Parent may change this at any time based on user activity.
-* `menushown?: boolean` (default `false`) - Bind this prop to track/change the visible state of the menu from the parent.
-* `value?: string` (default no selection) - Bind this prop to track/change the currently selected value from the parent.
-* `align?: GlueAlignOpts` (default `auto`) - Control where the menu will appear. Default is to use the current viewport to make a decision to maximize potential for menu growth.
-* `cover?: boolean` (default `false`) - When the menu is active, should it cover the button or be rendered above/below it?
-* `showSelected?: boolean` (default `true`) - When an item is currently selected, should it appear in the menu (with a visual indicator), or simply be removed from the list (showSelected: `false`)?
-* `width?: string` (default `undefined`) - When defined, this width will be passed through to the menu's CSS width. Use a valid CSS dimension such as `33em` or `159px`. Generally this will be used when you need to match the menu width to something else, like the button. If the width is static like `100%` a simple CSS rule is likely more efficient.
-* `computedalign: readable<{ valign: 'top'|'bottom', halign: 'left'|'right' }>` (default store is provided) - Bind this prop to receive a store that is updated each time a menu placement decision is made. Example of when this is useful is when you are trying to round corners of your button and need to know whether the menu is above or below your button so you know which corners to round and which to leave square. Note that the values do not update when the menu is hidden, so you may need to rely on `menushown` as well.
-* `usePortal?: HTMLElement|true` (default `false`) - If the menu would be clipped by an `overflow: hidden`, you can set this prop and it will be placed in the specified container, or the `document.body` if you simply say `true`. Placement will still be calculated correctly, unless there are scrolling containers between the button and the menu.
-* `emptyText?: string` (default `¯\_(ツ)_/¯`) - When there are no items (e.g. it's a filtered search and there were no results), we still display one disabled item in the menu to let the user know what is going on. Use this prop to specify the message.
-* `menuContainerClass?: string` (default `''`) - CSS class to pass through so you can do extra styling work
-* `menuClass?: string` (default `''`) - CSS class to pass through so you can do extra styling work
-* `menuItemClass?: string` (default `''`) - CSS class to pass through so you can do extra styling work
-* `menuItemHilitedClass?: string` (default `''`) - CSS class to pass through so you can do extra styling work
-* `menuItemSelectedClass?: string` (default `''`) - CSS class to pass through so you can do extra styling work
-
-## Events
-* `on:change` - Dispatched any time a new value is selected. Does not fire when you change the `value` property from the outside. Event detail will be the full PopupMenuItem object that was selected.
-
-## Types
-* `PopupMenuItem: { value: string, label?: string, disabled?: boolean }` - Each item must have a unique non-empty value. Display label is optional, as is a `disabled` status that will show the item in the list but not allow users to hilite or select it.
-
-## Disabling
-Since there are so many different possibilities for the button you attach to, the PopupMenu does not have a `disabled` prop. If the PopupMenu should be disabled, simply remove it from the DOM with an `{#if}` block. Remember to also set `aria-disabled` on your button and likely provide some visual indicators like `cursor: default` or the `disabled` attribute on elements that support it.

package/docs/ScreenReaderOnly.md

@@ -1,10 +0,0 @@
-# ScreenReaderOnly
-This component is for adding text that can be read to screen readers while remaining
-invisible to regular users. It accepts `arialive` and `ariaatomic` props to pass through to
-the corresponding HTML attributes. It also accepts an `id` prop in case you need to
-point at it with an aria-describedby attribute on some other element.
-
-Using this component is often better than using aria-label because aria-label still has poor support
-and sometimes is not good enough to make WAVE happy with an empty icon-link. It's also a
-good way to add additional text when sighted users have a little text already, e.g. to add
-interactivity instructions.

package/docs/actions.md

@@ -1,84 +0,0 @@
-# Actions
-
-## use:buttonify
-This action turns any HTML element into an accessible button that responds to keyboard events and has
-role="button" and the tabindex attribute set. You are still responsible for making sure it has
-readable content or a good label. Does NOT change styling at all.
-```svelte
-<div use:buttonify on:click={onClick}>You can tab to me and click me with the Enter key</div>
-```
-
-## use:glue
-This action glues the element it is placed on to the target specified, with a specified alignment
-option. It is most useful for dropdown or autocomplete menus.
-
-The element should have `position: absolute` on it already. It is not moved to a new place in the DOM,
-it just gets `top`/`left`/`bottom`/`right` properties set.
-
-If you have problems with the glued element being clipped by a parent with `overflow: hidden`, you
-may combine it with the `use:portal` action to move it somewhere else; `use:glue` will recalculate
-for the new location.
-
-If you do not specify an `align` setting, the default is `auto`, which will evaluate the current
-viewport and determine which alignment gives the glued element the most space to grow.
-```svelte
-<button bind:this={menubutton}>Activate Menu</button>
-<ul use:glue={{ target: menubutton, align: 'bottomright' }}>
-  <li>Menu Item 1</li>
-  <li>Menu Item 2</li>
-</ul>
-```
-
-## use:offset
-This action allows you to observe any DOM element's position in the body. You pass in a svelte store
-and it will be updated when the element moves.
-
-Another configuration option is `debounce: number`, which will debounce the updates for the specified
-number of milliseconds. Use this option if you will make a complicated calculation after each update and do not
-want to perform the calculation multiple times during a single animation or while the user is resizing
-their viewport/window. It will defer the updates until the animation or resizing stops for at least `debounce`
-milliseconds.
-```svelte
-<script>
-  const offset = writable({ top: 0, left: 0, bottom: 0, right: 0 })
-</script>
-<div use:offset={{ store: offset }}>distance between me and body top is {$offset.top}</div>
-```
-
-## use:portal
-This action allows you to move an element to a new place in the DOM upon mount. It's useful when your component
-is sensitive to getting clipped by parents with overflow: hidden or for anything like a modal or toast message
-that needs to be positioned relative to the body, but created within a smaller component, like a web form.
-
-For convenience, the default is to move it to `document.body` when you `use:portal` without any config:
-```svelte
-<div use:portal>I'm in the body now!</div>
-```
-If you are accepting an optional target as a prop, this may cause unexpected behavior where your parent component
-declines to pass a portal target, but your element ends up in `document.body`. To prevent this, you may pass `null`
-instead of `undefined`, and the element will stay where it was before the change to `null`:
-```svelte
-<script>
-  export let portaltarget = undefined
-</script>
-<div use:portal={portaltarget || null}></div>
-```
-
-## use:resize
-This action allows you to observe an element's width and height with the `ResizeObserver`. Svelte has a built-in
-`bind:clientWidth` functionality, but it works by inserting an invisible iframe into the DOM for each observation,
-which is a little ugly and potentially slow.
-
-You pass in a svelte store and it will be updated when the element's size changes.
-
-Another configuration option is `debounce: number`, which will debounce the updates for the specified
-number of milliseconds. Use this option if you will make a complicated calculation after each update and do not
-want to perform the calculation multiple times during a single animation or while the user is resizing
-their viewport/window. It will defer the updates until the animation or resizing stops for at least `debounce`
-milliseconds.
-```svelte
-<script>
-  const size = writable({ clientWidth: 100, clientHeight: 100, offsetWidth: 100, offsetHeight: 100 })
-</script>
-<div use:offset={{ store: size }}>My dimensions are {$size.offsetWidth}x{$size.offsetHeight}</div>
-```