Analyse de l'application WebPeek — Web Inspector pour le 6 octobre

WebPeek brings the four panels you already know to Safari on iPhone and iPad. Turn it on once and every page gets a small floating button; tap it and the inspector slides up over the page you are already reading. ELEMENTS • Tap the picker, then tap anything on the page to select it • A real DOM tree with syntax colouring and a breadcrumb • Edit attributes, text and outerHTML; delete nodes — all applied live • Matched CSS rules, every computed property, and a box-model diagram CONSOLE • Every console.* call captured from the very first line of the page • Uncaught errors, unhandled rejections and CSP violations, with stack traces • Expandable object trees — arrays, Maps, Sets, typed arrays, DOM nodes • An input line for running expressions, with history NETWORK • fetch, XMLHttpRequest, WebSocket, sendBeacon and EventSource, captured as they happen • Status, method, size, and a timing breakdown per request • Request and response headers, request body, response preview • Images, audio and video previewed inline • Copy as cURL, or export the whole session as a HAR file STORAGE • localStorage, sessionStorage and cookies — read, edit, add, delete • IndexedDB browser with paging, including what type each value is • Cache Storage, including what a Service Worker has cached • A usage bar for the origin BUILT FOR A PHONE • The panel lives inside the page — nothing to connect, nothing to install on a computer • Three heights, drag to resize, or a side dock on iPad • Light and dark, English, 简体中文 and 繁體中文 • Every destructive action asks first HONEST ABOUT LIMITS iOS gives Safari extensions a smaller toolbox than a desktop browser, and WebPeek says so instead of pretending. HttpOnly cookies stay invisible, pages with a strict Content-Security-Policy cannot run expressions, static files arrive without headers, and cross-origin responses only show the headers the server chose to expose. The in-app Tips screen explains each one and why. PRIVACY WebPeek reads only the page you are looking at, keeps everything on the device, and has no account, no analytics and no network calls of its own.