Comment # 17
on bug 8854
from Christopher Maynard
(In reply to Guy Harris from comment #15)
> Does the change I just checked in fix the problem?
Indeed, zooming-in is limited to about 10 levels now (which is more than enough
on my screen at least, because even that is totally unreadable) and Wireshark
no longer crashes; however zooming-out too far still causes the hex pane to
become completely black as mentioned in comment #1.
Regarding the "mystery text entry box" mentioned in comment #3, that appears to
act like a "Go To packet #X" dialog; however, you can enter other number pad
characters such as /, *, -, and +, which obviously don't work for a "Go To
packet #X" dialog where only digits would make sense. If you do enter a valid
frame # though, then Wireshark does jump to that frame #, and if you hit
<enter>, the packet is opened in a new window. I'm not sure if this is
expected behavior or not, but if it is expected, then this feature appears to
be undocumented as far as I can tell. It "feels" more like some weird,
unintended behavior though.
You are receiving this mail because:
- You are watching all bug changes.