Not sure if this is a temporary problem and if it would be "fixed" if I reboot the machine, but currently I have the following 100% replicable problem:
Typing a part of the recipient's name/address in any address field, I'm seeing a number of possible selections. But I can't select any of them with the mouse.
Oddly, I can mark parts of the offered selections with the mouse instead, see attached.
Selecting a recipient with the keyboard does still work, but only if I didn't click on any of the offered selections before. If I did that, even the keyboard selection doesn't work anymore.
Win7/64, FF 27.0.1, RC 1.1-git [GIT 20140605.2017].
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 06/06/2014 09:49 PM, Michael Heydekamp wrote:
Not sure if this is a temporary problem and if it would be "fixed" if I reboot the machine, but currently I have the following 100% replicable problem:
Typing a part of the recipient's name/address in any address field, I'm seeing a number of possible selections. But I can't select any of them with the mouse.
Fixed. There was recently a lot of changes in keyboard and mouse events handling. So, more regressions expected. E.g. http://trac.roundcube.net/ticket/1489932.
Am 08.06.2014 11:30, schrieb A.L.E.C:
On 06/06/2014 09:49 PM, Michael Heydekamp wrote:
Typing a part of the recipient's name/address in any address field, I'm seeing a number of possible selections. But I can't select any of them with the mouse.
Fixed. There was recently a lot of changes in keyboard and mouse events handling. So, more regressions expected. E.g. http://trac.roundcube.net/ticket/1489932.
Well, yes, thanks for the fix (confirmed, BTW). But when you're doing such kind of major changes - don't you test them before committing them...?
And why are you doing those changes at all - if everything worked well before? Code optimization?
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 06/09/2014 01:40 AM, Michael Heydekamp wrote:
Well, yes, thanks for the fix (confirmed, BTW). But when you're doing such kind of major changes - don't you test them before committing them...?
We do, however because we have no automated tests for UI....
And why are you doing those changes at all - if everything worked well before? Code optimization?
Nah, we're just checking how many of you use git-master ;)
Am 09.06.2014 12:33, schrieb A.L.E.C:
On 06/09/2014 01:40 AM, Michael Heydekamp wrote:
Well, yes, thanks for the fix (confirmed, BTW). But when you're doing such kind of major changes - don't you test them before committing them...?
We do, however because we have no automated tests for UI....
Of course not! But (why) don't you test them manually...?
And why are you doing those changes at all - if everything worked well before? Code optimization?
Nah, we're just checking how many of you use git-master ;)
Apparently I'm the only one. ;) At least the only running against such kinda bugs and reporting them - not even the devs appear to use it?
There's no better test than using the application in real and daily life.
Anyway: A serious answer (as to why these things have been changed) would still be appreciated.
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On Tue, Jun 10, 2014 at 9:22 PM, Michael Heydekamp listuser@freexp.de wrote:
Am 09.06.2014 12:33, schrieb A.L.E.C:
On 06/09/2014 01:40 AM, Michael Heydekamp wrote:
Well, yes, thanks for the fix (confirmed, BTW). But when you're doing such kind of major changes - don't you test them before committing them...?
We do, however because we have no automated tests for UI....
Of course not! But (why) don't you test them manually...?
Believe us, we do test things manually but we're all human beings with limited resources and thus we might miss some every now and then. That said, we even more appreciate feedback for early adopters like you!
And why are you doing those changes at all - if everything worked well before? Code optimization?
Apparently I'm the only one. ;) At least the only running against such kinda bugs and reporting them - not even the devs appear to use it?
There's no better test than using the application in real and daily life.
Anyway: A serious answer (as to why these things have been changed) would still be appreciated.
You might have followed the posts on the dev mailing list and saw that we're currently improving the UI for users with disabilities using assistive technologies. The major changes happened in the larry skin and the core. Some required adaptions to the classic skin haven't yet been made because they might still be object for changes.
Sorry for not explaining all of our commits, considerations and thoughts here in detail but that'd be a luxury service nobody actually can afford...
~Thomas
-
A.L.E.C -
Michael Heydekamp -
Thomas Bruederli