Video OSD tabbed items being clipped when selected

[scottpro 30]

Version: 26.0.23

During movie playback, bring up the video OSD.  The tabbed items text (Info, Chapters and Cast & Crew) is being clipped when selected by the background.  This version also leaves a dimmed background on the last selected tab.  Last selected is defined by selecting one of the tabs (Info, Chapters and Cast & Crew) and than using the up arrow to bring up the playback display.

Example - version 26.0.23

Not selected:

Selected:

 

 

For comparison, example of not selected and selected from previous version 26.0.22.  The last selected tab does not have a dimmed background and the text is not clipped by the background when selected.

Not selected:

Selected:

Edited 5 hours ago by softworkz

[softworkz 5382]

I have moved this to the Web App forum. This is not an app-specific issue and the legacy Windows app is no longer supported. Yet the legacy Windows app was displaying the hosted web app which of course supported and this is the right place for it.

[scottpro 30]

When was the Legacy Windows app (ET 3.0.20/21) no longer supported?

If the Legacy Windows app is no longer supported than why is the content it accesses is being updated.
Legacy Windows app: https://tv.emby.media
Windows Web app: https://app.emby.media

From what I can see is that the contents of the tv.emby.media is just a copy/mirror of the app.emby.media contents.

Since the Windows Web app runs under a later version of Chromium (the users web browser) and the Legacy Windows app uses a old version of Electron (11.5.0.0) that any testing is done on the Windows Web version and not the Legacy version.  If this is the case than perhaps Emby should stop updating the tv.emby.media since it poses potential breaking changes that are not tested and leaving the users to find them.

Perhaps Emby could release an updated version of Emby Theater Legacy with the latest version of Electron and MPV so it can use the latest updates from the web content and be consistent with current web browsers.  Not sure how many users are using the Legacy version but it isn't that difficult to update an existing project.  Heck, I'll do it if you want.

Edited 3 hours ago by scottpro

[softworkz 5382]

1 hour ago, scottpro said:

When was the Legacy Windows app (ET 3.0.20/21) no longer supported?

If the Legacy Windows app is no longer supported than why is the content it accesses is being updated.
Legacy Windows app: https://tv.emby.media
Windows Web app: https://app.emby.media

There doesn't exist something like a "Windows Web App". The Windows app does not access any of these URLs. Changes to content on those URLs do not affect the Windows app. It has everything included and is self-contained. It gets updated solely by regular applicatiion updates through the Windows store.

