Ticket #10514 (assigned defect)

Opened 3 years ago

Last modified 15 months ago

Scrolling using the arrow keys or dpad in Browse

Reported by: erikos Owned by: humitos
Priority: normal Milestone: Future Release
Component: browse-activity Version: Development build as of this date
Keywords: Cc: dsd
Action Needed: code Verified: no
Deployments affected: Blocked By:
Blocking:

Description

- open a pdf in Browse

- try to scroll with the arrow keys or the dpad

- the scrolling behavior is inverted (up scrolls down, down scrolls up)

This is because by default the Spinbutton has the focus. And 'up' means here increment the page number (going down) and 'down' means here decrement the page number (going up).

I think the interface is a bit misleading. I think we should use the same interface as Read to be consistent.

Attachments

Change History

Changed 3 years ago by erikos

  • cc manuq added

Changed 3 years ago by erikos

Manuel, as you have been working on the scroll/dpad interface in Read lately maybe this one is something for you.

Changed 3 years ago by manuq

Thanks Simon, I will check.

Changed 3 years ago by manuq

I'm about to send a patch that will add Browse key bindings for pdf that are consistent with Read.

The focus issue is still present. I found that the pdf window is focused when:

  • I change to another activity and then come back to Browse.
  • I click on any Browse tool button and then move the cursor to the pdf area.
  • I do two grabs (click and drag) with the mouse over a text in the pdf, trying to select it.

The focus issue does not happen when browse is started as a previous activity, being the last visited page a pdf.

I tested adding needs_xembed to the configuration file of mozplugger, as it's man page states, but it doesn't solve the problem.

Changed 23 months ago by dsd

  • cc dsd added; manuq removed
  • owner changed from erikos to manuq
  • milestone changed from 11.3.0 to Future Release

In 12.1.0 this is better, but when opening a PDF file the focus is not transferred. So the user must click on the PDF for no apparent reason before these controls become functional.

Changed 15 months ago by humitos

  • owner changed from manuq to humitos
  • status changed from new to assigned

We should add a grab_focus on the Evince widget when the switch-page signal is emitted.

Note: See TracTickets for help on using tickets.