Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gtk gtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,434
    • Issues 1,434
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 246
    • Merge requests 246
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • gtkgtk
  • Issues
  • #929

Closed
Open
Created Oct 01, 2017 by Bugzilla@bugzilla-migration💬Reporter

[PATCH] GtkListBox: Rows remain selected after they have been removed

Submitted by Jonathan Moerman

Link to original bug (#788393)

Description

If a selected row is removed, is_selected () still returns true, which causes buggy behavior if it is added to GtkListBox. It can lead to multiple rows being selected, even if the selection mode is GTK_SELECTION_BROWSE or GTK_SELECTION_SINGLE, and it is not possible to change the selected row to those rows.

A workaround is to temporarily change the selectable property to false.

Tested with 3.18.9, from the code it looks like this bug is present in 3.22 and in master.

While selected rows are not commonly removed and then added it would be nice if this weird behavior would be fixed in the next stable version of Gtk+.

Version: 3.22.x

Assignee
Assign to
Time tracking