Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS theme errors #335

Open
3 of 14 tasks
Nakroma opened this issue Jan 31, 2020 · 2 comments
Open
3 of 14 tasks

CSS theme errors #335

Nakroma opened this issue Jan 31, 2020 · 2 comments

Comments

@Nakroma
Copy link
Member

Nakroma commented Jan 31, 2020

I'm submitting a...

  • Bug report
  • Feature request
  • Documentation issue or request

Current behavior

There are several theme conflicts currently:

  • Warframe Open Trades has Wow Classic colors
  • The loading bar color doesn't change when switching between games (main loading bar and graph bars)
  • The two circling dots in the "Connecting to NexusHub..." bar are Warframe colors

Expected behavior

They should have the correct theme.


Minimal reproduction of the problem


Environment

Browser:

  • Chrome (desktop) version:
  • Chrome (Android) version:
  • Chrome (iOS) version:
  • Firefox version:
  • Safari (desktop) version:
  • Safari (iOS) version:
  • IE version:
  • Edge version:

For development issues:

  • Node version:
  • Operating System:

Additional Description

@Nakroma Nakroma added Type: Bug Scope: UI Game: WoW Classic Issues that concern the WoW Classic subsite. labels Jan 31, 2020
@Kaptard
Copy link
Member

Kaptard commented Jan 31, 2020

Further issues:
[ ] The main loading bar color doesn't change when switching between games

@Nakroma Nakroma removed the Game: WoW Classic Issues that concern the WoW Classic subsite. label Feb 1, 2020
@Nakroma
Copy link
Member Author

Nakroma commented Mar 3, 2020

The progress bar errors are the same error, they appear because the progress styling is defined by the body class, which doesn't get refreshed when switching games. I'm not sure if this is easily fixable, because cubic handles the progress bar stuff. However, this bug is almost not noticable and occurs rarely so I'll put it in the backlog for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants