In article <[EMAIL PROTECTED]>, Martin Fritsche <[EMAIL PROTECTED]> wrote: >Peter Stein wrote: > >> How do you know? I certainly have not corresponded with you. >> Are *you* on the Mozilla project team and have *you* investigated >> this problem? There is no evidence that *anyone* has taken a >> serious look at this. Don't believe me? Look up the tracking >> report for the above bug #. > >I've looked at it. >There are four entries. Two of them are wrote by you. The others saiy, >that it could not be confirmed. I also couldn't confirm it. Why should >everyone write, taht he couldn't confirm it?
You plus 2 others doesn't equal "everyone". And I've already offered a speculation cynical as it might be as to why it isn't being confirmed. Part of the problem was that nobody bothered to read the "steps to reproduce" that I originally submitted. You may have noticed that my detailed examples for this bug was the last entry. >Don't you think, that there >would be a lot more entries, when this bug would exist at more people? Not everyone who discovers a bug actually files a report. A quick scan of the newsgroup easily confirms that. And yes, there are other folks finding this bug or one similar to it. Just look for subjects like "can't enter text...", etc. >Did you update ypur libraries? Which libraries? To what version(s)? >Did you try a new profile? It was suggested I delete the profile chrome folder. Tried it. No effect. >Did you try build 0.9.9? Yes, that's what motivated my post in the first place. >It works very fine here. >When you did the steps above and the bug is still there, make a screenshot. It won't show anything new which hasn't already been covered in the bug report. >> Highly unlikely. I run lots of Linux apps. Why is only Mozilla getting >> tripped up? More to the point, why are other people reporting similar >> problems? >Who ist reporting similar bugs? At 125290 it's only you. Already covered above.
