(In reply to Benjamin Smedberg [:bsmedberg] from comment #42)
> Bug 838763 now covers disabling both the print and print-preview buttons for
> fullpage plugins. For in-content plugins I don't think we care about
> printing at this point.
Why ever not? This is pretty basic stuff, and other browse
I was not aware that this was idealogical issue. I thought it was
purely technical!
If that is the case then it seems like the idealogical battle has been
already lost, as Firefox is now the only browser that contains this
broken UI.
I can guarantee that if we are waiting for all plugin makers (
My understanding of the problem (and I'm sure someone will correct me if
I'm wrong) is that currently Firefox loads the plugin in a separate
process and therefore has *no control* over how it handles keyboard
events.
In other words, when a plugin has the focus, the chain of events is as
follows:
Adding my voice - this is something that bugs the crap out of me! So
much time is wasted editing long URLs (Bugzilla URLs being a
particularly common example) just to get to the home-page!! Easier to
type the whole damn thing by hand!
--
You received this bug notification because you are a memb
(In reply to Piyush Soni from comment #557)
> On the other hand, if HTML5 becomes really popular, it might replace Flash
> altogether, removing the need of fixing this bug...
Whilst the focus of this bug is on Flash, due to it's current ubiquity,
the bug affects all plugins. Therefore, even if Fl
