💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

Until themed-picture is loaded again, the #gh-light-mode-only / #gh-dark-mode-only fragments might work as a workaround that follows the GitHub theme instead of the OS:

![Example](light.webp#gh-light-mode-only)
![Example](dark.webp#gh-dark-mode-only)

These don't rely on JavaScript. GitHub's stylesheet hides one of the two based on its own data-color-mode attribute (:root[data-color-mode=light] … [href$="#gh-dark-mode-only"] { display: none } and the reverse), so it should sidestep the custom-element registration problem you found. I haven't checked it in the new repo view with GitHub set to Light and the OS on Dark, so it's worth a quick test on your README. The downside is you lose <picture>'s single-request behavior and srcset, so it's a stopgap, not a replacement. The <themed-picture> registration still needs fixing on GitHub's side.

Thank you.

This isn't a very convenient solution, since this README is also published on npm. I hope this bug gets fixed soon.