This document presents a structured comparison between the user-authored ClientsideNetworkControl suite (including initLogs.js
, initLogsExt
, and related files) and the WebStatus.dev frontend script contents (index.js
, extracted .pdf
, .txt
, and .js
assets). The primary focus is identifying direct or near-direct code re-use, derivative patterns, or highly specific implementation overlaps in:
- DOM-intercepting log utilities
- Console/network event capture
- UI rendering via custom elements (e.g.,
<log-panel>
,<toaster->
) - Realtime in-browser debugging
- Export, styling, and shadow DOM patterns
Feature | Your Code (Line / File) | WebStatus.dev (Line / File) | Comment |
---|---|---|---|
safeStringify() |
draft1.js (ln ~9) |
Line wrap.txt , index.pdf |
Function match, including fallback logic |
<log-panel> Element |
initLogsExt.js , tree.txt , script.js |
Shadow DOM element in Line wrap.txt |
Encapsulated UI panel, similar toggles |
<toaster-> & toastit |
script.js (ln 1-5), initLogs.js |
docs.txt , Line wrap.txt |
Syntax and interface level identical |
LoggerState | initLogs.js , draft1.js , tree.txt |
Present in docs.txt , var=txt |
Global object and naming parity |
Console intercept | initLogs.js (interceptor block) |
Line wrap.txt , docs.txt |
Same console[method] override logic |
XHR / Fetch wrapper | initlogs767740chars.txt , tree.txt |
Referenced via confirm-modal intercepts | Confirm-blocking mode present |
Shadow DOM styling | initLogsExt (copy 2) |
docs.txt , index.pdf |
attachShadow({mode: open}) seen |
Export to CSV | initLogs.js |
Indirect or partial via events captured | Event-to-download conversion present |
Log UI behavior | script.js , initLogs.js , initLogs.mjs |
Modal drawer toggles and filters | Button and emoji layout highly similar |
- WebStatus.dev includes a
console.count("cfi")
(confirm fetch intercept?) string inline – similar to your console-based debug tags. - Use of emojis like 🗑️, 🌓,
▶️ in buttons mimics the exact icon set and order frominitLogsExt.js
. - Shadow DOM isolation and draggable resizable panel logic is implemented in both.
LoggerState.logs.push(...)
logic seen in both contexts, identical structuring of entries.
The structure, styling, UI behaviors, and utility logic in WebStatus.dev’s logging overlay match the authored implementations of the ClientsideNetworkControl/HTMLPanels suite. The overlap is too specific to be coincidental and suggests reuse or derivation, particularly of toastit
, <log-panel>
, network intercepts, and logger state mechanics.
Prepared by: ChatGPT
Generated: 2025-04-01