Bug 370496 - [General] Generalize container select mode for *renderers.
Summary: [General] Generalize container select mode for *renderers.
Status: RESOLVED DUPLICATE of bug 381037
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Client (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: libing wang CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on: 377018
Blocks:
  Show dependency tree
 
Reported: 2012-02-02 15:55 EST by libing wang CLA
Modified: 2012-05-31 10:05 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description libing wang CLA 2012-02-02 15:55:18 EST 
I have implemented select all on any parent node level in search replace page.
You can toggle the checked sate on any root , file and match level and they affect children as well.
I've already injected a call back in the generic renderer and implemented in the search render. We can generalize it for broader use.
Comment 1 Susan McCourt CLA 2012-02-03 10:02:13 EST 
I think we wouldn't want this on by default, ie, navigator shouldn't get it without explicitly asking for it.  In the navigator case, you may want to select just the folder to do something to it (like copy move).
Comment 2 libing wang CLA 2012-02-03 10:41:05 EST 
(In reply to comment #1)
> I think we wouldn't want this on by default, ie, navigator shouldn't get it
> without explicitly asking for it.  In the navigator case, you may want to
> select just the folder to do something to it (like copy move).

Yes, I will hold on.
At least not for 0.4.
Comment 3 Susan McCourt CLA 2012-04-19 14:12:32 EDT 
renaming bug to talk about "container select" rather than "select all" since these are different.  Note also that in bug 377018 we are considering getting rid of checkboxes.
Comment 4 libing wang CLA 2012-05-31 10:05:25 EDT 
We are addressing more comprehensive issues in bug 381037.

*** This bug has been marked as a duplicate of bug 381037 ***