Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1271516 - wayland: scrolling on breadcrumbs doesn't work
Summary: wayland: scrolling on breadcrumbs doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: WaylandRelated
TreeView+ depends on / blocked
 
Reported: 2015-10-14 08:02 UTC by Fabio Valentini
Modified: 2016-04-07 15:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-07 15:27:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fabio Valentini 2015-10-14 08:02:36 UTC
Open nautilus, change to a directory that overflows the headerbar space for breadcrumbs. Scroll on the headerbar to move crumbs left / right.

Actual results:
does nothing under wayland.

Expected results:
moves crumbs to left / right under X.

This might be another instance of mutter not passing on scroll events correctly, but that is just speculation on my end.

Version-Release number of selected component (if applicable):
nautilus-3.18.0-1.fc23.x86_64
gtk3-3.18.1-1.fc23.x86_64

Comment 1 Fabio Valentini 2015-11-11 12:21:41 UTC
This still doesn't work with
gtk3-3.18.2-1.fc23.x86_64 and
nautilus-3.18.1-1.fc23.x86_64.

Any chance this will get fixed - as it is really annoying.

Comment 2 Kamil Páral 2015-11-18 13:44:32 UTC
I can reproduce this.

Comment 3 Christian Stadelmann 2016-04-07 13:56:58 UTC
This issue has been closed upstream for nautilus and gtk+ 3.20. It can be closed now.


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