Both URLs point to the same code. The only difference is that tv.emby.media has TV mode as default and app.emby.media does not (at least that's how it was before TV mode selection was added to the welcome screen. 
And both URLs represent the "Emby Web App" which this forum is about. We also often call it the "hosted web app" (because we are hosting it for users).

The old Windows app was using the code from tv.emby.media, but tv.emby.media has never been a url specifically for that app. There were (not sure whether still any) other apps using it as well and tv.emby.media is also useful on TV models with a browser but for which we do not have specific apps.
 

1 hour ago, scottpro said:

Since the Windows Web app runs under a later version of Chromium (the users web browser)

No. It ships its own fixed version of the WebView2 runtime to prevent bad surprises and different client behavior due to Windows updates of the included browser engine. In that regard it is quite similar to Electron, but the player integration is done in a completely different (and much better) way.

The combination of fixed browser engine version plus the UI code being included in the app itself makes it very resilient against any kinds of bad surprises from one day to another.

 

1 hour ago, scottpro said:

Perhaps Emby could release an updated version of Emby Theater Legacy with the latest version of Electron and MPV so it can use the latest updates from the web content and be consistent with current web browsers.  Not sure how many users are using the Legacy version but it isn't that difficult to update an existing project.  Heck, I'll do it if you want.

You can't. There's no more way to bring mpv playback or any other kind of content into a Chromium engine. Those interfaces have been removed long ago and that's why the Electron version of the old app couldn't be updated anymore and is meanwhile a honeypot of browser vulnerabilities. It's irresponsible for a sw verndor to offer any such version to users and for users it's dangerous and risky to use any such application. I had discussions with Chromium developers about it and they acknowledged that there is no other way to bring video content into a browser's DOM with a native player like it was possible with NaCL/PPAPI (flash player was using this for example).
I had found a loophole in a somewhat newer Electron (which the first WMC UI Windows app was using), but shortly after, they completely ripped out all code for this from Chromium.

It's a dead horse, entirely. There will never be any update for that old app, I'm afraid.

Edited 2 hours ago by softworkz

[scottpro 30]

Thanks for the update. I just wanted to clarify some of the terminology around the different Emby apps, since I think some of the naming can be a little confusing.

• The Electron-based Windows application is the Legacy Windows App. It runs as an Electron application wrapped by Emby Theater and supports the MPV player. Its user interface and functionality are also tied to tv.emby.media. This URL is defined in main.js under the electronapp folder.
• The Microsoft Store version is the Windows App. It is a native C# application, and the assets required to run Emby Theater are packaged locally with the application.
• The Web App is the Emby-hosted version of Emby Theater that runs in the user's local web browser. Depending on the configuration, it can be accessed through app.emby.media or tv.emby.media.
• The local server web client is also an Emby Theater session running in a web browser, but its assets are hosted directly by the user's local Emby Server. Unlike the hosted Web App, it does not receive incremental client updates independently; updates are generally delivered as part of an Emby Server upgrade.

Since tv.emby.media is used by the Web App and is also still referenced by the Legacy Windows App, there appears to be some overlap between the two paths as Emby transitions toward the newer Windows App.

For my particular setup, this is not a significant issue. I self-host tv.emby.media on a local server and can run different versions from roughly the past 18 months. I also have the ability to address certain bugs or issues myself and merge those changes into newer Emby updates. Most users, however, do not have that flexibility and are dependent on the versions and fixes provided through the normal release channels.

For now, I plan to continue using the Legacy Windows App because the newer Windows App has several restrictions—primarily around MPV customization—that do not work well with my current setup.

That may change in the future as the Windows App continues to mature, but at the moment the Legacy Windows App remains the better fit for my needs.

[softworkz 5382]

8 minutes ago, scottpro said:

Thanks for the update. I just wanted to clarify some of the terminology around the different Emby apps, since I think some of the naming can be a little confusing.

Yea, things have changed over time and at some places you may find older terminology.

Most of your points are accurate. The one mismatch is the term "Emby Theater". It had been used for the old Linux and old Windows apps which were both driven by Electron. For the new Windows (and Linux) apps, it was decided to retire the "Emby Theater" naming.
It has never been a name for the web app.

 

13 minutes ago, scottpro said:

• The Electron-based Windows application is the Legacy Windows App.and was called Emby Theater for Windows It runs as an Electron application wrapped by Emby Theater and supports the MPV player. Its user interface and functionality are also tied to tv.emby.media. This URL is defined in main.js under the electronapp folder.
• The Microsoft Store version is the Windows App. is a native C# application, and all UI code assets required to run Emby Theater are  is packaged locally with the application.
• The Web App is the Emby-hosted version of the UI code Emby Theater that runs in the user's local web browser. Depending on the configuration, it can be accessed through app.emby.media or tv.emby.media.
• The local server web client is a version of the UI code that is included in Emby Server. also an Emby Theater session running in a web browser, but its assets are hosted directly by the user's local Emby Server. Unlike the hosted Web App, it does not receive incremental client updates independently; updates are generally delivered as part of an Emby Server upgrade.

 

21 minutes ago, scottpro said:

Since tv.emby.media is used by the Web App and is also still referenced by the Legacy Windows App, there appears to be some overlap between the two paths as Emby transitions toward the newer Windows App.

• tv.emby.media is the "Web App"
• There is no overlap
  The UI code is developed to run on a wide variety of browsers and browser versions. There are other target platforms with old browser versions that we are trying to keep supported, so when you see fixes for issues you see in the old app, it doesn't mean they were made specifically for the legacy Emby Theater application
• There is no transition
  The Windows app has been released 2.5 years ago already and is well established, used by a pretty large number of users every day
  You are one of the last few remaining people still using the legacy app and the only one posting about it

 

39 minutes ago, scottpro said:

For now, I plan to continue using the Legacy Windows App because the newer Windows App has several restrictions—primarily around MPV customization—that do not work well with my current setup.

Besides for a general mpv version (+ffmpeg) update, there are no hot requests for mpv features/options to add - just a handful of inidividual ones, each by one person only. It's been pretty quite in that direction, even though the new Linux beta is out for half a year now and uses the very same mpv implementation. Nobody found anything missing so far. It seems that most users have come to realize that there's no need for a complex mpv.conf file to achieve great and high-quality playback (even though you can never fully satisfy the 100% and you may be one of the 0.001% for wich it doesn't suffice).

 

38 minutes ago, scottpro said:

That may change in the future as the Windows App continues to mature,

Feel free to participate in the Windows beta program (open for new registrations soon) and help us improve its maturity whereever you see it lacking  

 

PS: Hosting the UI code locally is a good measure, also in terms of security. But you should be very careful about the sources for images you are using, because that old Electron version is vulnerable to almost all of the browser (chromium) image parsing exploits which have been discovered and fixed (everywhere else) over the past 6-8 years - and there were many of this kind.