[buddypress-trac] [BuddyPress Trac] #6005: No-js bulk deletion of messages
buddypress-trac
noreply at wordpress.org
Mon Nov 17 17:59:18 UTC 2014
#6005: No-js bulk deletion of messages
----------------------------------------+------------------
Reporter: lakrisgubben | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 2.2
Component: Messaging | Version:
Severity: normal | Resolution:
Keywords: needs-refresh dev-feedback |
----------------------------------------+------------------
Comment (by lakrisgubben):
I've uploaded a screenshot of a mockup using the 2014 theme. Seeing as
there's (depending on what we decide) going to need to be some new
functions written (mark single thread read/unread link amongst others) I
thought it'd be less work to first decide on a route we'd like to try and
then code the stuff. :)
So, the attached screenshot has gotten rid of the unread column totally,
and instead opts for having the total message count (which I think would
need a function if we'd decide to use it) in parenthesis after the senders
name. But it also has some extra screen-reader info that tells the user
about how many of those messages are unread. So the markup would look
something like:
{{{
<td width="30%" class="thread-from">
From: <a href="http://bp.dev/members/test/" title="test">test</a>
(3)<span class="bp-screen-reader-text">messages 0 unread</span>
<br>
<span class="activity">November 11, 2014 at 7:34 pm</span>
</td>
}}}
This might be too much, was just an idea I got when fiddling around with
the html. @hnla suggestion from comment16 would also work, even though if
the th says "unread" that column will be very wide considering that it'll
only contain a number.
The screenshot has also made the delete button a link and added
Read/Unread buttons on each thread. It only has bold on the first line of
the unread messages (if: from: user and subject). And removes the select
read/unread/all dropdown and replaces it with a bulk action (mark
read/mark unread/delete) dropdown.
Regarding the th-headings. The ones I've added should only be seen as
placeholders and would love to get some thoughts on what to name them,
maybe a native english speaker would be better at that than me. ;)
Any and all thoughts welcome!
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6005#comment:19>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list