Comment 577 for bug 263435

This is my understanding of the issue. After getting 'click to play' enabled builds of Firefox and when you click on a "ctp" content, Firefox loses focus just like how it did even before ctp came out(you can tell when the (tested in windows 8) layout/theme color fades when a window loses focus in ctp builds) which is the bottom line. Firefox loses focus in order to start the plugin, restored after clicked on the content with mouse.
The hurdle is to merge the plugin content with the Firefox layout without both losing focus amirite?

(In reply to Tim H. from comment #561)
> with the recent trend to "rapid releases", better described as "constantly
> broken"; and the attempt to turn it into a visual clone of Chrome, I decided
> to just use Chrome instead.

The memory improvements you might be seeing these days in the "rapid release" builds are because of the implementation speeds based off the rapid release schedules.Don't tell me you like slow browsers (many benchmarks even prove Firefox handles memory much better than chrome these days). There are changes to designs proposed for Firefox and are already being worked on. These designs are a big improvement to what you see now, more space to view content compared to earlier versions. Now, why all such hate on the new theme especially when both of us know its better than it ever was. Mozilla gets it that some people don't like the theme which is why new designs are on the table. Wait till it gets out, constant complaining about known matters don't help much unless you have a patch that can be reviewed on what you want.

This is for everyone from here.