async function onAjaxedPagesRaw(callback) {
	await onDomReady;
	document.addEventListener('pjax:end', callback);
	callback();
}
/*
 * When navigating back and forth in history, GitHub will preserve the DOM changes;
 * This means that the old features will still be on the page and don't need to re-run.
 * For this reason `onAjaxedPages` will only call its callback when a *new* page is loaded.
 *
 * Alternatively, use `onAjaxedPagesRaw` if your callback needs to be called at every page
 * change (e.g. to "unmount" a feature / listener) regardless of of *newness* of the page.
 */
When navigating back and forth in history, GitHub will preserve the DOM changes;
This means that the old features will still be on the page and don't need to re-run.
For this reason `onAjaxedPages` will only call its callback when a *new* page is loaded.

Alternatively, use `onAjaxedPagesRaw` if your callback needs to be called at every page
change  regardless of of *newness* of the page.
When navigating back and forth in history GitHub will preserve the DOM changes ; This means that the old features will still be on the page and don ' t need to re - run . For this reason ` onAjaxedPages ` will only call its callback when a * new * page is loaded . Alternatively use ` onAjaxedPagesRaw ` if your callback needs to be called at every page change regardless of of * newness * of the page .
async function onAjaxedPagesRaw(callback) {
	await onDomReady;
	document.addEventListener('pjax:end', callback);
	callback();
}
async function onAjaxedPagesRaw ( callback ) { await onDomReady ; document . addEventListener ( 'pjax:end' , callback ) ; callback ( ) ; }
When navigating back and forth in history, GitHub will preserve the DOM changes;
 This means that the old features will still be on the page and don't need to re-run.
When navigating back and forth in history GitHub will preserve the DOM changes ; This means that the old features will still be on the page and don ' t need to re - run .