64bit 'HTMLTexture (String)' baseURL bug


I tested the new 64bit node HTMLTexture (EX9.Texture String) and found a bug:

The node does not render any texture at all unless you change the _ base url_ a couple of times. For the first time you enter a valid base URL the content of the base url gets rendered instead of my string i input in _ HTML_. Afterwards any _ base url_ works in order to render my _ HTML_. At the moment i use this as a workaround.

HTMLTexture(String)-bug.rar (5.5 kB)

I can remember having issues with rendering strings since moving to CEF3 and it seems to be related to https://code.google.com/p/chromiumembedded/issues/detail?id=579 - we’ll need to wait a little until they merge the proposed patch into trunk.

yap, seems to be our problem:
You need to load at least one URL before you can use LoadRequest.
For example, you can pass “about:blank” as the |url| parameter to
Once the browser has been created you can then call LoadRequest().
Though i’m wondering why i have to do it more than one-times in vvvv. Probebly there is some more happening wrong under the hood…? (see https://discourse.vvvv.org/
thanks Elias

Check latest alpha - should work now. The node uses a different technique now to load/render the HTML string.

thx elias! it is working now :)

– except if i set the base url to an empty string or ‘about:blank’.

As there is no ‘browsing context’ for HTMLTexture (EX9.Texture String), no fallback base url can be found.

But shouldn’t it work anyway as it is a special use case within vvvv? Is there a solution to catch those errors and avoid emtpy render output?

cant you tell HTMLTexture (EX9.Texture String) to use the local project or vvvv path if there is an empty (or even invalid) base URL?

Just did the following commit - alpha build containing it (ee774cff) should be available soon:

Changed the default value of BaseUrl pin in The HTMLTexture (EX9.Texture String) node.

gracias elias!