View Issue Details

IDProjectCategoryView StatusLast Update
0022298mantisbtwebpagepublic2017-03-12 06:12
ReporterTicketSolver Assigned Toatrol  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionno change required 
OSWindows 7 
Product Version2.1.0 
Summary0022298: Mantis pages are not displayed correct in Firefox and Chrome
Description

As you can see in the attached screenshots, Mantis is not well displayed in Firefox (V. 51.0.1, 32Bit). Same problem occurs in Chrome. In Internet Explorer everything seems to be correct.

In Firefox I get the following error message displayed in the console:
"Keine der "sha256"-Hashes im "integrity"-Attribut stimmen mit dem Inhalt der Subressource überein."

TagsNo tags attached.
Attached Files
Overview_page.JPG (168,476 bytes)   
Overview_page.JPG (168,476 bytes)   
view_tickets_page.JPG (127,207 bytes)   
view_tickets_page.JPG (127,207 bytes)   

Activities

atrol

atrol

2017-02-01 09:40

developer   ~0055438

I was not able to reproduce the issue.

Does clearing your browser cache fix the issue?

TicketSolver

TicketSolver

2017-02-01 09:57

reporter   ~0055439

No this does not help. Even a restart of the computer doesn't solve the problem.

I suppose that the wrong visualisation is because of some scripts being blocked because the sha256-Hash within the integrity attribute does not match with the subressources.
Thats also the error message I get within the console in Firefox.

As far as I know there were a new feature in Firefox and Chrome released which should make sure that all scripts correspond to the original script before being executed.
Because the hash checksum (within the inegrity attribute) does not match with the subressources some scripts aren't executed. This results in a wrong page visualisation.

atrol

atrol

2017-02-21 04:51

developer   ~0055730

Maybe this is also your issue 0022328:0055550

atrol

atrol

2017-03-02 17:43

developer   ~0055878

TicketSolver,

You did not provide any feedback whether 0022328:0055550 is also your issue ; I am therefore resolving this issue as "no change required".

Feel free to reopen the issue at a later time and provide the requested information.