Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Screen shots cause vulnerability issue

  • 5 replies
  • 2 have this problem
  • 5 views
  • Last reply by finitarry

more options

I work on a password management system. During testing in the firefox environment I found that on the "New Tab" page it shows screen shots and links to recently visited pages. The problem is it is taking screenshots when I reveal a password in my password management solution.

So in short, when I open firefox you see a page full of screenshots of my passwords.

I want to advice on how I can solve this from the website perspective. I want to stop firefox from taking screenshots of a particular page without configuring the browser.

Any suggestions would be greatly appreciated!

I work on a password management system. During testing in the firefox environment I found that on the "New Tab" page it shows screen shots and links to recently visited pages. The problem is it is taking screenshots when I reveal a password in my password management solution. So in short, when I open firefox you see a page full of screenshots of my passwords. I want to advice on how I can solve this from the website perspective. I want to stop firefox from taking screenshots of a particular page without configuring the browser. Any suggestions would be greatly appreciated!

All Replies (5)

more options

You could set Firefox to use a blank page for new tabs. In the about:config window, change this setting:

browser.newtab.url - change to about:blank

more options

I want to do this on the webpage side, not the browser side. Is there any meta tags or anythign that will prevent this from happening?

more options

hello jon, bug #754608 might give some clues.

more options

You can create these Boolean prefs on the about:config page if you want to disable the thumbnails on the about:newtab page.

  • name: browser.pagethumbnails.capturing_disabled with value: true
  • name: pageThumbs.enabled with value: false
more options

So the first setting prevents the thumbnails from being made to begin with, and the second setting prevents them from being displayed? Seems a bit redundant, doesn't it?