Adwaita-for-Steam VS web-bugs

I use this skin its mostly fine and looks much better than default for me

Adwaita for Steam seems to not play well with this new beta, but I don't understand how to uninstall this theme. Any help? Thanks!

I'd love to some day see a GTK interface option, similar to https://github.com/tkashkin/Adwaita-for-Steam but actually a GTK/libadwaita app rather than just emulating the look.

A good fix is installing the Adwaita skin for Steam Or if you prefer the vanilla steam use this skin

I'm using cantarell-static for Adwaita-for-Steam to work better. After an flatpak package update, none of my flatpak gnome apps can use this font anymore.

- Patch steam library files

The adwaita theme for steam does not have the first issue.

All you have to do is to edit resource/layout/uinavigatorpanel.layout of your skin and replace all references to emailreminderbar or phonereminderbar with LibraryAnchor. Here is this fix applied to my skin for example.

It won't load on my system :(

do you mean steam app theme or profile theme? if its steam app then github is your friend (example), if its for your profile then steam points shop

The thread is very long, here is the relevant comment:

https://github.com/webcompat/web-bugs/issues/131916#issuecom...

https://github.com/webcompat/web-bugs/issues?q=is%3Aopen+is%...

Microsoft Teams (which I don't think many people use voluntarily) in particular breaks in stupid ways - and then in others if you spoof your user agent.

a link to the video would help with troubleshooting, seems like another case of "this site or this particular feature doesn't support firefox" otherwise report to https://webcompat.com/

Have any of you faced this? If the website is made to open only in chromium-based browsers, I am planning to report to Webcompat. But before that, I thought I would make sure from others. Any experience or quick fix would be appreciated.

Teams was a classic hellhole for me when I was using Linux. Nowadays it lets you in but Firefox genuinely doesn't support all of the features the Teams site uses. This means certain features are made unavailable to Firefox users. Forcing the user agent makes some of these partially work but they are also still broken so Mozilla doesn't want to enable a user agent override by default and Microsoft doesn't want to enable a feature that only half works.

This GitHub WebCompat issue serves as a good example history https://github.com/webcompat/web-bugs/issues/77892

https://github.com/webcompat/web-bugs/issues/125920#issuecom...

having recently looked at a firefox performance regression for filing a bugreport, tooling that tracks performance (quite publicly) sees attention, easy upload to share tracing profiles also helps: https://firefox-source-docs.mozilla.org/testing/perfdocs/ind...

Their dedicated blog keeps you posted if firefox perf is your interest https://blog.mozilla.org/performance/

If you have a particular website you notice chromium being significantly faster with, for an easy report, there's https://webcompat.com/ - though bugzilla is better than it seems when coming from github issues