The Incubator build is for development and testing, not regular everyday usage.

With all due respect tom, your comments are the very reason why Adobe tends not to let things publically available this early. They are afraid that people like you will make comments/judgements like this. You need to understand a little bit about software development, this is called an alpha build. Yes they say it's a public beta but it's just been released, it's so fresh any developer would still classify this as an alpha. Adobe is TRYING to open it's doors to us, it's trying to ditch the old secretive, cloak and dagger business model and give us a real opportunity to provide useful, contructive feedback. Not complaining about aeshtetics on a product that brand spanking new (essentially) and still in development. So I think I speak on behalf of the Adobe team when I say, you're welcome for the opportunity to get exclusive preview access to this free software you didn't have to pay a dime for.

Why would the watermark be there you think?

So people who use it see that they are actually using the correct webplayer and to remind everybody that this is a beta player.

You asked WHY, I believe that the reason is given above.

If they did not do this in past then its another thing. Obviously they decided to do it this time

You are such a polite person on the forum. Congratulation on your manners and have a good life. You're now on ignore here

afaik this is not a public release.

first: sorry for my englsh:

I think the problem is, that the most developers aren't 100% professionals. The most have only one computer for developing and for else.

So when you have installed flashplayer 11  every swf in the internet have the build information.

Couldn't it be possible to integrate in the context menu a button to switch display buidinformation on or off.

I think flashplayer 11 is also flashplayer10.2 without any bugs.

The bugs in the incubation build concern only the  core classes for 11??

And should one normal user download and install flashplayer, he should be aware of using the buildinformation.

OK. Perhaps a button in the context menu wouldn't be not so perfect, because normal users would forget using flashplaer11. But there should be a possibility to change a line in some configuration files to toggle display off.

Going one step further, it would be handy for testing to display actual info like render mode and fps automatically down there, too, because many demos don't do so, and we can only guess which demo seems to fall back to software mode in some environments.

I fully understand the watermark. GPU accelerated demos in flash are very interesting for a broad mass, and many non-developers will download the incubator build just to see some demos live. If there was no watermark, most users would leave this player as a standard as long as their daily flash apps like video portals i.e. are working. This behaviour could result in very many unstable builds around the world for a long time, even after final flash players 11 and even 12 are distributed.

The watermark is the best direct way to avoid this.

For those occasions where one wants the watermark to be invisible one can always make the stage high enough (or wide enough) such that the watermark is off the page.