Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში. აქ არავინ უნდა მოგთხოვოთ ტელეფონზე დარეკვა, შეტყობინების გაგზავნა ან პირადი მონაცემების გაზიარება. რამე საეჭვოს შემჩნევისას გთხოვთ გვაცნობოთ „დარღვევის მოხსენებით“.

ვრცლად
გადაწყვეტილი დაარქივებული

Copy content of inspector

cor-el პასუხგაცემული
erw1

I have saved an html page, I do 'inspect element'. That opens a web developer's interface on tab 'inspector'. What I want to do next is copy all that is in it. Ctrl-A does not select all.

I have saved an html page, I do 'inspect element'. That opens a web developer's interface on tab 'inspector'. What I want to do next is copy all that is in it. Ctrl-A does not select all.
მიმაგრებული ეკრანის სურათები

ყველა პასუხი (4)

შერჩეული გადაწყვეტა

I don't think that you can get the full page source via the developer tools. You can get the source of the head and body tag via the right-click context menu (Copy > Copy Outer HTML), i.e. you can get the source of a selected node.

You can't get the part before the HEAD tag (!DOCUMENT and in your screenshot also some conditional code for IE). You need to open the page source in a tab via the right-click context menu on the web page (View Page Source) to get the full page source. Select All and "View Selection Source" give you the source as generated from the DOM.

ჩასწორების თარიღი: , ავტორი: cor-el

Isn't Ctrl+U the same thing? Regardless, Viewing the page source keeps some elements (emails) protected that are OTOH visible in the inspector.

Wait, actually, no, I do see the 'mailto's that were previously hidden.

Case closed.

Hello,

I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution.

Thank you for contacting Mozilla Support.

Node that sometime the web page can load extra content via XHR, but I wouldn't expect this on a page you loaded locally.