A client-side includes tag.
Full Changelog: https://github.com/github/include-fragment-element/compare/v6.2.1...v6.3.0
Full Changelog: https://github.com/github/include-fragment-element/compare/v6.2.0...v6.2.1
Full Changelog: https://github.com/github/include-fragment-element/compare/v6.1.1...v6.2.0
Full Changelog: https://github.com/github/include-fragment-element/compare/v6.1.0...v6.1.1
CSP trusted types is an API that allows a website to reduce the possibility of XSS by controlling what kind of content can be placed in a "sink" like .innerHTML
.
This release introduces a flexible callback that allows the calling code to provide its own sanitization or rejection of an server response for an <include-fragment-element>
. For example, the site may want to allow the server to send a header to assert that certain HTML is sanitized and safe to use as-is, or the site may want to run the response through a sanitizer.
try
in new async code. by @lgarron in https://github.com/github/include-fragment-element/pull/83
npm run format
. by @lgarron in https://github.com/github/include-fragment-element/pull/85
setCSPTrustedTypesPolicy()
for CSP trusted types. by @lgarron in https://github.com/github/include-fragment-element/pull/81
Full Changelog: https://github.com/github/include-fragment-element/compare/v6.0.1...v6.1.0
Full Changelog: https://github.com/github/include-fragment-element/compare/v6.0.0...v6.0.1
Full Changelog: https://github.com/github/include-fragment-element/compare/v5.3.2...v6.0.0
This release fixes a bug where calling load()
on a loading=lazy
element causes the contents not to be replaced when the element becomes visible.
Thanks to @latentflip for his contributions to this release 🙌🏻
https://github.com/github/include-fragment-element/compare/v5.3.1...v5.3.2
This release guarantees the order of events. The order will now always be:
loadstart
include-fragment-replace
include-fragment-replaced
load
loadend
This release also guarantees that during the loadstart
dispatch, the <include-fragment>
element will still exist and be connected to the DOM.
This adds a new attribute: loading
. The loading
attribute is eager
by default but can be set to lazy
which will defer loading of the fragment until it is visible in the viewport. This is similar to <img loading=lazy>
.