Mby it's worth to give users who have a firefox master password a hint that they should enter this when they see "Enter Password or Pin for "NSS Certificate DB""

Description

It's very useful to display Toc for a very long readme file, please consider it!!

Environment (if bug)

• Octotree version:
• Browser & version:
• OS & version:
• Screenshot, if any (drag an image here)
• Console error log below this line

• windows 10

• FF 58.0b11 (64-bit) uBo 1.14.21rc4
  or

• chrome Version 64.0.3282.24 (Official Build) beta (64-bit) uBo dev build 1.14.21.104

• go to google.com

• open dashboard, logger

• refresh page

• choose some element to block for example:
  notifications.google.com

• Click on the 4th cell of a log entry => to create a static filter

• create the filter => `||notifications.g

The current Readme file seems a bit unstructured and needs some improvements.
The Readme.MD should be updated with the following points to be kept in mind:

• Have a table of contents
• Have a different file for Contributing.MD and reference it in Readme.MD
• Have a better Contributing.MD file with a proper table of contents and tips.
• Currently, the link to Xcode Developer Tools in Readme do

https://www.reddit.com/r/uBlockOrigin/comments/9dr9jd/modify_referrer_policy_headers_and_meta/

https://developer.chrome.com/extensions/privacy#property-websites

chrome.privacy.websites.referrersEnabled

More extensions means more memory usage, so I'd like to keep the number of privacy extensions to a minimum.

Also, could Decentraleyes be merged with uBlock Origin using uBlock redire

Page Requirements

• ability to add a single page to the archive (like echo <url> | archivebox add)
• ability to import a list of pages / feed of URLs into the archive (like archivebox add <url>)
• link to the homepage of the index /
• link to the django admin list of URLs for editing the archive /admin/
• link to the archivebox github repo & documentati

👋 I noticed that there are a couple of instances of words "easily" and "just" in your documentation. Unfortunately, words like this can make people feel frustrated and isolated while reading (myself included, hence the issue) - especially if they are facing issues.

If it's alright with your team, I'd like to take a shot at updating the content to make it more inclusive by removing instance

The GET /session/{session id}/moz/screenshot/full endpoint cannot take full page screenshot of horizontal scroll document. takes viewport only.

Vertical scroll page works fine.

System

• Version: 0.24.0
• Platform: macOS Mojave 10.14.5
• Firefox: 67.0.4
• Selenium: java 4.0.0-alpha-2

Testcase

Currently, the Import button on the Import Account Screen Errors is enabled but Errors when no string/file is presented.

Should disable that button on empty strings/file.

versions

• SlimerJS: 1.0
• Firefox: 58
• Operating system: Alpine Linux container

Steps to reproduce the issue

The legacy PhantomJS uses a rather weird convention for evaluateJavaScript function - it asks the script input to be wrapped around function() {}, or the script will not be executed at all. For example:

http://phantomjs.org/api/webpage/method/evaluate-java-script.

OS platform / Browser

Windows 10/Chrome Version 69.0.3497.100 (Official Build) (64-bit)

melonJS version

master branch - 10/1/2018 - melonjs 6.2.0

Bug description

UI example mouse clicks won't work with simulation_rpg example

Steps to reproduce the bug

I have put in a pull request 951 - code which reproduces the problem.
(see examples/isometric_rpg_ui)
https

https://simon.html5.org/test/html/rendering/color-attributes/ has tests for https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#rules-for-parsing-a-legacy-colour-value

As far as I can tell, there are no tests for this in wpt.

Likely the tests don't quite match with the current spec. But they do reveal that there are some differences between Gecko and WebKit/Blink.

As you know it is hard to surf on web with user.js. I always have problem with many sites, but it i realyly takes time to find which config is not compatibale with the visited site. I think we can create a list of buggy sites so anyone can contribute it.

I can start with mines:

• site
• bug
• comments
• how to fix

• linkedin.com
• does not go home page after login
• this is

NYtimes doesn't show its articles properly on the private window.

I would like to read articles in NYtimes on the private window.

Thank you for your hard work :)

Short description

The tab close buttons seem to be partially or completely obstructed by an invisible element. Clicking on tab close buttons or on tabs does not work across the obstructed area.

Steps to reproduce

1. Start Firefox with clean profile.
2. Install TST.
3. Create a large enough number of containers (e.g. 100) using long enough names (e.g. `ABCDEFGHIJKLMNOPQRSTUVXYZab

I'm opening this issue because:

• I'll report a bug
• I'll propose a new feature

Description

The current system for links could be more intuitive. Whereas other keybindings are case-sensitive, link hints are not, leading to confusion.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. Press f to start following links
2. Spot a hin

manifest.json currently contains a blank description for the keyboard shortcut to open bitwarden in the sidebar. This causes confusion in the new FF 66 keyboard shortcut manager.

I can submit a pull request to fix this, or you can do it, whichever you prefer.

Add on suggestions [and other privacy related suggestions] mentioned at the following websites for consideration/integration:

Prism Break: https://prism-break.org/en/categories/windows/#web-browser-addons

• Cookie AutoDelete
• Decentraleyes
• HTTPS Everywhere
• Mailvelope
• NoScript
• Privacy Badger
• uBlock Origin

Privacy Tools: https://www.privacytools.io/#addons

• Privacy Badg

Expected: Microphone permission box has clearly contrasted controls

Actual: Black-on-dark-gray checkbox is difficult to distinguish, especially if monitor is not on maximum brightness:

When you have read a link you want to follow, your eye are at the right edge of the link text. I find it annoying to have to trace back to the beginning of a long link text to identify the hint.