search

INSPIRE-MIF / helpdesk-validator

Community discussion forum for INSPIRE validation issues
41 stars 22 forks source link

Blue header and footer too wide and fixed in results page, information window too narrow (2024.0.1) #1042

Closed dhdeangelis closed 1 month ago

dhdeangelis commented 3 months ago

With v. 2024.0.1, in both the public instance and a local docker instance, the results of a test are shown within a very narrow central window whereas the blue background header and footer are far too wide and fixed in place (see below). This happens at least in Firefox (123.0) and Chromium (120.0.6099.224) in Linux.

It is still possible to export the test results to html and look at the result without blue header and footer in any of those browsers. This is therefore possibly a minor annoyance and not a serious bug.

From the validator:

image

As a free html:

image

fabiovinci commented 3 months ago

Dear @dhdeangelis,

thank you for the notification, we will fix it in the next release.

fabiovinci commented 1 month ago

Dear @dhdeangelis ,

the solution is available in staging, I tested it and it works fine. Can you check it too, please?

dhdeangelis commented 1 month ago

Thank you @fabiovinci, that's good news. However, I could see if it works because I get the red error box whenever I want to proceed. image

jenriquesoriano commented 1 month ago

Dear @dhdeangelis , we cannot reproduce the issue you are facing in the Staging environment. Could you please detail it? Thank you in advance. Best,

fabiovinci commented 1 month ago

Dear @dhdeangelis,

thank you for the check, in the meantime, we will include the fix in the next release.

dhdeangelis commented 1 month ago

we cannot reproduce the issue you are facing in the Staging environment. Could you please detail it?

@jenriquesoriano I guess it had to do with some network setting, both Firefox and Chromium had warned of "unsafe" connection. Then, upon giving the link to a metadata post for example the red box appeared.

thank you for the check, in the meantime, we will include the fix in the next release.

@fabiovinci that's wise, I guess the problem in testeing had to do with network configuration, etc as answered above.

Thank you all and good luck with the new release.

dhdeangelis commented 1 month ago

I can now confirm this issue is not present in the docker version of 2024.1