On 11/24/24 5:28 AM, Kirill A. Korinsky wrote:
> On Sun, 24 Nov 2024 13:57:53 +0100,
> Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
>> On Sun, Nov 24, 2024 at 12:07:31PM +0100, Kirill A. Korinsky wrote:
>>> On Sun, 24 Nov 2024 11:36:13 +0100,
>>> Antoine Jacoutot <ajacoutot@bsdfrog.org> wrote:
>>>> To enable Webassembly in chromium you need to:
>>>> export ENABLE_WASM=1
>>>>
>>>> Maybe it should be documented somewhere...
>>>>
>>> I think that somethig like this in README
>>>
>>>          Web Assemble support:
>> Isn't it called WebAssembly? (or Wasm)
>>
> Yes, it is.
>
>>>          - some web applications and "not a bot" verification require support for
>>>          Web Assemble, which is disabled by default and can be enabled by adding
>>>          ENABLE_WASM=1 to used environment variables.
>>>
>>> answers that questions.
>>>
>>> But increase revision for all chromes only for update readme looks as waste
>>> of tons of resources.
>> I don't understand what you mean.
>>
> after some discussion with tb@ here a diff which increases revision as well.
>
> Index: www/chromium/Makefile
> ===================================================================
> RCS file: /home/cvs/ports/www/chromium/Makefile,v
> diff -u -p -r1.814 Makefile
> --- www/chromium/Makefile	20 Nov 2024 17:21:08 -0000	1.814
> +++ www/chromium/Makefile	24 Nov 2024 13:21:41 -0000
> @@ -11,6 +11,7 @@ DPB_PROPERTIES+=	lonesome
>   COMMENT=		Chromium browser
>   
>   V=			131.0.6778.85
> +REVISION=		0
>   
>   DISTNAME=		chromium-${V}
>   
> Index: www/chromium/pkg/README
> ===================================================================
> RCS file: /home/cvs/ports/www/chromium/pkg/README,v
> diff -u -p -r1.4 README
> --- www/chromium/pkg/README	11 Mar 2022 20:09:41 -0000	1.4
> +++ www/chromium/pkg/README	24 Nov 2024 13:20:57 -0000
> @@ -41,3 +41,8 @@ Interoperability with base window manage
>   - some window managers do not have compositing support; for instance, fvwm.
>   In order to have decent graphic rendering, they should be supplemented by
>   a compositing manager. For instance, xcompmgr in base.
> +
> +WebAssembly support:
> +- some web applications and "not a bot" verification requires support
> +for WebAssembly, which is disabled by default and can be enabled by
> +adding ENABLE_WASM=1 to used environment variables.
> Index: www/iridium/Makefile
> ===================================================================
> RCS file: /home/cvs/ports/www/iridium/Makefile,v
> diff -u -p -r1.210 Makefile
> --- www/iridium/Makefile	7 Nov 2024 14:45:06 -0000	1.210
> +++ www/iridium/Makefile	24 Nov 2024 13:21:51 -0000
> @@ -12,6 +12,7 @@ DPB_PROPERTIES+=	lonesome
>   COMMENT=		Iridium browser
>   
>   V=			2024.10.130.2
> +REVISION=		0
>   
>   DISTNAME=		iridium-browser-${V}
>   PKGNAME=		iridium-${V}
> Index: www/iridium/pkg/README
> ===================================================================
> RCS file: /home/cvs/ports/www/iridium/pkg/README,v
> diff -u -p -r1.2 README
> --- www/iridium/pkg/README	11 Mar 2022 20:10:00 -0000	1.2
> +++ www/iridium/pkg/README	24 Nov 2024 13:22:02 -0000
> @@ -41,3 +41,8 @@ Interoperability with base window manage
>   - some window managers do not have compositing support; for instance, fvwm.
>   In order to have decent graphic rendering, they should be supplemented by
>   a compositing manager. For instance, xcompmgr in base.
> +
> +WebAssembly support:
> +- some web applications and "not a bot" verification requires support
> +for WebAssembly, which is disabled by default and can be enabled by
> +adding ENABLE_WASM=1 to used environment variables.
> Index: www/ungoogled-chromium/Makefile
> ===================================================================
> RCS file: /home/cvs/ports/www/ungoogled-chromium/Makefile,v
> diff -u -p -r1.144 Makefile
> --- www/ungoogled-chromium/Makefile	20 Nov 2024 18:24:55 -0000	1.144
> +++ www/ungoogled-chromium/Makefile	24 Nov 2024 13:24:24 -0000
> @@ -13,6 +13,7 @@ COMMENT=		Chromium browser sans integrat
>   
>   V=			131.0.6778.85
>   UGV=			${V}-1
> +REVISION=		0
>   
>   DISTNAME=		ungoogled-chromium-${V}
>   
> Index: www/ungoogled-chromium/pkg/README
> ===================================================================
> RCS file: /home/cvs/ports/www/ungoogled-chromium/pkg/README,v
> diff -u -p -r1.1.1.1 README
> --- www/ungoogled-chromium/pkg/README	4 Oct 2022 12:56:00 -0000	1.1.1.1
> +++ www/ungoogled-chromium/pkg/README	24 Nov 2024 13:22:12 -0000
> @@ -41,3 +41,8 @@ Interoperability with base window manage
>   - some window managers do not have compositing support; for instance, fvwm.
>   In order to have decent graphic rendering, they should be supplemented by
>   a compositing manager. For instance, xcompmgr in base.
> +
> +WebAssembly support:
> +- some web applications and "not a bot" verification requires support
> +for WebAssembly, which is disabled by default and can be enabled by
> +adding ENABLE_WASM=1 to used environment variables.
>
>
Thank you both for that. Yes, I did not see any part of

'export ENABLE_WASM=1' in chromium's package readme.


With that applied in ~/.profile, login to https://vault.bitwarden.com
worked fine, with noted exception below.

Logging in on the Bitwarden extension gave a new error after
entering the correct password.

"An error has occurred
Attempting to use disconnected port object."

When I typed the wrong password, the extension successfully reported
'incorrect password'. It didn't even do that before.

Using 'chrome --enable-wasm' with the variable set gives the same
result. It looks like the environment variable has replaced the command
flag. That is fine.

I removed and re-installed the Bitwarden extension and that resolved
the 'disconnected port object' error.

This works with chrome launched from the shell. Launching from the CWM
Alt-Shift-? 'exec program' menu returns the original error for the website
and extension: webassemby required.

Does this mean chromium does not pickup the .profile environment when
launched outside the shell?

This tested with the same result on:
- 7.5
- 7.6-release
- 7.6-beta from August 10th 2024

- And that same -beta install upgraded to today's November 24th snapshot

This is a lot better! But how can I get chromium to pick up the shell
environment to get webassembly when launched from the window manager's

menu and not from the shell?