X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Why don’t mozilla addon pages have addon versions on the top

Kuphostiwe

This is a minor annoyance, but I don't understand the sense of it.

Firefox addon pages used to have the addon versions and dates at the top of the page, next to the addon name. Now you have to scroll halfway down the page to see this information.

Does this make sense to anyone?

This is a minor annoyance, but I don't understand the sense of it. Firefox addon pages used to have the addon versions and dates at the top of the page, next to the addon name. Now you have to scroll halfway down the page to see this information. Does this make sense to anyone?

Isisombululo esikhethiwe

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).

Funda le mpendulo ngokuhambisana nalesi sihloko 0
Isicaphuno

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Shockwave Flash 32.0 r0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Eminye Imininingwane

jscher2000
  • Top 10 Contributor
8758 izisombululo 71655 izimpendulo
Kuphostiwe

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?

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?
Ingabe lokhu kube usizo kuwena?
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17520 izisombululo 158427 izimpendulo
Kuphostiwe

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

Is this about the Addons website or about the builtin about:addons page ?
Ingabe lokhu kube usizo kuwena?
Isicaphuno

Umnikazi wombuzo

jscher2000 said

By the way, your Firefox reports it is version 68. Are you on the Extended Support Release channel?
I'm still in the midst of transitioning to Fx69. I had a bunch of custom buttons that no longer work in Fx 69, so I'm looking for the best addon replacements. Almost done.

cor-el said

Is this about the Addons website or about the builtin about:addons page ?
Were talking about any Mozilla addon hosted page
''jscher2000 [[#answer-1258953|said]]'' <blockquote> By the way, your Firefox reports it is version 68. Are you on the Extended Support Release channel? </blockquote>I'm still in the midst of transitioning to Fx69. I had a bunch of custom buttons that no longer work in Fx 69, so I'm looking for the best addon replacements. Almost done. ''cor-el [[#answer-1259001|said]]'' <blockquote> Is this about the Addons website or about the builtin about:addons page ? </blockquote>Were talking about any Mozilla addon hosted page

Okulungisiwe ngu noel_envode

Ingabe lokhu kube usizo kuwena?
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17520 izisombululo 158427 izimpendulo
Kuphostiwe

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

  • javascript:void(location.pathname+='versions/');
You can use this bookmarklet to open the Addons website version history page. * javascript:void(location.pathname+='versions/');
Ingabe lokhu kube usizo kuwena?
Isicaphuno
jscher2000
  • Top 10 Contributor
8758 izisombululo 71655 izimpendulo
Kuphostiwe

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;

''noel_envode [[#answer-1259338|said]]'' <blockquote> ''cor-el [[#answer-1259001|said]]'' <blockquote> Is this about the Addons website or about the builtin about:addons page ? </blockquote>Were talking about any Mozilla addon hosted page </blockquote> 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... <code>document.querySelector('h1.AddonTitle').childNodes[0].textContent += ' ' + document.querySelector('dd.AddonMoreInfo-version').textContent;</code>
Ingabe lokhu kube usizo kuwena?
Isicaphuno

Umnikazi wombuzo

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

''cor-el [[#answer-1259343|said]]'' <blockquote> You can use this bookmarklet to open the Addons website version history page. * javascript:void(location.pathname+='versions/'); </blockquote> Thanks ''jscher2000 [[#answer-1259345|said]]'' <blockquote> 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... <code>document.querySelector('h1.AddonTitle').childNodes[0].textContent += ' ' + document.querySelector('dd.AddonMoreInfo-version').textContent;</code> </blockquote> 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
Ingabe lokhu kube usizo kuwena?
Isicaphuno
jscher2000
  • Top 10 Contributor
8758 izisombululo 71655 izimpendulo
Kuphostiwe

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.

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.
Ingabe lokhu kube usizo kuwena?
Isicaphuno

Umnikazi wombuzo

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?

''jscher2000 [[#answer-1259363|said]]'' <blockquote> 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.</blockquote> What are the possible consequences of of doing so?

Okulungisiwe ngu noel_envode

Ingabe lokhu kube usizo kuwena?
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17520 izisombululo 158427 izimpendulo
Kuphostiwe

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);
You can of course run this JavaScript as a bookmarklet and ad the version data if you need it. <pre><nowiki>javascript:void(document.querySelector('h1.AddonTitle').childNodes[0].textContent+=' '+document.querySelector('dd.AddonMoreInfo-version').textContent);</nowiki></pre>
Ingabe lokhu kube usizo kuwena?
Isicaphuno
jscher2000
  • Top 10 Contributor
8758 izisombululo 71655 izimpendulo
Kuphostiwe

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.

''noel_envode [[#answer-1259443|said]]'' <blockquote> ''jscher2000 [[#answer-1259363|said]]'' <blockquote> 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.</blockquote> What are the possible consequences of of doing so? </blockquote> 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.
Ingabe lokhu kube usizo kuwena?
Isicaphuno

Umnikazi wombuzo

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

''jscher2000 [[#answer-1259490|said]]'' <blockquote>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. </blockquote> 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
Ingabe lokhu kube usizo kuwena?
Isicaphuno
jscher2000
  • Top 10 Contributor
8758 izisombululo 71655 izimpendulo
Kuphostiwe

Isisombululo Esikhethiwe

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).

''noel_envode [[#answer-1260406|said]]'' <blockquote> ''jscher2000 [[#answer-1259490|said]]'' <blockquote>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. </blockquote> When you say "Add-ons site", do you mean about:addons, or any Mozilla addon hosted page?</blockquote> I mean https://addons.mozilla.org/ <blockquote> Are there any domains you would feel comfortable with clearing from extensions.webextensions.restrictedDomains </blockquote> 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).
Ingabe lokhu kube usizo kuwena?
Isicaphuno
Buza umbuzo

Kufanele ulogele ukungena ku-akhawunti yakho ukuze uphendule amaphosti. Uyacelwauqale umbuzo omusha, uma ungekabi nayo i-akhawunti namanje.