I would prefer it on top myself. I'm not a big fan of de-cluttering the interface to the point of having to take extra steps to find things.

As a quick reference, you could bookmark this internal URL: about:support#extensions-tbody

By the way, your Firefox reports it is version 68. Are you on the Extended Support Release channel?

Is this about the Addons website or about the builtin about:addons page ?

jscher2000 said

By the way, your Firefox reports it is version 68. Are you on the Extended Support Release channel?

cor-el said

Is this about the Addons website or about the builtin about:addons page ?

You can use this bookmarklet to open the Addons website version history page.

• javascript:void(location.pathname+='versions/');

noel_envode said

cor-el said

Is this about the Addons website or about the builtin about:addons page ?

Were talking about any Mozilla addon hosted page

If you need the version up there, you can run this little script, but of course extensions are disabled on AMO, so how would you do that automatically? Hmm...

document.querySelector('h1.AddonTitle').childNodes[0].textContent += ' ' + document.querySelector('dd.AddonMoreInfo-version').textContent;

cor-el said

You can use this bookmarklet to open the Addons website version history page.

• javascript:void(location.pathname+='versions/');

Thanks

jscher2000 said

If you need the version up there, you can run this little script, but of course extensions are disabled on AMO, so how would you do that automatically? Hmm... document.querySelector('h1.AddonTitle').childNodes[0].textContent += ' ' + document.querySelector('dd.AddonMoreInfo-version').textContent;

I'm sure you must know about this about:config entry

extensions.webextensions.restrictedDomains

Locate it up and empty all the domains, and then you can run addons.

But I don't know how to go about incorporating that script to test it

Yes, I don't recommend lettings all add-ons run on restricted Mozilla domains since the product allows elevated privileges on some of those domains.

You could create a userscript in Tampermonkey, Greasemonkey, or Violentmonkey to run the script.

jscher2000 said

Yes, I don't recommend lettings all add-ons run on restricted Mozilla domains since the product allows elevated privileges on some of those domains.

What are the possible consequences of of doing so?

You can of course run this JavaScript as a bookmarklet and ad the version data if you need it.

javascript:void(document.querySelector('h1.AddonTitle').childNodes[0].textContent+=' '+document.querySelector('dd.AddonMoreInfo-version').textContent);

noel_envode said

jscher2000 said

Yes, I don't recommend lettings all add-ons run on restricted Mozilla domains since the product allows elevated privileges on some of those domains.

What are the possible consequences of of doing so?

It depends on what the sites have access to. For example, on the Add-ons site, you can click a button to uninstall any installed add-on when you are on its page. On this site, you can click a Share Data button to provide data from the Troubleshooting Information page. On the Firefox Accounts site, well, let's not even broach the consequences.

jscher2000 said

It depends on what the sites have access to. For example, on the Add-ons site, you can click a button to uninstall any installed add-on when you are on its page. On this site, you can click a Share Data button to provide data from the Troubleshooting Information page. On the Firefox Accounts site, well, let's not even broach the consequences.

When you say "Add-ons site", do you mean about:addons, or any Mozilla addon hosted page?

Are there any domains you would feel comfortable with clearing from extensions.webextensions.restrictedDomains

noel_envode said

jscher2000 said

It depends on what the sites have access to. For example, on the Add-ons site, you can click a button to uninstall any installed add-on when you are on its page. On this site, you can click a Share Data button to provide data from the Troubleshooting Information page. On the Firefox Accounts site, well, let's not even broach the consequences.

When you say "Add-ons site", do you mean about:addons, or any Mozilla addon hosted page?

I mean https://addons.mozilla.org/

Are there any domains you would feel comfortable with clearing from extensions.webextensions.restrictedDomains

I have removed this site (support.mozilla.org) from the list so I can use some specific productivity and styling tools here. I understand this allows nosy extensions to extract large amounts of information about my Firefox if they want to (I trust them not to).