Ticket #2469 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

No scrollbar when viewing USB sticks in Journal

Reported by: jfuhrer Owned by: kimquirk
Priority: normal Milestone: Trial-3
Component: journal-activity Version:
Keywords: Cc:
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

OFW: Q2C18 Build: 535

I was able to get Journal to display a journal icon and opened it, looking at its contents. At first, it only displayed a couple files, then it quickly loaded all of them. However, there were more files than could display in one window. I did a search for some of the files that weren't displayed and found them, so I know that they were on the USB stick, but there was no scrollbar to get to them.

Attachments

tmpQWFVzI.png (59.9 kB) - added by jfuhrer 7 years ago.
Here's the entry list for the USB stick. The file go.sh is there, but isn't visible because there's no scrollbar.
tmpLoZKD2.png (19.3 kB) - added by jfuhrer 7 years ago.
Here's verification that go.sh is in fact on the stick (but was only visible after I did a specific search, becuase I could't scroll to it.)

Change History

Changed 7 years ago by tomeu

I'm having trouble reproducing this, Can you attach a screenshot?

You can take a screenshot with alt+1. This will create an image in the journal that you can upload directly from Browse.

Thanks!

Changed 7 years ago by jg

  • owner changed from tomeu to jfuhrer
  • milestone changed from Untriaged to Trial-3

Changed 7 years ago by jfuhrer

Here's the entry list for the USB stick. The file go.sh is there, but isn't visible because there's no scrollbar.

Changed 7 years ago by jfuhrer

Here's verification that go.sh is in fact on the stick (but was only visible after I did a specific search, becuase I could't scroll to it.)

Changed 7 years ago by jfuhrer

  • owner changed from jfuhrer to kimquirk

Reassigning to Kim.

Changed 7 years ago by tomeu

  • status changed from new to closed
  • resolution set to fixed

Scrolling has been heavily refactored since and this issue should have been solved (couldn't reproduce any more).

Note: See TracTickets for help on using tickets.