-
Notifications
You must be signed in to change notification settings - Fork 23.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMP] mail: make UI aware of first unread message #165973
[IMP] mail: make UI aware of first unread message #165973
Conversation
35043d3
to
6e0cbfa
Compare
409f713
to
384a028
Compare
384a028
to
8c68468
Compare
1cee8fd
to
b7ee458
Compare
f786d74
to
f81109b
Compare
f81109b
to
afc8e54
Compare
9e3c871
to
799c2ce
Compare
799c2ce
to
2fb7f14
Compare
e2131ea
to
56ac256
Compare
1dbdf91
to
2a623f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@robodoo delegate+
Ok for the extra commit now, this needs to be squashed
2a623f6
to
c7bfbc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@robodoo r+
9663bfc
to
9862809
Compare
Pushed to rebase and to fix an edge case (user didn't read any message). Before, we returned null meaning the new message separator was not displayed. Now, we return the first message. |
63d126c
to
8c8eea5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@robodoo delegate+
@robodoo r+ |
This task aims at allowing the user to scroll to the first unread message. In order to do so, we need to determine which message is the first unread message. Until now, this information was only computed as part of the rendering process. This commit introduces this information as part of the thread model state instead. part of task-3551627
8c8eea5
to
19b7c2f
Compare
@robodoo r+ |
This task aims at allowing the user to scroll to the first unread message. In order to do so, we need to determine which message is the first unread message. Until now, this information was only computed as part of the rendering process. This commit introduces this information as part of the thread model state instead. part of task-3551627 closes #165973 Signed-off-by: Matthieu Stockbauer (tsm) <tsm@odoo.com>
This task aims at allowing the user to scroll to the first unread message. In order to do so, we need to determine which message is the first unread message. Until now, this information was only computed as part of the rendering process. This commit introduces this information as part of the thread model state instead. part of task-3551627 closes odoo#165973 Signed-off-by: Matthieu Stockbauer (tsm) <tsm@odoo.com>
Until now, the new message separator was computed during rendering.
This task aims at allowing the user to scroll to the first unread
message. In order to do so, we need to determine which message is
the target of the new message separator.
This commit introduces this information as part of the thread model
state.
part of task-3551627