df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing>
21 lines
1.0 KiB
TypeScript
21 lines
1.0 KiB
TypeScript
import type { JSX } from 'react';
|
|
/**
|
|
* When a `nonce` is present on an element, browsers such as Chrome and Firefox strip it out of the
|
|
* actual HTML attributes for security reasons *when the element is added to the document*. Thus,
|
|
* given two equivalent elements that have nonces, `Element,isEqualNode()` will return false if one
|
|
* of those elements gets added to the document. Although the `element.nonce` property will be the
|
|
* same for both elements, the one that was added to the document will return an empty string for
|
|
* its nonce HTML attribute value.
|
|
*
|
|
* This custom `isEqualNode()` function therefore removes the nonce value from the `newTag` before
|
|
* comparing it to `oldTag`, restoring it afterwards.
|
|
*
|
|
* For more information, see:
|
|
* https://bugs.chromium.org/p/chromium/issues/detail?id=1211471#c12
|
|
*/
|
|
export declare function isEqualNode(oldTag: Element, newTag: Element): boolean;
|
|
export default function initHeadManager(): {
|
|
mountedInstances: Set<unknown>;
|
|
updateHead: (head: JSX.Element[]) => void;
|
|
};
|