1307014 - GTK: Sort arrow not hidden from column when column in front is selected until hover

Status: RESOLVED WORKSFORME

(Toolkit :: UI Widgets, defect)

Description

[eerruzzie]

Attachment: both the "Date" and "From" columns show the sorting arrow, after sorting switched from "Date" to "From"

If you change the column used for sorting the message list, the column which was previously used for sorting continues to display the sorting arrow until you hover your mouse over it, at which point the arrow disappears. See screen capture showing both "Date" and "From" columns having the sorting arrow, after having switched the sorting from "Date" to "From".

Comment 1

[Jorg K (CEST = GMT+2)]

Which platform is this? Do you use hardware acceleration?

Comment 2

[eerruzzie]

Linux. I don't believe hardware acceleration is enabled. about:support says:
GPU Accelerated Windows: 0

Comment 3

[Jorg K (CEST = GMT+2)]

I think HWA is disabled by default, also on Linux. Look, there are so many distros that it's very hard to get them all to work. Which distro are you using? And it's x64? I've CC'ed our UI expert, let's see what he says.

Comment 4

[Richard Marti (:Paenglab)]

I can confirm it on Kubuntu. But also with Firefox's Bookmark Library:

With the default columns Name, Tags and Location, select first the Name column to show the sorter arrow, then the Tags and then the Location. Everything looks okay. But now select the Tags again. The arrow on Location stays. Don't hover the Location column but select the name column. Now all three columns have the arrow. With hovering Tags and Location the arrows disappear.

Now rearrange the Tags and Location columns so they are Name, Location and Tags. Now do the same as above from left to right and then from right to left. When clicking on Locations the tags arrow disappears but the Locations arrow stays when selecting the Name column.

Comment 5

[eerruzzie]

I'm using Fedora (Mate Desktop) and it's 64-bit.

Comment 6

[eerruzzie]

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=836aa9658341&tochange=831f8e040f38

Comment 7

[eerruzzie]

this is no longer an issue in the current release