uBlock Origin marked as "shimmed" at arewee10syet.com

Add-ons Development
#1

For long the extension I maintain, uBlock Origin, was not listed at https://www.arewee10syet.com/, but today I found out it had been added to the list, and marked as a "shimmed"exyension – with no issue number provided.

I am not aware of uBlock Origin not being fully compatible with multiprocess – given it was first written for Chromium, being fully e10s-compatible was built-in from the start.

How can I find out why it is marked as “shimmed”, so that I can address whatever it is that prevents it from being marked as a fully e10s-compatible add-on?

#2

It may be that your install.rdf doesn’t have a multiprocessCompatible property. It’s tricky to spell too, I mispell it all the time. Do you have that in your rdf?

#3

I have the following line in install.rdf:

<multiprocessCompatible>true</multiprocessCompatible>

This works since Nightly recognizes uBO as a multiprocess-compatible extension.

#4

Alright, never mind, it seems uBO’s status on https://www.arewee10syet.com/ has now been revised to “compatible”.

#5

The latest version of https://www.arewee10syet.com/ shows uBlock Origin (“uBO”) as being compatible (correct), but (erroneously IMO) reports “Shims” and “CPOW” count of “26,264”.

uBO is fully compatible with e10s, no shim required, as opposed to what the entry states.

I do use uBlock Origin with Nightly, and the only “CPOW” warnings which I have seen were the ones reported months ago, and caused by a bug in Nightly which has been fixed since months now (Nightly was mistakenly loading uBO as a non-e10s-compatible addon).

Is there a way for me to find out who edited the information for uBO on https://www.arewee10syet.com/, so that I can ask for clarification about how it was decided that uBO needs “Shims” and causes “CPOW” warnings – something which I haven’t seen since the Nightly issue mentioned above?

1 Like