Quote Originally Posted by Bearfot View Post
what is the difference between providing arguments in the New_c.WebView2(...) compared to BindTo(...)?
None ...
The only difference is, that the optional timeout-param is a bit shorter (5sec) behind New_c, than in BindTo (8sec) -
though this might exactly be the difference on some older (slower) machines between the two calls.
I have corrected that timeout-difference in the cConstructor-call to 8sec now (to match with BindTo).

Quote Originally Posted by Bearfot View Post
I.e. adding userDataFolder and additionalBrowserArguments seems only have to affect in BindTo(),
All the Params are just "routed through" to BindTo, as they come in via New_c.WebView2 -
(the only exception - as said - being a different timeout, when you leave this param-slot free).

Quote Originally Posted by Bearfot View Post
and also it seems ...
I can't just provide the additionalBrowserArguments without also specifying a userDataFolder.
If userDataFolder is left empty or as an empty string, BindTo will fail.
If userData is left empty, the BindTo-call will internally not "leave it that way", but initialize it to:
If Len(userDataFolder) = 0 Then userDataFolder = New_c.FSO.GetLocalAppDataPath
(which resolves e.g. on my Win10 to: C:\Users\Olaf\AppData\Local)

Perhaps certain commandline-arguments only work with certain UserDataFolder-Paths
(which might also depend on the OS-version you are using - I've heard of Users who have had problems on Win7)...

As for your earlier question... I think "finding the right HTML5" (and Css- or style-attributes)
is in the responsibility of the Users of this control-binding (to not blow this thread here "out of proportion") -
and would suggest to post your HTML-questions in a better matching Forum (or SubForum on this site).

HTH

Olaf