github-featured/cloakhq--cloakbrowser
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

release: v0.5.3 — Windows font profile feature set + proxy identity and Windows CLI fixes

Browse Source
This commit is contained in:
CloakHQ
2026-07-30 03:13:56 +02:00
parent 7f78805b06
commit 59406d807c
7 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+2 -1
View File
@@ -6,8 +6,9 @@ Changes are tagged: **[wrapper]** for Python/JS wrapper, **[binary]** for Chromi
---
## [Unreleased]
## [0.5.3] — 2026-07-30
- **[wrapper]** When the Windows font-metrics profile is requested, the launch feature set now matches a stock Chrome install rather than Playwright's test-harness defaults, which switch off a feature stock Chrome ships enabled. Merged into any `--enable-features` value you pass instead of adding a second flag. Python, JavaScript, and .NET.
- **[wrapper]** **A second browser launched from the same Node process no longer inherits the first one's proxy identity.** When one process called `launch()` more than once with different proxies, every launch after the first reused the earlier connection to the exit-IP lookup service, because Node pools those connections by destination and the destination is the same for every proxy. The tunnel opened through the new proxy was built and then discarded, so later browsers were given the first proxy's exit IP, timezone and locale while their traffic correctly went out through their own proxy. Each launch now resolves its own exit IP. Single-launch processes were never affected. JavaScript only; Python and .NET open a fresh client per lookup.
- **[wrapper]** Fix GeoIP and WebRTC exit-IP resolution dropping the credentials of an authenticated HTTP proxy given as a settings object — `{"server": ..., "username": ..., "password": ...}` — instead of a URL with inline credentials (#469). Only SOCKS proxies kept their credentials, so the HTTP lookup was rejected and fell back to resolving the proxy gateway's hostname. That returns a real address, so resolution appeared to succeed while reporting the gateway's timezone and locale rather than the session's actual exit IP, and `--fingerprint-webrtc-ip=auto` was dropped entirely. Both forms of the same proxy now resolve identically. Python, JavaScript, and .NET.
- **[wrapper]** **`cloakbrowser info` no longer aborts partway through on a Windows console.** `cmd.exe` defaults to a code page that cannot represent the report's check mark and arrow, so the command stopped with an encoding error at the first one and the remaining diagnostics were never printed. Those marks now degrade to plain text when the console cannot take them, per character. UTF-8 consoles, including Linux, macOS and Windows Terminal, are unchanged. Python.