Thanks for the feedback!
>Icons should be used to help clarify things, but most of the icons seem to be just arrows pointing right on links. You can probably omit them!
I discussed my opinion on icons in the article, and I stand by it in this case.
> the source tree, I had no idea I could click on the file names until I hovered over them by chance. Blue text alongside black text is a very strong signal that the blue text is a link and the black text is not. (Also note that in the file path at the top, the ancestor directories are blue and clickable while the current directory is black and not). Here is where an icon would be useful: to disambiguate between directories and files.
Good point. I don't want to add an icon, but I should make filenames underlined or something like that.
>for whatever reason, keyboard navigation doesn't work for me in Firefox.
That's bizarre, it works fine for me. Can anyone else reproduce this?
>Icons should be used to help clarify things, but most of the icons seem to be just arrows pointing right on links. You can probably omit them!
I discussed my opinion on icons in the article, and I stand by it in this case.
> the source tree, I had no idea I could click on the file names until I hovered over them by chance. Blue text alongside black text is a very strong signal that the blue text is a link and the black text is not. (Also note that in the file path at the top, the ancestor directories are blue and clickable while the current directory is black and not). Here is where an icon would be useful: to disambiguate between directories and files.
Good point. I don't want to add an icon, but I should make filenames underlined or something like that.
>for whatever reason, keyboard navigation doesn't work for me in Firefox.
That's bizarre, it works fine for me. Can anyone else reproduce this?