Welcome to awesome bug tracking system.

FS#642 - Titlebar left on the starting tag after movetotag happens

Attached to Project: awesome
Opened by anrxc (anrxc) - Sunday, 27 September 2009, 23:28 GMT
Last edited by Julien Danjou (jd) - Monday, 28 September 2009, 13:07 GMT
Task Type Bug Report
Category Core
Status Closed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version git/master
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


I caught a problem with titlebars.

First, I have a Firefox rule:

{ rule = { class = "Firefox", instance = "Navigator" },
properties = { tag = tags[screen.count()][3] }

Second, I have a piece of code in my manage signal function that adds a titlebar to each floating client, or every client if we are on a floating layout.

if awful.client.floating.get(c) or
awful.layout.get(c.screen) == awful.layout.suit.floating
if not c.titlebar then awful.titlebar.add(c, { modkey = modkey }) end

If I am on a tag with floating layout and I start Firefox, because of the current awesome 3.4 behaviour the client is first visible on the starting tag before being moved (with flashes and every thing else... you know).

Problem for this report is that the client titlebar is left visible on the starting tag after the client has been moved. If I do anything to force re-arranging the screen (like starting another client) the titlebar will vanish. The attached image shows the problem, a titlebar left on the starting tag.

This task depends upon

Closed by  Julien Danjou (jd)
Monday, 28 September 2009, 13:07 GMT
Reason for closing:  Works for me
Additional comments about closing:  Apparently fixed recently somehow.