1. the bug even isn't confirmed for firefox-3.5 (for firefox-3.0 only),
2. the patch (three new lines and one changed line only!) suggested in upstream bugzilla (even being a workaround) isn't even tried?
Sorry for persistence, the issue is indead very, very annoying. I'm ready to test..
To maintainers: are there any reasons for:
1. the bug even isn't confirmed for firefox-3.5 (for firefox-3.0 only),
2. the patch (three new lines and one changed line only!) suggested in upstream bugzilla (even being a workaround) isn't even tried?
Sorry for persistence, the issue is indead very, very annoying. I'm ready to test..