A little more about the wmode bug. It only happens in Firefox on Windows, when you set the wmode parameter in the embed tag in your HTML. A number of things happen when setting this wmode parameter:

• The function Key.isDown() always returns false.
  If you're using the Key.isDown() function in an onKeyDown handler, just use the Key.getCode() function. Key.getCode() works fine, and it is made for use in onKeyDown handlers. But I noticed that some people (who are colleagues of mine)  use the Key.isDown() function in an onKeyDown handler.
  If you really need the Key.isDown() function, to test if a key is still down in  a loop or between frames, you must use a workaround. Something like this will do:
  

  var spaceDown:Boolean = false;
  this.onKeyDown = function() {
  	if (Key.getCode(Key.SPACE)) spaceDown = true;
  }
  this.onKeyUp = function() {
  	if (Key.getCode(Key.SPACE)) spaceDown = false;
  }
  this.onEnterFrame = function() {
  	if (spaceDown) {
  		// whatever you want to do when the SPACE key is pressed
  		trace ("SPACE"); 
  	}
  }
  Key.addListener(this);

  This issue and solution is also posted here.
  
• When entering text in a textfield the wrong keymapping is used (for some keys) instead of the user's keymapping. This bug will often show up when entering an email address. The @ key will put something else in the text field. In my case a é character , but British users seem to get a double quote, Germans get a q, French users get something else, etc
  As far as I know there is no workaround for this.

• A problem with hitareas and positioning
  
• A problem with the mousewheel
• The I-beam pointer is not showing properly in a textfield