TZP: trap resource:// blocking

OK, I’ll rerun prototype for section reruns as well 😃

I notice the delay (I use F5) on file:// … have to close and restart nightly after a dozen or of them. Not noticed it on http … so will be interesting when I upload all my changes: so much stuff here

I changed up line-height and scrollbar info by only reporting a narrower range of known zoom values: since FF recently added 400 and 500% - that and I think a lot of values on Linux will change with native theming disabled. In order to test it I made it update-able in real time: that was fun.

closing: have sorted out timing out in promises, and overall hardened all the isThings used throughout my code: promising them once on each pageload

@sereneblue FYI: on Cydec

• cydec also tries to mess with error strings (which is not a real solution IMO, since what errors are generated and how they are, can be different depending on the script: i.e it’s a game of whack a mole). The error’s generated in my test are from passing a string to a new function (thanks to abraham)

const newFn = x => typeof x != 'string' ? x : new Function(x)()

//and here are the three error strings used to check if you are firefox
try {newFn("alert('A)")} catch(e) {res.push(e.name +": "+ e.message)}
try {newFn(`null.value = 1`)} catch(e) {res.push(e.name +": "+ e.message)}
try {let test = newFn("let a = 1_00_;")} catch(e) {res.push(e.name +": "+ e.message)}

• cydec also mangles math function results: which is the fourth isFF test (the one which also sets the isEngine)

That cydec really is a piece of work: right now I’m returning [object Object] in navigator.connection because of it’s hijinks

Correct. Here’s an example of Privacy Possom starting with none on page load and then 10 lies on re-run.

Yes, that’s it. The timeout resolve only resolves the promise if the promise is still pending.

If you like, you can reduce some of the nested bracket layers by checking if !(isFF && isTB === ""), resolve early if true, and then the else block can be omitted since a false condition will execute everything else. It reads fine either way though.

function get_isTB() {
    return new Promise(resolve => {
        // resolve early if condition is true
        if (!(isFF && isTB === "")) {
            return resolve("done")
        }
        // else
        try {

        } catch (e) {

        }
    })
}

…And, an arrow function can remove the nested function brackets (minimal nesting).

const get_isTB = () => new Promise(resolve => {
    // resolve early if condition is true
    if (!(isFF && isTB === "")) {
        return resolve("done")
    }
    // else
    try {

    } catch (e) {

    }
})

you mean like this? I think I get it now, the resolve can only be resolved once, then the promise is over, including the timeout?

function get_isTB() {
	return new Promise(resolve => {
		if (isFF && isTB === "") {
			try {
				// extensions can cause this to never promise
					// FF is ~1ms, TB is ~20ms
				var timeout = window.setTimeout(function(){
					// assume false: if actually TB, you're a CRAZY edge case
					isTB = false
					console.debug("get_isTB timed out")
					resolve("get_isTB timed out")
				}, 100)
				//setTimeout(() => resolve("promise failed"), 100)

				let t0 = performance.now()
				// etc