After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 771602 - Text view sets spurious adjustment values
Text view sets spurious adjustment values
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
3.21.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-09-17 21:53 UTC by Kai Willadsen
Modified: 2018-05-02 17:33 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Simple python test case (619 bytes, text/x-python)
2016-09-17 21:53 UTC, Kai Willadsen 		Details

Description Kai Willadsen 2016-09-17 21:53:55 UTC 
Created attachment 335781 [details]
Simple python test case

If you set the value of a GtkTextView vertical adjustment to a non-integral value, GtkTextView normalises this to an integral value *and* re-sets it, causing the GtkAllocation to emit a spurious value-changed event.

For example, a program calls gtk_adjustment_set_value(adj, 100.5) on the textview's vadjustment and then receives *two* value-changed events: one to 100.5 and one to 100.0. Personally, I think it would be fine if it emitted one either of these events... just not both.

While a workaround has been applied (and it's fine) this caused a bug in Meld where, because we were getting value-changed adjustment events that didn't correspond to either our actions or user actions, scrolling broke.
Comment 1 GNOME Infrastructure Team 2018-05-02 17:33:00 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/675.