If more than one browser tab is open with your web app, we will always display the console logs coming from the latest active tab (or window). If the user switches tabs during a recording, the console will also switch to the new focused tab, and it will be notified in the console flow with a "Tab switch" event.
What if Birdie doesn't collect all the logs ?
Console log recording systems captures logs generated within the web page’s JavaScript context. However, certain logs that users see in the browser console may not be captured due to the following limitations:
Browser and Extension Logs: Logs generated by the browser itself (e.g., warnings, deprecation notices) or by browser extensions (e.g., ad blockers, developer tools) are beyond the scope of our page-level JavaScript and cannot be intercepted.
Cross-Origin Restrictions: Logs from scripts loaded from other origins may be restricted by browser policies (like CORS), making them inaccessible for security reasons.
Direct Browser Logs: Some browser-level errors, like network failures (net::ERR_BLOCKED_BY_CLIENT), are directly logged by the browser to the console and do not pass through JavaScript console methods, meaning they cannot be recorded by our system.
These limitations are inherent to browser security models and cannot be bypassed by standard JavaScript execution within the web page.
Network Requests
Birdie will also capture Fetch and XHR requests made during the recording.
