Remaining OpenFL 8 issues

This is the list of currently known issues still remaining with OpenFL 8. Most of them are fairly minor. The ones I consisder most important are printed in bold.

• Performance:

  • On some systems, FlxBunnyMark is significantly slower with drawQuads than drawTiles - note that the "bunny-performance" is close to identical, the culprit seems to be UI elements and/or textfields (press space to toggle)
  • Performance in the FlxSpriteFilters demo is bad when animations are enabled

• Shaders:

  • The scanline effect in the Filters demo isn't quite correct (there's a "flickering")
  • The dropdowns in the BlendModeShaders demo vanish when used
  • openfl_TextureSize doesn't seem to work in regular per-sprite filters, only shader filters (see MosaicEffect demo)

• HTML5:

  • The Filters demo produces an out of memory crash
  • There are "Could not generate web font" warnings on the first build

• Misc:

  • FlxPreloader doesn't seem to behave correctly on Flash
  • The debugger buttons look broken on some systems (https://github.com/openfl/openfl/issues/1857)
  • The DynamicShadows demo is broken (https://github.com/HaxeFlixel/flixel-demos/issues/252)
  • Flixel's fonts aren't working on some old Android devices (https://github.com/openfl/lime/issues/885)
  • FlxBitmapText.textColor doesn't work as expected (https://github.com/HaxeFlixel/flixel/issues/2143#issuecomment-383978432)

Start by reproducing the unchecked items in the FlxBunnyMark and FlxSpriteFilters demos, then read the linked FlxBitmapText.textColor comment. Compare drawQuads and drawTiles with UI or text elements enabled, check animation performance, and verify the text-color behavior. Done means the remaining issues are either fixed and verified or documented with a narrowed cause.