Bug 263128 - Not possible to search in threads
Summary: Not possible to search in threads
Status: RESOLVED DUPLICATE of bug 263118
Alias: None
Product: KMail Mobile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Windows CE Microsoft Windows CE
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-14 11:53 UTC by Bjoern Ricks
Modified: 2011-01-17 14:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
All mails in a thread a shown (34.77 KB, image/png)
2011-01-14 11:53 UTC, Bjoern Ricks
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bjoern Ricks 2011-01-14 11:53:25 UTC
Created attachment 56002 [details]
All mails in a thread a shown

It's not possible to search for a specific mail subject in a thread.

Steps to reproduce:
1) Write a mail to yourself
2) Reply to your mail and change the subject after receiving
3) Go to message list and open the thread
4) Start typing to search for the changed subject of the second mail

Results:
Both mails are still shown

Expected:
Only the second mail should be shown

Happens on maemo too.
Comment 1 Tobias Koenig 2011-01-17 14:10:48 UTC
Both bugs, 263118 and 263128, are caused by the fact, that the thread contents view does not have its own filter model and quick search line edit. With the current code base it is impossible to fix it without major changes, which might introduce new regressions -> the implementation will be delayed.

Notes for implementors: It seems we need a new state, which allows us to go from the thread content view to the message viewer and back (we have to store/restore the selection as well in this case). Furthermore the state machine must be extended (or rewritten with QSM) to support sub-states (to make context actions work) and to allow non-switchable states. The latter is needed to remove the ShowThreadContent state from the stack if the user selects a folder directly from the navigation bar.

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