THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1242 - "Client got tagged with wrong tag"
User who did this - Daniel Hahler (blueyed)
----------
> Doesn't that mean that the parent (the main firefox window) must already have
> had a wrong tag?
It could also mean that a property::screen handler was involved, given that the
code was triggered, although awesome was starting up (see the PR above).
Some more thoughts, but maybe irrelevant now:
Couldn't it be possible that tag.withcurrent is already connected, interfering
here?
c:connect_signal("property::screen", tag.withcurrent)
Another source of interference might be the layout handler:
capi.client.connect_signal("property::screen", function(c)
for screen = 1, capi.screen.count() do layout.arrange(screen) end end)
----------
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1242#comment3948
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
