Custom headers not propagated with -hl after v1.4.0

[gchem1se]

From what I understood while looking through the commits, v1.4.0 changed -hl from the previous "hybrid" behavior to the new "full-headless" mode.

It looks like the new full-headless engine does not currently propagate custom headers into the browser page the same way the hybrid engine did. This may be a regression for users who relied on -hl -H ... in v1.3.0.
It would make sense for full-headless mode to apply custom headers similarly to the hybrid engine. Or, if this is intentional, maybe the docs could mention that custom headers are not injected in full-headless mode.

Also, I noticed that -hh still works, although I’m not fully sure which operational mode it maps to now. Since it seems to preserve the previous behavior, it might be worth documenting it more clearly, or removing it if it is not meant to be supported.