Datalist does not work in browser docks

[ratbo99]

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

27.1.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

*

OBS Studio Crash Log URL

No response

Expected Behavior

could use the Website as Custom Dock like in the Browser, but Datalist attribute didn't work in Dock.

Current Behavior

cant use a website with datalist as a dock

Steps to Reproduce

1.i used a node.js server for my overlay...in chrome everything is fine...but not as a dock in obs 2. 3. ...

Anything else we should know?

No response

[mihawk90]

1.i used a node.js server for my overlay...in chrome everything is fine...but not as a dock in obs

Those are not actionable steps to reproduce.

Some kind of sample HTML to test would be the minimum effort to have someone test this.

That said: obsproject/obs-browser#148

[ratbo99]

i want to use a normal website as a brwoser dock, but it seems obs can't handle datalist tags.

for example:

<label for="myBrowser">Gib einen Browsernamen ein:</label>
<input list="browsers" id="myBrowser" name="myBrowser" />
<datalist id="browsers">
  <option value="Chrome">
  <option value="Firefox">
  <option value="Internet Explorer">
  <option value="Opera">
  <option value="Safari">
</datalist>

works in a browser, but not as obs dock...you can't intereact with the datalist element in obs.

EDIT: so the bug is from 2019? nice

[WizardCM]

Datalist definitely shouldn't be broken in docks, the ticket linked above is only for browser sources.

I'll move this into the correct repo and mark it as confirmed, as I have verified the bug.

[WizardCM]

I've confirmed in cefclient that this is not limited to OBS.

[WizardCM]

Additionally, I've verified this is not fixed in CEF 90 or 94 in cefclient. Marshall has confirmed that this likely won't change https://bitbucket.org/chromiumembedded/cef/issues/906/cef3-add-html5-datalist-support#comment-60781391

[RytoEX]

Unless we switch from the CEF/Alloy runtime to the Chrome runtime, I do not see a path for us to change this. Given that we currently have no plans to do so, I'm not sure it makes sense to keep this open, so I'm going to close this for now.