3 ms·
Considering it's still occurring in the most recent release of Flash Player 10, I'd say it's nothing like pointing out IE6 bugs at all. If they had actually fi
by stevenwei 17y ago
Considering it's still occurring in the most recent release of Flash Player 10, I'd say it's nothing like pointing out IE6 bugs at all.
If they had actually fixed that bug in the Flash plugin and people were using older versions, then you might have a point.
- radley 17y agoThe bug has to do with loading 5+ year old Flash 7/8 swfs. A better analogy would be he's making a stink about a Carbon bug for obsolete OS 8/9 apps. Carbon still ships with OSX and serves the same purpose as AVM1 in Flash Player: basic (but not perfect) backwards-compatibility for legacy code.
- stevenwei 17y agoI'm surprised that more priority hasn't been put into fixing it though. A bug that crashes the browser out in the wild for a year and a half? Someone malicious could do some pretty obnoxious things with it. Incidentally this use case isn't completely unheard of. There is still a lot of AS2 content out there that companies haven't bothered to migrate to AS3 yet (for whatever reason).
- bad_user 17y agoIf you don't have the resources for fixing old known bugs, then you should remove backwards compatibility, especially since bugs are caused by buffers/stack overflows / segmentation faults ... which could lead to unauthorized code executed on your machine. How else do you think botnets are made?