You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would allow for easily adding support for new features or changes that have been made to the interface.
Sometimes features aren't available for everyone, so I or any other contributors might not catch every edge case if it's not possible to view and test it ourselves.
To make things even worse, Google uses a process of obfuscating their CSS which consistently breaks the theme even if seemingly nothing has changed.
Some of the CSS is split into files which are only loaded on specific views, (join screen, welcome page, in call) and only occurs for users who are logged in, which makes an automated process difficult.
Perhaps there is an endpoint which can be used to view all the CSS.
However, despite that, several months ago I was able to automatically generate the theme but only for apps.google.com/meet/ and meet.google.com/xxx-yyyy-xxxx. I never committed those changes because that would cause style conflict and leave the call portion of the theme untouched, the most important part.
The text was updated successfully, but these errors were encountered:
This would allow for easily adding support for new features or changes that have been made to the interface.
Sometimes features aren't available for everyone, so I or any other contributors might not catch every edge case if it's not possible to view and test it ourselves.
To make things even worse, Google uses a process of obfuscating their CSS which consistently breaks the theme even if seemingly nothing has changed.
Possible Solution
Use a forked version of GitHub-Dark's automated CSS program. Documentation can be found here: https://github.com/StylishThemes/GitHub-Dark#auto-generated-css
Problem
Some of the CSS is split into files which are only loaded on specific views, (join screen, welcome page, in call) and only occurs for users who are logged in, which makes an automated process difficult.
Perhaps there is an endpoint which can be used to view all the CSS.
However, despite that, several months ago I was able to automatically generate the theme but only for
apps.google.com/meet/
andmeet.google.com/xxx-yyyy-xxxx
. I never committed those changes because that would cause style conflict and leave the call portion of the theme untouched, the most important part.The text was updated successfully, but these errors were encountered: