💬 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. ⭐

This does sound inconsistent with what many users would expect from a "Code" view.

Since SVG files are both image assets and XML documents, it may be helpful to clarify whether GitHub is intentionally treating SVGs differently from other text-based formats or whether this is an unintended regression.

A few questions that could help narrow it down:

• Does this happen for all SVG files or only specific ones?
• Does selecting the Raw button display the XML source correctly?
• Is the behavior the same on different browsers and devices?
• Does the file contain standard SVG/XML markup, or was it generated by a tool that adds unusual content?

As a temporary workaround, users who need to inspect the markup may be able to use Raw, download the file, or append the raw file URL directly.

If this is reproducible across repositories and browsers, it seems reasonable to expect the Code tab to provide access to the underlying XML source rather than only the rendered image preview.