- This adds two custom events,
include-fragment-replaceandinclude-fragment-replaced. See details at #59.
Assets
2
- Convert to TypeScript/remove Flow type support.
- Package is now type module. UMD build is removed.
Assets
2
- use
.includes(..)instead of.match(..)to identify accept header (#56)
Assets
2
- Add type to HTMLElementTagNameMap in typescript declaration file (#55)
Assets
2
Add support for an optional <include-fragment accept=""> attribute for specifying the Accept header for fetch requests. #51.
Assets
2
- types(ts): fix window declaration type a4a8aa6
Assets
2
- types(TS): add window declaration c726aee
Assets
2
<include-fragment> element
A Client Side Includes tag.
Installation
$ npm install --save @github/include-fragment-element
Usage
All include-fragment elements must have a src attribute from which to retrieve an HTML element fragment.
The initial page load should include fallback content to be displayed if the resource could not be fetched immediately.
import '@github/include-fragment-element'Original
<div class="tip">
<include-fragment src="/tips">
<p>Loading tip…</p>
</include-fragment>
</div>On page load, the include-fragment element fetches the URL, the response is parsed into an HTML element, which replaces the include-fragment element entirely.
Result
<div class="tip">
<p>You look nice today</p>
</div>The server must respond with an HTML fragment to replace the include-fragment element. It should not contain another include-fragment element or the server will be polled in an infinite loop.
Errors
If the URL fails to load, the include-fragment element is left in the page and tagged with an is-error CSS class that can be used for styling.
Events
Request lifecycle events are dispatched on the <include-fragment> element.
loadstart- The server fetch has started.load- The request completed successfully.error- The request failed.loadend- The request has completed.
const loader = document.querySelector('include-fragment')
const container = loader.parentElement
loader.addEventListener('loadstart', () => container.classList.add('is-loading'))
loader.addEventListener('loadend', () => container.classList.remove('is-loading'))
loader.addEventListener('load', () => container.classList.add('is-success'))
loader.addEventListener('error', () => container.classList.add('is-error'))Options
| Attribute | Options | Description |
|---|---|---|
src |
URL string | Required URL from which to load the replacement HTML element fragment. |
Deferred loading
The request for replacement markup from the server starts when the src attribute becomes available on the <include-fragment> element. Most often this will happen at page load when the element is rendered. However, if we omit the src attribute until some later time, we can defer loading the content at all.
The <details-menu> element uses this technique to defer loading menu content until the menu is first opened.
Patterns
Deferring the display of markup is typically done in the following usage patterns.
-
A user action begins a slow running background job on the server, like backing up files stored on the server. While the backup job is running, a progress bar is shown to the user. When it's complete, the include-fragment element is replaced with a link to the backup files.
-
The first time a user visits a page that contains a time-consuming piece of markup to generate, a loading indicator is displayed. When the markup is finished building on the server, it's stored in memcache and sent to the browser to replace the include-fragment loader. Subsequent visits to the page render the cached markup directly, without going through a include-fragment element.
Relation to Server Side Includes
This declarative approach is very similar to SSI or ESI directives. In fact, an edge implementation could replace the markup before its actually delivered to the client.
<include-fragment src="/github/include-fragment/commit-count" timeout="100">
<p>Counting commits…</p>
</include-fragment>A proxy may attempt to fetch and replace the fragment if the request finishes before the timeout. Otherwise the tag is delivered to the client. This library only implements the client side aspect.
Browser support
Browsers without native custom element support require a polyfill. Legacy browsers require various other polyfills. See examples/index.html for details.
- Chrome
- Firefox
- Safari
- Microsoft Edge
Development
npm install
npm test
License
Distributed under the MIT license. See LICENSE for details.