Weird differences between headless and headful mode

[o0101]

Few people would encounter this (as headful mode can only be turned on by setting an environment variable), but I notice that some things seem to break in headful mode:

• it looks like some of our injected scripts are not loaded sometimes when we activate a tab in headful mode.
• sometimes but not always, screenshots of a tab do not work, and no info is provided about this by the debug log (there are no entry for shots when there should be), when we activate a tab.

It could be a weird issue with somehow these commands are being dropped because their session does not match the currently active session we have on record, but why that would differ between headless and headful (except maybe some timing based race condition?) is unclear to me now.

But I would expect the debug log to show "X dropped as session is not active/does not exist" But instead it's like those commands are not even being sent.

So it could be an issue on the client side.

I really have no idea what causes this difference right now. It's very weird. Issue not showing AT ALL when we run in headless mode, but it headful mode it happens, about 75% of the time.

😆 🤷‍♂