Page MenuHomeSoftware Heritage

UI: wrong usage of the "go to origin" icon next to the origin URL that redirect to SWH
Closed, MigratedEdits Locked

Description

In a view like a revision, the upper part of the content looks like:

But there several UI caveats there:

  • the displayed URL is NOT what the href point to,
  • the "go to origin" icon is misused: it generally means the link next to it (here the URL that href to somewhere else) is a link to an external resource.

I believe this part of the table is unintuitive and against user's perception of the expected behavior of such snip of web page.

Event Timeline

douardda triaged this task as Normal priority.Nov 17 2020, 11:11 AM
douardda created this task.

What do you suggest here ? Removing the href to the displayed URL ?

I found it confusing initially too; but didn't report it because I don't have a better solution

That link is not really needed anymore as we can get back to the root directory of the master branch by clicking on the snapshot date link.

So I propose to remove the link while keeping the displayed origin URL. But I think we should keep the "go to origin" icon as we do not
want to have a huge link to the origin URL.

We need to think about a better UI for this, but I have no solution for now.

For the record, we have the same issue in the "Save code now" requests table.
Originally, the link to the archived origin was available from the "Status" column but I was asked to change it as it was not prominente enough.

So I propose to remove the link while keeping the displayed origin URL. But I think we should keep the "go to origin" icon as we do not
want to have a huge link to the origin URL.

Thinking it back, simply pointing the href to the origin URL and removing the icon seems the right choice here.

Another point I forgot to mention here: the origin URL link at the top of the origin context views enable to quickly get back to the HEAD branch root directory for the last visit performed by SWH on the origin.

Such a link should remain present in the origin context views so this clearly calls for UI improvements regarding what is displayed above the tabs.