Chrome Version: 69.0.3497.100
OS: Mac OS10

What steps will reproduce the problem?
(1) Navigate to a page that has this snippet of HTML in it: https://bit.ly/2J6KcHX (for a live example, search this site for any name, and click through to an individual record and look at the tables: https://on.ny.gov/2fzggci)

(2) Open devtools, look at under any of the <table> entities. Separately, right-click and select 'View page source'.

(3) Note that <tbody> tag has been added by devtools (correcting the flawed HTML of the page itself). In the page source, it's not present.

What is the expected result?
Devtools reflects the actual underlying page source, so that (e.g.) the developer can try to figure out why this page isn't working with common parsers.

What happens instead?
Devtools shows a 'healed' version of the HTML, covering up the fact that the underlying HTML is invalid. 

This bug isn't meant to suggest it should stop auto-fixing pages, but that the fixes should be styled differently so that a developer knows they were added by devtools, rather than reflect the actual page source.

Leaving this marked as 'Bug' because I don't know whether it's intentional or not, if so this may be a FR for UX to show what's added and what's real page source in devtools.