> On Jul 18, 2017, at 4:39 PM, Sam Ruby <[email protected]> wrote:
>
> On Tue, Jul 18, 2017 at 2:03 PM, Craig Russell <[email protected]> wrote:
>> Hi,
>>
>> Small usability question. When I select a message to work on, sometimes I
>> just want to bail.
>>
>> I don't want to delete the current message, just go back to the message
>> list so I can come back later and file the document. This is the work flow
>> in the case of public key not uploaded.
>>
>> The browser back button doesn't work. Several of the pages are the actions I
>> just took that got me here. All of the titles listed are "ASF Secretary
>> Mail". Only one goes back to where I was.
>>
>> So, two possible solutions:
>>
>> 1. Change the title of the page that processes a message: "Processing"
>> Then, the browser back drop-down will show
>> Processing
>> Processing
>> Processing
>> ASF Secretary Mail
>> Processing
>> Processing
>> Processing
>> ASF Secretary Mail
>
> Can I suggest an alternative? Make the back button work as you would
> expect it to?
>
> https://github.com/apache/whimsy/commit/9ccb0cdfe0a5a8aa40e73be80dc51c4f325a90bd
>
> Note: my experience is that these APIs tend to be finicky. I've
> lightly tested it on both Firefox on Safari, but there may be edge
> cases that need to be handled.
The project dropdown is a bit awkward. Here's what I'd like to see:
Tab into the project field. It's highlighted. Start typing the project name.
t: shows tomcat
o: shows tomcat
m: shows tomcat
e: shows tomee
backspace: shows tomcat
tab out of the field, with tomee selected
What actually happens:
Tab into the project field. Start typing the project name.
t: shows tomcat
o: shows ode
m: shows madlib
backspace: exits the icla page, back to the message list
Is the current behavior part of a dropdown definition, part of reactjs? Can it
be "fixed" easily?
>
>> 2. Add a button next to (File) that goes back to the message list: (Cancel)
>
> FWIW, the link in the top left ('ASF Secretary Mail') already takes
> you to the message list.
So it does. I had no idea that it was a link.
I've concluded that this tool is more easily read than written. I can navigate
to where the problem is; I just can't reliably write code to fix it.
I appreciate all the help fine tuning this to my standards.
Thanks,
Craig
>
>> Ez-pz
>>
>> Craig
>>
>> Craig L Russell
>> Architect
>> [email protected]
>> P.S. A good JDO? O, Gasp!
>
> - Sam Ruby
Craig L Russell
Architect
[email protected]
P.S. A good JDO? O, Gasp!
