uBlock/platform/mv3/extension/matched-rules.html

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1">
<title>Matched rules</title>
<link rel="stylesheet" href="css/default.css">
<link rel="stylesheet" href="css/common.css">
<link rel="stylesheet" href="css/fa-icons.css">
<link rel="stylesheet" href="css/dashboard-common.css">
<link rel="stylesheet" href="css/matched-rules.css">

<link rel="shortcut icon" type="image/png" href="img/icon_64.png"/>
</head>

<body>

<div id="matchedEntries">
</div>

<template id="matchInfo">
    <div class="matchInfo">
        <span class="requestInfo"></span>
        <span class="ruleInfo"></span>
    </div>
</template>

<script src="js/theme.js" type="module"></script>
<script src="js/fa-icons.js" type="module"></script>
<script src="js/i18n.js" type="module"></script>
<script src="js/matched-rules.js" type="module"></script>
</body>
</html>
[mv3] Add minimal ability to diagnose ruleset issue A new icon has been added to the popup panel, to open a popup window with a terse list of DNR events for the current tab, in reverse chronological order (most recent DNR event appears at the top). The new ability is available only when the extension is sideloaded, as per `declarativeNetRequestFeedback` documentation. Ref: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#event-onRuleMatchedDebug Purposefully minimal, so as to have something rather than nothing when having to diagnose filtering issue with the DNR API. Example: https://github.com/uBlockOrigin/uBOL-home/issues/156 The content of the popup window does not dynamically update, force a refresh (F5) to get the most recent DNR events. This might be improved in the future. The DNR event buffer is not persisted, so the buffer is empty when service worker is restarted. This might be improved in the future by using session storage API. There is no output filtering ability in this first draft. This might be improved in the future. DNR rules are reported. The filter from which a DNR rule originates is not reported. Given that the rulesets are optimized after conversion from original filter lists to reduce the DNR rule count, this is unlikely to ever be possible. 2024-07-29 20:54:46 +02:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
			`<meta charset="utf-8">`
			`<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1">`
			`<title>Matched rules</title>`
			`<link rel="stylesheet" href="css/default.css">`
			`<link rel="stylesheet" href="css/common.css">`
			`<link rel="stylesheet" href="css/fa-icons.css">`
			`<link rel="stylesheet" href="css/dashboard-common.css">`
			`<link rel="stylesheet" href="css/matched-rules.css">`

			`<link rel="shortcut icon" type="image/png" href="img/icon_64.png"/>`
			`</head>`

			`<body>`

			`<div id="matchedEntries">`
			`</div>`

			`<template id="matchInfo">`
			`<div class="matchInfo">`
			`<span class="requestInfo"></span>`
			`<span class="ruleInfo"></span>`
			`</div>`
			`</template>`

			`<script src="js/theme.js" type="module"></script>`
			`<script src="js/fa-icons.js" type="module"></script>`
			`<script src="js/i18n.js" type="module"></script>`
			`<script src="js/matched-rules.js" type="module"></script>`
			`</body>`
			`</html>`