Bug 1047140

Summary: some patches (scroll events, notification timeout, twitter api 1.1 fixes)
Product: [Fedora] Fedora Reporter: Fabrice Bellet <fabrice>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gwibber-3.4.2-10.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-03 08:31:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fix scroll events handling
none
Increase the notification bubble timeout (from 2 secs to 5 secs)
none
More fixes for twitter 1.1 API
none
Fix soup URI parsing none

Description Fabrice Bellet 2013-12-29 11:45:18 UTC
Hi!

I have patches, that solve some issues with gwibber, mainly the scroll events that are not handled uniformly depending on the widget the cursor in located on, and other fixes for twitter API 1.1.

Comment 1 Fabrice Bellet 2013-12-29 11:51:56 UTC
Created attachment 843057 [details]
Fix scroll events handling

This patch makes more widgets of the main timeline window aware of scroll events (mouse/kbd). The scrolling is still not smooth, and still has problems (for example, it doesn't remember when inline pictures are shown in the timeline), but it provides a more "predictable" behaviour, in the sense that all widgets that compose the timeline will now handle scroll events.

Comment 2 Fabrice Bellet 2013-12-29 11:56:22 UTC
Created attachment 843059 [details]
Increase the notification bubble timeout (from 2 secs to 5 secs)

This patch was needed with gnome2 notification daemon, to make notification bubbles stay a bit longer on screen (2 seconds to read a tweet may be a bit short :) It may still be useful with MATE.

Comment 3 Fabrice Bellet 2013-12-29 12:00:39 UTC
Created attachment 843060 [details]
More fixes for twitter 1.1 API

This patch adds some supplementary fixes to restore search capabilities in twitter with the 1.1 API (tweets searches and contact searches)

Comment 4 Fabrice Bellet 2013-12-29 12:08:59 UTC
Created attachment 843061 [details]
Fix soup URI parsing

This patch uses the url.fragment value of the soup URI parsed string, to pass search queries from the main timeline window to the search window (when clicking on a highlighted hashtag for example). The problem was that the hash symbol "#" is interpreted specifically by the URI parser as a separator, and args2[1] was always filled with an empty string. url.fragment seems to be the good variable to use in this case.

Comment 5 Fedora Update System 2013-12-30 19:26:35 UTC
gwibber-3.4.2-10.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gwibber-3.4.2-10.fc19

Comment 6 Fedora Update System 2013-12-30 19:26:47 UTC
gwibber-3.4.2-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gwibber-3.4.2-10.fc20

Comment 7 Fedora Update System 2013-12-31 09:52:37 UTC
Package gwibber-3.4.2-10.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gwibber-3.4.2-10.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-24164/gwibber-3.4.2-10.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-01-03 08:31:44 UTC
gwibber-3.4.2-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-01-09 07:43:45 UTC
gwibber-3.4.2-10.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.