SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. save a web page as .html to ~/Downloads 2. delete the saved .html OBSERVED RESULT associated folder that contains various other files such as CSS, etc still remains EXPECTED RESULT associated folder for the deleted .html file should also be deleted since it is no longer useful SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel version: 5.13.0-22-generic
I see use cases where you'd want to keep site files without needing the .html file, this isn't a bug.
Created attachment 145008 [details] attachment-19124-0.html yes, for web developers perhaps, but not for the general public. ok, if not a bug, can it be a feature request? On 12/31/21 15:18, Yerrey Dev wrote: > https://bugs.kde.org/show_bug.cgi?id=447745 > > Yerrey Dev<yerrey@protonmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |yerrey@protonmail.com > > --- Comment #1 from Yerrey Dev<yerrey@protonmail.com> --- > I see use cases where you'd want to keep site files without needing the .html > file, this isn't a bug. >
(In reply to hong from comment #2) > Created attachment 145008 [details] > attachment-19124-0.html > > yes, for web developers perhaps, > but not for the general public. > ok, if not a bug, can it be a feature request? The feature request would need to be for the browser that saved the page as an html file and an adjacent folder. It could create a folder and save the items within, or it could save the page as a single file. There is no reliable way for Dolphin to know that the folder and the html file are associated. The only way to do this in Dolphin would be to employ a heuristic that needs to be kept in sync with the browser that saved the page. If the developers of that browser change their minds about how page saving works, Dolphin would need to support both the "old" way(s) and the "new" way. Each browser uses its own convention for saving pages, and thus Dolphin would need a heuristic for each of them. This is not sustainable.
Created attachment 145019 [details] attachment-16477-0.html got you. thanks a lot for your explanation! come to think of it, i believe in the old windows days, browser saved it as .mhtml and when the file was deleted (i guess with 'file explorer'), all disappeared. On 1/1/22 13:03, argonel wrote: > https://bugs.kde.org/show_bug.cgi?id=447745 > > argonel<argonel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |RESOLVED > Resolution|--- |DOWNSTREAM > > --- Comment #3 from argonel<argonel@gmail.com> --- > (In reply to hong from comment #2) >> Created attachment 145008 [details] >> attachment-19124-0.html >> >> yes, for web developers perhaps, >> but not for the general public. >> ok, if not a bug, can it be a feature request? > The feature request would need to be for the browser that saved the page as an > html file and an adjacent folder. It could create a folder and save the items > within, or it could save the page as a single file. > > There is no reliable way for Dolphin to know that the folder and the html file > are associated. The only way to do this in Dolphin would be to employ a > heuristic that needs to be kept in sync with the browser that saved the page. > If the developers of that browser change their minds about how page saving > works, Dolphin would need to support both the "old" way(s) and the "new" way. > Each browser uses its own convention for saving pages, and thus Dolphin would > need a heuristic for each of them. This is not sustainable. >