|
|
Rank: Newbie
Groups: Member
Joined: 3/7/2016
Posts: 8
|
Dear support team, is there an equivalent to the Tab.audible property (see https://developer.chrome.com/extensions/tabs) available in EOWebBrowser? I need to detect, if a WebView is playing audio. Thanks for your help! Best regards, Christoph
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Unfortunately no. There is no way for you to get this information. Our product only includes the browser engine part, not the tab system. The audible status is not exposed either.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 3/7/2016
Posts: 8
|
Hmm, I was expecting this, but hoped for an alternative. Do you think, you will implement this for a single WebView in the near future? Or is this at all possible using the Chromium infrastructure?
Thanks,
Christoph
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
We can put this on our list but I do not think this is our priority since it involves not only just the tab system that is completely missing but also various interface that interacts with them. So the amount of code changes required and the risk of breaking something else would out weight the benefit here. As such I do not see it being implemented in the near future. Sorry about it!
|
|
Rank: Newbie
Groups: Member
Joined: 3/7/2016
Posts: 8
|
Actually, I'm not interested in the tab system itself. I just need to know, if the WebView is playing sound or not. I just mentioned the tab system, since it was the only place where I found the information exposed in the chrome api. A simple 'Audible' property on the WebView would be enough for my use case.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
We understand that you do not need the tab system. But in Chromium's code base those two parts are tied together. We can not just cut one single piece out for a single customer because it will quickly become unmanageable for us if we were to do it that way. That leave the only option being isolate the whole interface layer from the UI, which is not trivial at this point.
|
|