Web Browser Widget cannot open Figma Pages

Development Asset Creation
, ,
1

Hello,

I am trying to load a Figma Page via the Web Browser Widget, but it shows the following error message:[Image Removed]

Is there a way to fix this issue ?

Best

Dominic

2

Steps to Reproduce

  1. Create a Widget Component and use a Widget with a WebBrowser
  2. Publish your Figma design as website
  3. Try to load your Figma web site
3

The log states

Loaded CEF3 version 90.6.7.2358 from C:/Program Files/Epic Games/UE_5.5/Engine/Binaries/ThirdParty/CEF3/Win64Which is an over 4 years old chromium version😕

I will try if I can replace the lib with a newer one, but I guess that the interfaces has changed quite a bit.

Is it possible to put the newer lib in one of our project directories ? Its linked like this in CEF3Utils.Build.cs

AddEngineThirdPartyPrivateStaticDependencies(Target,
				"CEF3"
				);

Best

Dominic

4

I was not able to exchange the Binaries for CES.

CEF3.build.cs is linking statically against a defined version and exchanging only UE_5.5\Engine\Binaries\ThirdParty\CEF3\Win64 will result in a crash on engine startup, I guess the version differ too much.

Is there any other way to update the CES version except for doing a source build and fixing all incompatibilities with the newer version ?

Note: in 5.7 the version is updated to 128.x , current version would be a 139.x :confused:

5

Hi,

I’m not sure you’ll be able to update CEF easily without a source build, as you’ll need to also rebuild EpicWebHelper to align with the new binaries. The 128 binaries should also be in 5.6 if you plan to upgrade, though note that it’s currently opt-in. In order to switch to the updated binaries:

  1. Modify CEF3.build.cs to set bUseExperimentalVersion=true for the desired platform
  2. Rebuild EpicWebHelper in the Shipping Editor configuration

[This [Content removed] has some information about backporting those changes if you decide to go with that approach. I did a quick test against some of the sample sites listed here in v99 vs. v128 and can confirm that they were broken in v99 and working properly in v128, though note that the browser performance is a limiting factor for some.

Best,

Cody