https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16318

            Bug ID: 16318
           Summary: Avoid moving the selected packet when
                    applying/removing display filters.
           Product: Wireshark
           Version: 3.0.7
          Hardware: x86-64
                OS: Windows 10
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: Low
         Component: Qt UI
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: j...@mccabe.org.uk
  Target Milestone: ---

Build Information:
Version 3.0.7 (v3.0.7-0-g9435717b91f5) 
Copyright 1998-2019 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software;
see the source for copying conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 
Compiled (64-bit) with Qt 5.12.6, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.39.2, with LZ4, with Snappy, with
libxml2 2.9.9, with QtMultimedia, with AirPcap, with SBC, with SpanDSP, with
bcg729. 
Running on 64-bit Windows 10 (1909), build 18363, with Intel(R) Core(TM)
i5-4590S CPU @ 3.00GHz (with SSE4.2), with 16306 MB of physical memory, with
locale English_United Kingdom.1252, with Npcap version 0.9983, based on libpcap
version 1.9.1-PRE-GIT, with GnuTLS 3.6.3, with Gcrypt 1.8.3, without AirPcap,
binary plugins supported (14 loaded). Built using Microsoft Visual Studio 2017
(VC++ 14.16, build 27034). 
Wireshark is Open Source Software released under the GNU General Public
License. 
Check the man page and https://www.wireshark.org for more information. 
--
If a packet is selected in the capture view, and a display filter is applied or
removed, the selected packet moves to the bottom of the capture view (assuming
there are enough packets to fill the view above that point - but that's a
special case!). It would be nice to be able to keep the selected packet at the
same position rather than have it move.

Here's an example to illustrate what happens now, with 3.0.7. Say I have the
following (summary) displayed:

----
 58 DNS
 59 IGMPv2
 60 UDP
 61 IGMPv2
 62 IGMPv2
 63 IGMPv2
 64 IGMPv2
 65 ARP
 66 WireGuard
 67 WireGuard
 68 TCP
----

I select packet 60 then apply UDP as a filter. The capture window changes to:

----
 49 DNS
 50 DNS
 51 DNS
 52 DNS
 53 DNS
 54 DNS
 55 DNS
 56 DNS
 57 DNS
 58 DNS
 60 UDP <- selected packet moves to the bottom
----

Now, if I scroll so that packet 60 is in the middle of the capture list I get:

----
 54 DNS
 55 DNS
 56 DNS
 57 DNS
 58 DNS
 60 UDP
 66 WireGuard
 67 WireGuard
 91 WireGuard
 92 DNS
 93 DNS
----

Then finally, with packet 60 still selected, I delete the capture expression
and get:

----
 50 DNS
 51 DNS
 52 DNS
 53 DNS
 54 DNS
 55 DNS
 56 DNS
 57 DNS
 58 DNS
 59 IGMPv2
 60 UDP <- selected packet moves to the bottom again
----

This enhancement request suggests a change such that the behaviour is more like
as follows. Start with the same as before:

----
 58 DNS
 59 IGMPv2
 60 UDP
 61 IGMPv2
 62 IGMPv2
 63 IGMPv2
 64 IGMPv2
 65 ARP
 66 WireGuard
 67 WireGuard
 68 TCP
----

I select packet 60 then apply UDP as a filter. The capture window changes to:

----
 57 DNS
 58 DNS
 60 UDP <- selected packet remains where it was
 66 WireGuard
 67 WireGuard
 91 WireGuard
 92 DNS
 93 DNS
 96 DNS
 97 DNS
 99 DNS
----

Now, if I scroll so that packet 60 is in the middle of the capture list I get:

----
 54 DNS
 55 DNS
 56 DNS
 57 DNS
 58 DNS
 60 UDP
 66 WireGuard
 67 WireGuard
 91 WireGuard
 92 DNS
 93 DNS
----

Then finally, with packet 60 still selected, I delete the capture expression
and get:

----
 55 DNS
 56 DNS
 57 DNS
 58 DNS
 59 IGMPv2
 60 UDP <- selected packet remains where it was
 61 IGMPv2
 62 IGMPv2
 63 IGMPv2
 64 IGMPv2
 65 IGMPv2
----

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to