With Chrome, Safari, and Edge enabling the tracking feature called Hyperlink Auditing, or Pings, by default without a way to disable them, users will need to rely on browser extensions to block them going forward.
Source: Blocking Hyperlink Auditing Tracking Pings with Extensions
Content Security Policy (CSP) allows you to dictate a policy for content restrictions on a web site that is enforced by the browser. By setting a CSP header, can control the resources that are loaded when a visitor is viewing your website. The CSP spec allows you to build very specific policies for your site that can handle all of the different types of resources that a site might load. It is a valuable tool for protecting your site visitors.
In addition to blocking resources that violate the defined CSP, the CSP spec details a mechanism for sending reports of such violations. Monitoring these violations can help you ensure that your site is never serving content that violates your wishes whether those violations are the result of producer, developer, or hacker actions.
Source: What to Expect When Expecting Content Security Policy Reports
Hi Jerl, you don’t need to explain the problem to me. I still have dom.disable_window_open_feature.toolbar set to true in about:config although it no longer does anything. As support forum volunteers, we don’t get special access to developers, we have to get in line like everyone else.
Did I post this before? The reason the toolbar buttons are hidden is a built-in style rule. So as an unofficial community developed workaround, you can inject an overriding style rule to make them visible again.
Setting this up is a little bit involved, so please set aside 10 quiet minutes to work through it.
(For anyone who already has a userChrome.css file set up, you just need to add the rule under (A) to your file.)
(A) Select and copy the following style rule code
/* Override Hiding of Toolbar Buttons in Limited Feature Windows */ *|*:root[chromehidden~="toolbar"] .chromeclass-toolbar-additional { display: -moz-box !important; /* default is display: none */ }(B) Generate and download a
userChrome.cssfileOpen the following page and paste the above rules into the editor, replacing the sample rule:
https://www.userchrome.org/download-userchrome-css.html
Then click “Generate CSS File” and save the userChrome.css file to your computer. (See first attached screenshot)
Use the downloads list on the toolbar to open the downloads folder directly to the new userChrome.css file. (See second attached screenshot)
Minimize that file browser window for later reference.
(C) Create a new
chromefolder in your profile folderThe following article has the detailed steps for that (#1, #2, and I recommend #3)
https://www.userchrome.org/how-create-userchrome-css.html
I have videos for both Windows and Mac in case the text is not clear.
(D) Move the
userChrome.cssfile you downloaded in Step B into thechromefolder you created in Step C(E) Set Firefox to look for userChrome.css at startup — see step #6 in the above article.
The next time you exit Firefox and start it up again, it should discover that file and apply the rule.
Success?
Once you start tweaking the interface this way, you’ll probably find more and more things you want to do. I suggest bookmarking the pages where you get the code for future reference because changes to Firefox may break them and it’s easier to request an update if you can find the source.
Source: Prevent new window from hiding addons in toolbar | Firefox Support Forum | Mozilla Support
Firefox Quantum‘s interface is still extremely customizable thanks to its userChrome.css file. You can edit this file to hide unwanted menu items, move the tab bar below the navigation toolbar, view multiple rows on your bookmarks toolbar, and do other things that normally wouldn’t be possible.
Source: How to Customize Firefox’s User Interface With userChrome.css
A preference is any value or defined behavior that can be set (presumably, one setting is preferable
to another). Preference changes via user interface usually take effect immediately. The values are saved to the user profile (in prefs.js), for both Firefox and Thunderbird.
A preference is read from a file, and can call up to four methods: pref(), user_pref(), sticky_pref() and lockPref(). All preferences files may call pref(), user_pref() and sticky_pref(), while the config file in addition may call lockPref().
Source: A brief guide to Mozilla preferences – Mozilla | MDN
How to Create a userChrome.css File
Updated May 24, 2019; Originally posted by jscher2000 on November 5, 2017.
Creating your userChrome.css file is the first step on your quest to make over Firefox’s interface. It takes a couple of minutes, but it’s important to take your time and get it right so Firefox loads and applies your style recipes on the first try.
At startup, Firefox will check for the userChrome.css file in a particular location: a folder named chrome inside your currently active profile folder. The profile folder is where all of your current settings and add-ons are stored. (If you want to learn more about that folder, see “Profiles — Where Firefox stores your bookmarks, passwords and other user data” on Mozilla Support.)
Here’s how you set that up (full details below):
- Open your currently active profile folder
- Create a new folder named chrome
- Create a desktop shortcut (alias) to the chrome folder for easier future access
- Make sure your OS is set to show you file extensions like .txt and .css
- Create a new text file inside the chrome folder named userChrome.css
- Change a preference in Firefox so it looks for your files at startup (in Firefox 69+)
A mod_rewrite Cheat Sheet – a quick reference guide for mod_rewrite, with rewrite flags, regular expression syntax and sample rules.
mod_rewrite Tutorialsmod_rewrite RewriteRule Flags
mod_rewrite RewriteCond Flags
Redirection Header Codes
mod_rewrite Directives
|
Regular Expressions Syntax
There’s an excellent regular expression tester at: http://regexpal.com/
mod_rewrite Server Variables: HTTP Headers
mod_rewrite Server Variables: Server Internals
|
mod_rewrite Sample Rule: Site Moved
Rewrites domain.com to domain2.com
mod_rewrite Sample Rule: Temporary Page Move
Rewrites domain.com/page.html to domain.com/new_page.html
mod_rewrite Sample Rule: Nice URLs
Rewrites domain.com/category-name-1/ to domain.com/categories.php?name=category-name-1
mod_rewrite Server Variables: Special
mod_rewrite Server Variables: Request
mod_rewrite Server Variables: Time
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Source: Removes the autoplay up next feature · GitHub
| // ==UserScript== | |
| // @version 1.0.2 | |
| // @name Removes the autoplay up next feature | |
| // @match *://www.youtube.com/* | |
| // @run-at document-start | |
| // @grant none | |
| // @noframes | |
| // ==/UserScript== | |
| (function () { | |
| ‘use strict‘; | |
| function removeAPUN() { | |
| var autoplaybar = document.getElementsByClassName(‘autoplay-bar‘)[0]; | |
| if (autoplaybar) { | |
| autoplaybar.removeAttribute(‘class‘); | |
| document.getElementsByClassName(‘checkbox-on-off‘)[0].remove(); | |
| } | |
| } | |
| window.addEventListener(‘readystatechange‘, removeAPUN, true); | |
| window.addEventListener(‘spfdone‘, removeAPUN); | |
| }()); |
