Flash 11 Fullscreen with Awesome WM [SOLVED]

Intrepid · 2011-10-11 20:04:45

Hey all,

I have read in the forums that by taking out web browsers from the "rules" section in rc.lua, flash would automatically go fullscreen in awesome.
However, even without said rules, flash 11 fullscreen video gets tiled for me in awesome 3.4. Eventually it becomes embedded again in the browser window. This works the same in all browsers.

The only workaround--which is not ideal--is to make it floating as it gains focus.
Does anyone know anything I can do for it to "just work" like it did in awesome 3.3? Thanks.

Last edited by Intrepid (2011-10-11 22:53:34)

kalhartt · 2011-10-11 20:51:12

I had to add a rule instead of removing one.

awful.rules.rules = {
    .......
    { rule = { instance = "plugin-container" },
        properties = { floating = true } },
}

Intrepid · 2011-10-11 21:24:02

@kalhartt, While that should work in theory, it did not work here. I can confirm that flash is technically run as "plugin-container" in firefox.

itti · 2011-10-11 22:30:15

I identify the flash overlay window via it's class (which seems to change from release to release). At the moment my flash fullscreen rule looks like this:

...
 { rule = { class = "Exe"}, properties = {floating = true}
...

One can find out the overlay window's class with xprop. Just run

sleep 5 && xprop

in a terminal and go into fullscreen flash. Then when the xcursor changes to a target cursor click on the overlay and analyze the xprop output in the terminal.

Last edited by itti (2011-10-11 22:32:29)

Intrepid · 2011-10-11 22:53:16

@itti, thanks, I was looking for that! I was using xprop before but never was able to catch the flash window in time. Using sleep helped a lot!

ddidderr · 2012-12-17 20:52:06

@itti, thanks! Window class "Exe" works. I did the xprop before and there was nothing with "Exe" in the output. WM_CLASS was "plugin-container" as well as WM_NAME. No occurence of the string "Exe". But it works when I tell awesome class = "Exe' and it does not work if I tell awesome class = "plugin-container" (which is what the output of xprop says). So HOW did you figure that out? And what is wrong?

ZenKen · 2013-01-08 15:37:03

For me it was

class = "Plugin-container"

Lowercase "plugin-container" and "Exe" didn't work, and xprop reports:

[...]
WM_CLASS(STRING) = "plugin-container", "Plugin-container"
[...]

So anyone seeing this, just be sure to check the case.

pectopah · 2014-07-17 01:33:34

Suggesting this approach:

client.connect_signal("focus", function(c) 
 if  c.name == "plugin-container" then  
    flash_client = c
    mt = timer({timeout=0.1})
    mt:connect_signal("timeout",function() flash_client.fullscreen = true
    mt:stop() end)
    mt:start()      
 end
end)

Arch Linux

#1 2011-10-11 20:04:45

Flash 11 Fullscreen with Awesome WM [SOLVED]

#2 2011-10-11 20:51:12

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

#3 2011-10-11 21:24:02

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

#4 2011-10-11 22:30:15

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

#5 2011-10-11 22:53:16

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

#6 2012-12-17 20:52:06

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

#7 2013-01-08 15:37:03

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

#8 2014-07-17 01:33:34

Re: Flash 11 Fullscreen with Awesome WM [SOLVED]

Board footer