Make it easier to copy the version, revision, and OS when reporting an issue
See original GitHub issueDescription
Suggestion: When reporting an issue, you’re asked (for production builds) to copy the Brave, Revision, and OS information from brave://version/ into the issue, It’s surprisingly fiddly to do that with the current layout of the version page. I suggest adding a [Copy]
button or similar that grabs it to the clipboard in a form that can be easily pasted into the issue.
Steps to Reproduce
Actual result:
Expected result:
Reproduces how often:
N/A, new feature suggestion
Brave version (brave://version info)
😉
Brave | 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)
Revision | 021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}
OS | Linux
Version/Channel Information:
Other Additional Information:
N/A, new feature suggestion
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (8 by maintainers)
Top Results From Across the Web
Version Control: A Good Practice Guide - University of Glasgow
Version control is the process by which different drafts and versions of a document or record are managed. It is a tool which...
Read more >A Visual Guide to Version Control - BetterExplained
Version Control (aka Revision Control aka Source Control) lets you track your files over time. Why do you care? So when you mess...
Read more >Version control: Effective use, issues and thoughts, from a ...
Put briefly... version control allows you to manage changes over time. It is most commonly used to track revisions to source code. For...
Read more >File Naming Conventions & Version Control
Include a 'version control table' with each important document, noting changes and their dates alongside the appropriate version number of the document. If ......
Read more >What is version control | Atlassian Git Tutorial
Version control is the practice of tracking and managing changes to software code. Learn about the benefits of version control systems here.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@d4mr took a quick peek using Chromium’s code search and looks like the code for that page is in https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/webui/version_ui.cc
There’s going to be some HTML/JavaScript (Polymer) in the Chromium side that is loaded by this Web UI code. That’s where the change you’ll need to make will be 😄 (the
version_ui.cc
may need edits, depending on if you add strings, etc) https://source.chromium.org/chromium/chromium/src/+/master:components/version_ui/resources/about_version.htmlTo get started, you can edit the Chromium code directly until you work something out and then we can figure out patching. When that time comes, we have some notes about patching in our guide (unfortunately this doesn’t cover Polymer patching, but I can help with that): https://github.com/brave/brave-browser/wiki/Patching-Chromium
@bsclifton I upgraded to a new connection and PC, and I have everything working. How can I proceed with patching? Also, do I need to add a new string for the “Copy Info to Clipboard” text?