| Summary: | Konqueror does not save file in typed location. | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Denis <auronius> |
| Component: | tdebase | Assignee: | Michele Calgaro <michele.calgaro> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | auronius, bugwatch, michele.calgaro |
| Priority: | P5 | ||
| Version: | R14.0.1 [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2575 | ||
|
Description
Denis
2016-05-20 06:21:46 CDT
Hi, after you type the new folder (MenuetOS) you are supposed to press enter so that the new location is used. If you already have something in the new folder, you should see the contents of the folder get dispayed on the dialog. Then continue with download. When you select from side menu, this does not happen because you choose the location directly. Try and let us know. However I think it is worth considering this a bug. If the user types a new URL but forgets to press enter, at the time he pressed the "continue" button the new location should be used. When I type ENTER after typing folder name, the file is saved correctly in typed location. However it would be much better, if user would not be obliged to type ENTER, and typed location for saving would be applied automatically after clicking on "Continue" button. > However it would be much better, if user would not be obliged to type ENTER, > and typed location for saving would be applied automatically after clicking on > "Continue" button. Yes, that is what I said in comment 2, so we are going to consider this a bug. There are actually two bugs in one. - if the user type the path without pressing enter - if the user partially type and then select the path from the autocompletion combobox that appears, without pressing enter at the end. In both scenarios, the new path is not used. Fixed in commit 53e36f6 (R14.1) and c8ff908 (R14.0) Commits 53e36f6d (master) and c8ff908d (r14.0.x) have been reverted and the problem fixed in a different way in commits 05bcfa76 (master) and 4c096c2 (r14.0.x). |