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

Interactive examples ignore changes of color schemes when features are not supported #1305

Closed
yarusome opened this issue May 21, 2023 · 2 comments
Labels
closed: stale This issue or pull request is very old, or requested information were not provided in time.

Comments

@yarusome
Copy link
Contributor

After navigating from a page with a supported interactive example to one with a non-supported example, the color scheme of the example on the second page sticks to the one on the first page after changing the color scheme on the second page.

Reproduction steps:

  1. Navigate to one page with a supported example.
  2. Select any color scheme.
  3. Navigate to a second page with a non-supported example.
  4. Change the color scheme.
@caugner caugner added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Oct 10, 2023
@caugner
Copy link
Contributor

caugner commented Oct 12, 2023

@yarusome Thank you for reporting this issue, and sorry for taking so long to get back to you.

Can you still reproduce this issue, and if so, can you provide your browser version and specific URLs you experience the issue with? Thank you! 🙏

@caugner caugner added needs info Needs more information to review or act on. and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Oct 12, 2023
@caugner
Copy link
Contributor

caugner commented Nov 21, 2023

Thanks again for raising this issue.

As we haven't heard back from you, we will go ahead and close this issue. If you think it's still relevant, please reply to the previous comment and reopen the issue. 🙏

We appreciate your understanding.

@caugner caugner closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2023
@caugner caugner added closed: stale This issue or pull request is very old, or requested information were not provided in time. and removed needs info Needs more information to review or act on. labels Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: stale This issue or pull request is very old, or requested information were not provided in time.
Projects
None yet
Development

No branches or pull requests

2 participants