Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-9285

> placement in wrong place

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-m6
    • Fix Version/s: 3.0.0-m6
    • Component/s: UI
    • Labels:
      None
    • Environment:
      Chrome MacOSX
    • Story Points:
      1
    • Sprint:
      Sprint 53, Sprint 54

      Description

      While demoing Tuesday, the team noticed that on Search the > sign that usually is at the end of the row on search to indicate that you can click and see more was not in the last "column" but in the second to last column.
      This does not occur on normal search and in fact seems to only occur when you have a component twice in different repositories like attached screen (dated 10/1).
      This was demoed in NPM and that is how I reproduced it - creating two npm hosted repos and publishing the same package to both and then searching on the name.

      In addition, I tangentially noticed similar behavior on the Capabilities screen right out of the box. The differences seem to be that it does not take any special circumstances to get it to break and the > is in the second column instead of the "last". See attached screen (dated 9/30).

      I was waffling whether this should be two issues or one. I conferred with Daniel Sauble who said start with one.
      Daniel suspects as I do, that the Capabilities issue (at least) is recent regression.
      I have not checked older NX3 or NX2 at this time.
      Test performed with debug off. Nothing in the log or JS console.

        Attachments

          Activity

            People

            Assignee:
            dsauble Daniel Sauble
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title