Bugzilla – Full Text Bug Listing
| Summary: | Column based New File... has side effect on Task Bar New File | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Ken Walker <ken_walker> |
| Component: | Client | Assignee: | Susan McCourt <susan> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 0.3 | ||
| Target Milestone: | 0.4 M1 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Ken Walker
this bug could be "just fixed" but it also begs the question. Should the parameter slideout be modal to all commands? If you execute some command, even if it doesn't use parameters or slideout, should that close the active slideout? Probably so....because the user could likely change the page context such that the command invocation (active item, etc.) doesn't make sense anymore. If you leave up a New File and navigate somewhere else, then decide to use it, the wrong thing works. Same with New Folder. Sorry, I mean does not work properly. Where you are in the Navigator isn't necessarily where the result takes place. (In reply to comment #3) > Sorry, I mean does not work properly. Where you are in the Navigator isn't > necessarily where the result takes place. exactly. That's what I meant by... >user could >likely change the page context such that the command invocation (active item, >etc.) doesn't make sense anymore. Right now the slideout knows who was active when it was invoked. fixed with d493130ad60ba071920cb7d5152d7ec64975653d 1 - the parameter collector still had the slideout page id hardcoded in places where instead it had to remember its invocation context. That fixed the "grow a pair" problem 2 - if we rerender commands for which there is an open parameter collector, we close it. So if the commands are rebound to a new context (like when you drill in the navigator) the slideout closes. . |