Bug 321180 - Show tags in Files even if no file of the currently selected type is associated with it
Summary: Show tags in Files even if no file of the currently selected type is associat...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Active
Classification: Plasma
Component: Applications (show other bugs)
Version: Master
Platform: Other Linux
: NOR wishlist
Target Milestone: PA 4
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-15 14:28 UTC by Thomas Pfeiffer
Modified: 2019-04-23 15:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Pfeiffer 2013-06-15 14:28:39 UTC
Currently if one tags e.g. some documents with a certain tag, then goes back to the file type selection, selects images and goes back to tags, that tag is not shown.
This prevents people from associating files of different types with the same tag in Files. The only way to do so is via SLC.
This is a big limitation because it is certainly not uncommon to tag files of different types with the same tag.

Reproducible: Always

Steps to Reproduce:
1. Open Files
2. Select a file type
3. Tag some files of that type with a new tag
4. Select a different file type
5. Go back to the Tags tab
Actual Results:  
The previously created tag is not shown

Expected Results:  
The tag is shown
Comment 1 Thomas Pfeiffer 2013-08-09 12:24:42 UTC
Marco tries to find a way to solve this.
Comment 2 Marco Martin 2013-08-09 15:17:47 UTC
probably fixed by http://commits.kde.org/plasma-mobile/f121a819b7169d1160b21978e84f04ae8ffe594f
Comment 3 Thomas Pfeiffer 2013-08-09 20:34:09 UTC
What works:
- Tag is displayed for file type where no file is associated
- Tagging a file of a new type with existing tag

What does not work
- Selecting the previously "empty" tag after tagging a file of the currently selected type with it is not possible. It only becomes selectable when I switch to another file type and back
Comment 4 Thomas Pfeiffer 2013-08-09 20:50:56 UTC
While testing the behavior after this fix, I stumbled upon another problem which may or may not be related to this. I've opened a new bug 323321