Bug 1747625 - Details pane in "Weather Report" window isn't scrollable with keyboard
Summary: Details pane in "Weather Report" window isn't scrollable with keyboard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-weather-plugin
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-31 08:18 UTC by Vadim Raskhozhev
Modified: 2020-05-19 02:52 UTC (History)
1 user (show)

Fixed In Version: xfce4-weather-plugin-0.10.1-2.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-19 02:52:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Xfce 15912 0 None None None 2019-09-01 18:30:12 UTC

Description Vadim Raskhozhev 2019-08-31 08:18:27 UTC
Description of problem: details pane in "Weather Report" window can be scrolled with mouse only. This is deadly annoying on laptops and their touchpads as the only tracking device.

Version-Release number of selected component (if applicable): 0.10.0

How reproducible: always

Steps to Reproduce:
1. Open "Weather Report"
2. Switch to "Details" pane (either arrow keys or ^PgUp/^PgDn would do)
3. Press down key, PgDn, space bar…

Actual results: nothing happens

Expected results: window scrolls down

Additional info: it workes on 0.8.11; probably this breakage is due to gtk3 transition.

Comment 1 Mukundan Ragavan 2019-08-31 17:38:52 UTC
Can you file this upstream or would like me to?

Comment 2 Mukundan Ragavan 2019-09-01 18:30:13 UTC
I have reported this upstream. Let's see what they say.

Comment 3 Vadim Raskhozhev 2019-09-02 00:08:48 UTC
(In reply to Mukundan Ragavan from comment #2)
> I have reported this upstream. Let's see what they say.

Thanks. Let's see

Comment 4 Ben Cotton 2020-04-30 21:13:18 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora Update System 2020-05-10 14:00:00 UTC
FEDORA-2020-93f15dfa11 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-93f15dfa11

Comment 6 Fedora Update System 2020-05-11 03:33:30 UTC
FEDORA-2020-93f15dfa11 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-93f15dfa11`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-93f15dfa11

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-05-19 02:52:27 UTC
FEDORA-2020-93f15dfa11 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.