My bad.. your right dude... stupid www. - It gave me that fresh farm bull!... Couple of weeks ago someone here mentioned Adobe had dropped "Fireworks".. So I run over to Abobe to find out whats going on?...
Happens to the best of us -- I just recently screwed up on negative values in Z-index the same way; invalid in CSS 2.0, never noticed that it's valid in CSS 2.1 since most of 2.1 was never implemented properly, I never bothered with it.
Though that's why I took browser makers to task a few years ago -- gaping holes in the html 4.01 and CSS 2.1 specs, so lets start implementing HTML 5 and CSS3 before we finish off what's existed for a decade. Makes perfect sense
Feel free to rip me a new one when I screw up too.
There's a LOT of disinformation out there -- see the people making wild claims about B and I being deprecated, or the folks that turn "don't use tables for layout" into "don't ever use tables". Flash gets a lot of flak and a lot of it is just FUD by people who have an agenda... like raging against the evil corporations, or promoting vendor lock-in -- a laugh when it's both at once; see HTML 5 VIDEO and AUDIO. Raging against the 'evil' plugins by 'evil' corporations, by creating new tags redundant to what already exists (OBJECT) that seems to exist JUST to let browser makers shove their favorite codec/container combinations down our throats, with the end result we end up deploying bloated code five times worse than anything we used during the WMP vs. QuickTime vs. Realplayer wars of the late `90's. -- a war that Flash won when it wasn't even considered a player at the time.
Hell, there's a reason Hulu won't touch HTML 5 with a 20 foot cattle prod... and NetFlix only begrudgingly implements it in browsers that have implemented the DRM options that most of the freetards are raging against right now. and to be frank, on most systems you get better more reliable playback if you go into Netflix's options and set it back to using flash!