Re:Adobe confirms: no Flash for Chrome on Android
by ThomPete on Wednesday February 08, 2012 @09:18AM
(#3566584)
So does HTML+CSS+JS
I still have a hard time seeing the point here
Re:Adobe confirms: no Flash for Chrome on Android
by gsa on Wednesday February 08, 2012 @09:40AM
(#3566669)
With Flash, the user or the developer has no choice if scroll and keyboard shortcuts break. With JS+HTML+CSS, the user has a choice to force the developer to fix their code (and a developer to not write code which breaks browser stuff).
Re:Adobe confirms: no Flash for Chrome on Android
by talmand on Wednesday February 08, 2012 @10:07AM
(#3566788)
How exactly does a user "force" a developer to fix their code when they use HS+HTML+CSS?
Re:Adobe confirms: no Flash for Chrome on Android
by gsa on Wednesday February 08, 2012 @10:49AM
(#3566949)
Answering both ThomPete and talmand here:
In Flash, browser shortcuts like ^L are always broken and you have no choice about that, because that's the way Flash is designed. If a similar thing happens in a non-Flash environment, it's because the developer designed it so.
If many users complain to the developer about stuff being broken, it has to count for something.
Re:Adobe confirms: no Flash for Chrome on Android
by talmand on Wednesday February 08, 2012 @01:56PM
(#3567870)
Again, how do they "force" developers to fix their code? Asking nicely is one thing but forcing is another. You implied that the user has more control over the developer in a JS+HTML+CSS environment over Flash. Plus, if some commonly used commands are broken in Flash then it's broken in all of them which doesn't mean broken; it means unsupported, there's a difference.
Exactly, and that's the problem. It means that it behaves the way the author wants it to, ignoring the users preferences. That is poor usability. I have lots of small annoyances with Flash, take for example the inability to auto-scroll across it (at least in Firefox on OS X). This would not be the case with normal content.