Sorry, I don't understand what you mean

You will need to provide some more information for this.

Do you mean by 'own mantis database' that you are trying to view issue 16 at bugs.mantisbt.org ?

OK, "own" means my database, I administrate and I put in some issues. One of them, the No.16 behaves somewhat strangely, as described above. Please have a look at the attached file - it shows the issue no.16

In the meantime I found out, that the problem is an added note, which contains xml-code as content. The content was copied from an configuration file, to show a solution for the specified feature. I'll add the pronblematic content as zip-file to this issue.

Maybe I can now encircle the problem a little bit more, because I added another note, which had the same problem - It seems to be the html code of "PRE" (guess the surrounding paranthesis) or test with them...

Thanks brody - i'll try to take a look at this if i get a chance (and no one else gets to it first)

Paul

Is this still an issue in 0.19.1?

@jlatour: Yes, indeed. Its an ongoing issue!

Could you tell us what was in the PRE tags?

Or... could you try a note on this issue that causes the symptoms?

@DGtlRift: look into the attached archive (content.zip), this contains the (partial) content, which makes the problems.
Its part of a configuration file, which is xml code

Hi there, I got another hint by having the same problem again on another issue in my own database - it seems, that the PRE-tag itself is the problem.
To check it, I will add a new issue here - I will name "PRE tag in a note problem"

0005118 has not the wanted result - maybe its something, which converts tags and the converted result confuses the browser, so it shows the dialog "the document contains no data"

In my installation I get the problem only, when

pre

Just to add to this - I have version 19.2 running, and have a problem when a pre tag is inside a bug note.

It fails to complete the page, thus alot of notes are not visible.

Take out the pre tag, and everything is fine. Would really like this one looked at if the Dev group have some time. =)

Note: 18.3 didn't have this problem (at least for me anyway)

I'm unable to reproduce this issue with the current CVS version.

@grangeway: thanks for the reminder.

Have to test it ... here:
will set a PRE tag inside this note after this line, put something in, and add an additional note afterthat. all notes have to be shown and no error from the browser

this is (pre) formatted text

and now for something different...

...well the next note about the pre tag problem...

The problem seems to be fixed. Thanks.
Hope, when installing the 1.0 release on my production issue database, the problem has gone, too.

 actual version (here): 1.0.0a2

Fixed as a side effect of some other changes in 1.0.0a2