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

Michael Mann <mman...@netscape.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
                 CC|                            |mman...@netscape.net
           Hardware|Other                       |All
     Ever confirmed|0                           |1
                 OS|FreeBSD                     |All
           Severity|Major                       |Minor

--- Comment #1 from Michael Mann <mman...@netscape.net> ---
With 1.12.11 I can reproduce, but it's a little harder than the steps indicate,
so I'm lowing the priority.

If I select a packet in the Packet List and select Copy->Bytes->Hex stream
(from context sensitive menu), I can copy the entire packet.

If I select a field from the Packet Details menu and select Copy->Bytes->Hex
stream (from context sensitive menu), I can copy the field.

If I select a field from the Packet Details menu and the click again on the
(same) packet in the Packet List, and select Copy->Bytes->Hex stream (from
context sensitive menu) I get the "singular" field as the bug indicates. But
what I did notice is that the field in the Packet Details is selected, but
inactive.

When I click on a different packet (same protocol with same fields) in the
Packet List, the fields in the Packet Details are not selected at all, and I
get the "whole packet" again.

With Qt, clicking on the Packet List from the Packet Details clears the
selection of the field in the Packet Details, so I get the whole packet again
and never see the bug.

-- 
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://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to