Closed Bug 297580 Opened 20 years ago Closed 20 years ago

Update button should check for updates on all extensions/themes

Categories

(Toolkit :: Add-ons Manager, enhancement)

Product:
Toolkit
Component:
Add-ons Manager
Platform:
x86
Windows XP
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: bugs.caleb, Unassigned)

Details

Currently, both the context menu update button and the big update button (at the
bottom of the EM/TM) do the same thing.

If an extension is selected then the big update button only does an update check
on that extension.

The problem is that newbies will find it difficult to do an update check for all
of their extensions/themes.

Reasons:

In order for the EM to check for updates on all the extensions you must deselect
all of them (click on an empty area). 
 * Some newbies won't realize this as easily as a tech savvy person.
 * With a long extension list, it becomes increasingly difficult to deselect

Also, the only "easy" way to do a mass update check (in FF1.1) is to go to Tools
> Options > Advanced > Update > Check Now.

I propose to have the update button that's at the bottom of the EM/TM to do a
mass update check, and the context menu one to do selective update checks.
-> Requesting aviray1.1 blocking
Severity: normal → enhancement
Flags: blocking-aviary1.1?
This looks a lot like bug 259057...
I was going to mention that bug in the report, but forgot to.

It's not quite the same.. that bug asks for being able to select multiple
extensions from the list (selective updates/disables/uninstalls on multiple
extensions)

This bug wants the update button to always do massive update checks :)
This is not intuitive but the update button already does a check of all items if
there are no items selected... just ctrl+click the selected extension (I believe
you have to do that twice and this issue will probably be resolved by bug
285584) and then click the update button.

As for making the update button check all when an item is selected I suspect
this is WONTFIX since it is possible to check all items by deselecting any
selected items and doing so is valid.
when I say "doing so is valid" I mean that checking just the selected item is
valid and checking all items with an item selected would be inconsistent in
regards to the other menu items like clicking the uninstall or options buttons
with an item selected.
(In reply to comment #5)
> when I say "doing so is valid" I mean that checking just the selected item is
> valid and checking all items with an item selected would be inconsistent in
> regards to the other menu items like clicking the uninstall or options buttons
> with an item selected.

You have a point about the consistency, but I still think it is not very newbie
friendly (doing ctrl+click, hell even I've never heard of that one).

You can mark as WONTFIX if you wish :)
(In reply to comment #6)
> You have a point about the consistency, but I still think it is not very newbie
> friendly (doing ctrl+click, hell even I've never heard of that one).
The majority of applications that I know of are written so that ctrl+click will
select and deselect a single item... this includes Windows explorer for files
and dirs for example. In this instance there is a single item already selected
so it is logical to think it would update just the single item as uninstall and
options do in the EM. Marking wontfix.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Flags: blocking-aviary1.1?
I have to agree that i didn't get that you could actually update all extensions
by unselecting the selected one. I learned that from this bug. 

I been using windows for ages and I do know you can ctrl + click to add more
items to the selected one, but that unselecting all of them would mean all of
them is not so intuitive.

Maybe have it the other way around, that when you open the extension manager,
that no extension is selected. Then clickin on the update button would do what
the user expected
I agree it isn't intuitive but having it automatically not have an extension
selected wouldn't help after it is open and an extension is manually selected.
Personally, I think the most intuitive solution without hurting existing
functionality is bug 259057.
it's all so ....
method to update

1.Extension manager                  
 --> extensions , 1 extension at the time

2.Themes manager 
 --> themes , 1 theme at the time

3.Menu-Help-Check for Updates
 --> all extensions, all themes and application (FF) simultaniously

4.Menu-Tools-Options-Advanced-Update
 --> application
 --> all extensions, all themes simultaniously

.... confusing, .... chaotic, ....poor design?

it's like we can't make up our mind of what we really want and instead add
entries to update just about anywhere.
Fixing bug 259057 is a nice solution, but that is only for powerusers, regular
users don't know you can ctrl + click something to select several things at the
time. 

But then again, I dont think that users like my father would even install
extension in the first place.

I fully agree with comment 10, there are too many places where you can update
extensions/themes, and they all seem to behave differently


(In reply to comment #10)
> it's all so ....
> method to update
> 
> 1.Extension manager                  
>  --> extensions , 1 extension at the time
> 
> 2.Themes manager 
>  --> themes , 1 theme at the time
Well, selected item or all items if none selected actually.

> 3.Menu-Help-Check for Updates
>  --> all extensions, all themes and application (FF) simultaniously
I personally would prefer it to not check extensions or themes so there is no
confusion as to what it is for... then again, I think most users just use it and
don't think on what it is for.

> 4.Menu-Tools-Options-Advanced-Update
>  --> application
>  --> all extensions, all themes simultaniously
> 
> .... confusing, .... chaotic, ....poor design?
> 
> it's like we can't make up our mind of what we really want and instead add
> entries to update just about anywhere.
Agreed though I don't mind the ability under the pref panel. I think it is clear
what it does in the pref panel due to the text and in the managers due to that
all the buttons apply to the selected item if selected - I do think the managers
need to be more intuitive for checking all but there hasn't been a suggestion I
would find more intuitive and I think the average user would just use auto-update.

(In reply to comment #11)
> Fixing bug 259057 is a nice solution, but that is only for powerusers, regular
> users don't know you can ctrl + click something to select several things at the
> time. 

> But then again, I dont think that users like my father would even install
> extension in the first place.
I think regular users will just use and get auto-notifications which would apply
in the example of your father if he did install an extension.
(In reply to comment #10)
 methods to update
 
 1.Extension manager                  
  --> extensions , 1 extension at the time
  --> rightclick contextmenu Update

 2.Themes manager 
  --> themes , 1 theme at the time
  --> contextmenu Update

 3.Menu-Help-Check for Updates
  --> all extensions, all themes and application (FF) simultaniously
 
 4.Menu-Tools-Options-Advanced-Update
  --> application
  --> all extensions, all themes simultaniously

if had forgotten the contexmenu update option

Robert, this is not meant as critisism, it's just an overview of how things have
evolved.

If you want to have anything added to the UI you are most likely to hit the
WONTFIX wall (which is good), but what's in the UI now should not be
protected/defended simply because it sneaked in during the past few years.

 

Peter - I didn't take it as criticism and I am in support of any improvement...
I just want to make sure it is an improvement vs. just creating a new bug with
the ui. I believe many would think it was a new bug if the update button in the
manager updated everything when an item was selected (e.g. different behavior
from the options and uninstall buttons) which is what this bug was about and why
it was marked WONTFIX. As far as the items you bring up I also agree and if
there were a bug about those issues I would be in support of it... I'm not
defending the current ui... just don't want to make it worse.
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.