Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in vulnerability details view #1356

Closed
TG1999 opened this issue Dec 5, 2023 · 19 comments
Closed

Bug in vulnerability details view #1356

TG1999 opened this issue Dec 5, 2023 · 19 comments
Assignees

Comments

@TG1999
Copy link
Contributor

TG1999 commented Dec 5, 2023

Screenshot from 2023-12-05 14-33-41

@johnmhoran
Copy link
Member

@TG1999 Can you please describe the bug?

@TG1999
Copy link
Contributor Author

TG1999 commented Dec 5, 2023

The border on the first table in the page is missing.

@johnmhoran
Copy link
Member

This -- from the public VCIO -- already has a border.

image

@TG1999
Copy link
Contributor Author

TG1999 commented Dec 5, 2023

@johnmhoran if you will check main branch, it does not have a border

@johnmhoran
Copy link
Member

So you're saying that the current public VCIO has the border but the main branch does not?

@TG1999
Copy link
Contributor Author

TG1999 commented Dec 5, 2023

Yes!

@johnmhoran
Copy link
Member

OK, noted, will add to my list of issues to tackle when I get to working on the vulnerability UI/API.

@johnmhoran
Copy link
Member

johnmhoran commented Dec 5, 2023

But I would like us to fix the dupe PURL issue and the search/lookup issue we've been discussing as well -- these are implicated in the number and characteristics of packages returned from a search in the UI/API and thus directly impact my planned consolidation in the vuln details view of the affected packages-fixed by packages tabs. Can we do that?

@TG1999
Copy link
Contributor Author

TG1999 commented Dec 5, 2023

But I would like us to fix the dupe PURL issue and the search/lookup issue we've been discussing as well -- these are implicated in the number and characteristics of packages returned from a search in the UI/API and thus directly impact my planned consolidation in the vuln details view of the affected packages-fixed by packages tabs. Can we do that?

@johnmhoran that's in progress here https://github.com/nexB/vulnerablecode/tree/package-purl-model-updates

@TG1999
Copy link
Contributor Author

TG1999 commented Dec 5, 2023

OK, noted, will add to my list of issues to tackle when I get to working on the vulnerability UI/API.

Alright, FYI this may be a deployment blocker.

@johnmhoran
Copy link
Member

@TG1999 Hmm. I just checked out main locally, without any current pull (in log last item is your Nov 27 Prepare for release v33.6.3 (#1348) commit), and the table has a border. I'll do a git pull and see how it looks.

image

@johnmhoran
Copy link
Member

In main, after a git pull, ran make run and ... there's a border. Perhaps I missed a step, e.g., after doing git pull in main and before make run?
image

@johnmhoran
Copy link
Member

@TG1999 My prior screenshots were in Chrome. But in Firefox, I can no longer see that table's border!?
image

@johnmhoran
Copy link
Member

@TG1999 In Chrome the color of the top table's borders looks lighter than the border of the table below -- maybe Firefox displays that color differently? In any event they should have the same colored border (tho not sure if that would change the display).

@johnmhoran
Copy link
Member

otoh looking in Firefox at the current hosted VCIO does show the top table's borders, fwiw.

@johnmhoran
Copy link
Member

For some reason Firefox and Chrome seem to be using different CSS. These are both from my updated local main, Firefox then Chrome -- even the indentation differs.
image
image

@johnmhoran
Copy link
Member

@TG1999 I need to update my prior comments -- in Chrome, I'd neglected to hit ctrl-F5 to refresh the CSS, and when I do, in my local instance the top table has no borders and has the same indentation/horizontal alignment as Firefox. This is the refreshed Chrome displaying the updated main locally:

image

Both Chrome and Firefox when refreshed still display the borders for the public VCIO.

The latest merge into main is my Package UI/API PR. I don't recall doing any Vulnerability UI-related work in that PR but am guessing some change I made removed the borders and changed the indent/alignment. Will dig into that now.

@johnmhoran
Copy link
Member

Looks like my CSS change for the Package details table borders gave effect to a previously-overidden prior border=0 setting for that Vulnerability details table. Creating a new branch to fix.

johnmhoran added a commit that referenced this issue Dec 5, 2023
Reference: #1356

Signed-off-by: John M. Horan <johnmhoran@gmail.com>
@johnmhoran
Copy link
Member

Fixed with #1358 and merged in December 2023. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants