Without uBlock, the button's alt-text would be 1px lower than the rest
of the nav items, and inconsistently capitalized.
With uBlock, the button would be slightly too high up.
This is on Firefox.
The solution is to apply styles on the `span` that GitHub's JS inserts.
However, using margin will make the entire nav jump during pageload, so
position: relative seems more robust there.
* Clarify event filter uses in hx-trigger
* Change hx-trigger event filter example to avoid ambiguity
input is both a tag and an event.
* Document the scope difference between standard selector and event filter
from:input listens to the page and click[event.target.matches('input')] listens to the element.
* Document that event filters as an alternative to CSS selectors require eval
* Move note about eval to standard event filters section.
* Simplify the referenced to standard event filters in the standard event modifiers section, and link to the standard event filters section instead.
* End quote in the correct place in standard event modifier doc.
* Correct language on how event filters from:body receive events.
* hx-trigger filter example catches click events specifically.
* Failing test for oob-swap within web components
* hx-swap-oob respects shadow roots
* Lint and type fixes
* fix jsdoc types for rootNode parameter
* Fix for linter issue I was confused about before
* oob swaps handle global correctly
* swap uses contextElement if available, document if not
Previous a commit made swapOptions.contextElement a required field. This
could have harmful ramifications for extensions and users, so instead,
the old behavior of assuming document as a root will be used if the
contextElement is not provided.
* rootNode parameter is optional in oobSwap
If not provided, it will fall back to using document as rootNode. jsdocs
have been updated for oobSwap and findAndSwapElements accordingly.
