Skip to content

Instantly share code, notes, and snippets.

View stdin.js
hints.addMode("i", "Show image",
function (elem) || /url\("(.*?)"\)/.exec(DOM(elem).style.backgroundImage)[1]),
function (elem) elem instanceof HTMLImageElement || DOM(elem).style.backgroundImage != "none",
. 9.rc
. rclib $*
getflags 'g,p,r,e expire,n nick,d desc,l lang'
if (~ $flage '') flage = N
if (! ~ $flagl '') ext=.$flagl
if (! ~ $#argv 0)
View stdin.js
let libc ="");
let write = libc.declare("write", ctypes.default_abi,,, ctypes.char.ptr,
write(2, "foo\n", 4);, null, [2, "foo\n", 4]);
ifeq "$(shell uname -s)" "Darwin"
ABI_ARCH = x86_64
ifeq "$(GECKO_MAJOR)" ""
View stdin.txt
0: BASE,abcdefghijklmnopqrstuvwxyz
1: MAIN,abcdefghijklmnopqrstuvwxyz
2: COMMAND,abcdefijklmnoprstuvwxyz
3: NORMAL,ehqx
4: OPERATOR,acdimnopqrsuvxyz
5: VISUAL,afimnopqrtuz
6: CARET,acdfimopqrstuxyz
7: TEXT_EDIT,mnqrz
8: OUTPUT_MULTILINE,abcdehilmnoprstuvwxyz
View stdin.js
myExtension.$("[style='cursor:pointer;']", wnd.document).each(function(i) {
ez(/"(.+?)"/.exec(myExtension.$(this).attr("onclick"))[1], i++);
View stdin.js
"use strict";
const MASK_CHAR = "×";
function passwordify(input, maskChar) {
maskChar = maskChar || MASK_CHAR;
function ignore() {}
function mask(node) {
node.textContent = node.textContent.replace(/./g, maskChar);
View stdin.js
.setBoolPref("isAddonsActive", isValid);
.setBoolPref("hasLogedIn", isLogin);
View stdin
<?xml version="1.0"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<html xmlns="">
<style type="text/css"><![CDATA[
View stdin
I'm sorry but this is disturbing... Rated 1 out of 5 stars
by Atavachron on October 28, 2011 #
While this add-on appears to have been rolled-back to the previous version, we are still all left scratching our heads as to what just happened. It looks as if we are going to have to scour the code of every updated Mozilla add-on in the future to make sure nothing shady has been added. But, I don't know how that is even possible.
We have no explanation as to what occurred or what the new code in this add-on actually did or if it had any lasting effects, and no guarantee that the version that is now on this page is really what it purports to be, namely the last available version before the one in question.
What if someone updates their add-on with suspicious code and simply doesn't announce it? I realize that new add-ons must be approved, but the security door seems to be wide-open with regard to updated add-ons in general.
You can’t perform that action at this time.