BUG(?): FP10, is not compatible 100% with FP9

Question

I just finished a small part of a web site in my HD, and put
it online to test it in different screens.
The first thing I noticed was that in a computer with Flash
player 10, some sliders (that I had create) was invisible - this
would make the site bugged. In flash player 9 the sliders was
appearing correctly after the data was load, in both plugin + debug
utility.
I uninstalled Flash Player 10 from that computer and
installed Flash Player 9. All worked correctly.
To repeat the error, installed again FP10.. and yeap. The
sliders never appeared. Uninstall and revert to FP9, all work
properly.
I appose temporary the web site without thing that may
identify it:
http://web.xvp.gr/bug/
Try it in a browser with FP10, and in one with FP9. In FP9
the sliders will come up after the menus are loaded from the txt
files (in future from php files). In FP10 the sliders (for each
menu-box) will never be appear... This means that if I had sold
that site before the FP10 come out, then in a few months the site
would be dead and I'd had problems. Same if I do it now..
Thus this is an important bug - incompatibility, and should
fixed ASAP..... although I have no idea why is it happening.
If you think too that it is important, then tell to any
offical techician of Adobe to contact with me to share the .fla
codes in order to be found the problem, or tell me what should I
do... For now the project is frozen... :/

Answer 1

..I found a bug in the source code I had, and as it seems
it's problem of FP9 compiler/player and not FP10 player.
I was initializing a variable as: ScrY=5, and then used it as
Scry;; (not capital 'Y')... Compiler and FP9 player was taking
correct that value... But FP10 was placing that variable "ypos" at
a huge position, making the sliders out of screen. After correcting
the letter the FP10 showed correctly the sliders at their position.
The initialization was doing through objects creation:
tApp = {
Titl: {col: 0x554b44, tBold: true, Dy:-2, tItal:false,
tSize:18, tFont:"Myriad Pro", tAlign:"center" },
Def: {col: 0x322b27, tBold: false, Dy:0, tItal:false,
tSize:14, tFont:"Myriad Pro", tAlign:"center" },
Over: {col: 0x414da3, tBold: true, Dy:-1, tItal:false,
tSize: 14, tFont:"Myriad Pro", tAlign:"center"},
Sel: {col: 0x000000, tBold:true, Dy:-1, tItal:false, tSize:
14, tFont:"Myriad Pro", tAlign:"center"},
tWidth: 200, Scrx:228, ScrY: 5, ScrH:180
and used from the Object later as: scr.y=tapp.Scry; (where
tapp = tApp;).
Thus I guess Compiler couldn't check the error, at compiling
time.
And at runtime as tapp.Scry was undefined FP9 was giving it
0 value, while FP10 gave it undefined value (random memory value).
Thus in FP9 it was faken-working and FP10 produced the error...
Still, this is incopatibility that can destroy a site from
such a simple error made in FP9.... Just have it in mind if it ever
happens to you...