Human Folly about “Firefox”

index

• Firefox is now the last major browser that still supports ublock origin (pcworld.com):

  #Firefox still supports #uBlock Origin, but #Microsoft Edge is dropping support for it, by following #Google in dropping support for Manifest V2.

  on 02026-08-18
• Firefox Tor IndexedDB privacy vulnerability (fingerprint.com):

  #IndexedDB ordering (of database names) forms a stable process-lifetime identifier in #Firefox, presumably because of some kind of hash table randomization. “In Tor Browser, the stable identifier persists even through the “New Identity” feature, which is designed to be a full reset that clears cookies and browser history and uses new #Tor circuits.” #security

  on 02026-04-24
• Secure contexts (developer.mozilla.org):

  #Firefox #browsers consider localhost and file: URLs to be "secure contexts" for #HTML5 APIs like getUserMedia and service workers and custom protocol handlers

  on 02023-02-07
• Item (news.ycombinator.com):

  the #HTML5 camera API #getUserMedia in #Firefox #browsers requires HTTPS (or localhost) since 02019; the about:config flag to allow otherwise is media.getusermedia.insecure.enabled

  on 02023-02-07
• A short walkthrough of webrender (masonchang.com):

  Mason Change explains how the new #graphics system in #Firefox works. #toread

  on 02017-08-22
• Show bug (bugzilla.mozilla.org):

  the #Mozilla #Firefox bug for #canvas getImageData (or putImageData?) leaking memory. Unfortunately not fixed until version 32.0a1 and 31b3 in 2014.

  on 02016-01-11
• Pairing problems (blog.mozilla.org):

  The #UX problems with the first version of #Firefox Sync #security.

  on 02015-08-19
• Using LZ4 compression in JavaScript without node JS (stackoverflow.com):

  Tarelli reports problems with PierreC’s #JS #LZ4 #compression implementation in #Chrome and #Firefox

  on 02015-08-05