Rendering issue in the message list page

[ntmlod]

No problem on the Forum & Topic list pages but in the message list view the banner is overriding by the main navigation bar and the remaining content of the page.
In the HTML code of the page, a style script line seems to be missing in the head block by comparison with other page.

<style type="text/css">
    @media screen { #mainnav, #ctxtnav, #pagepath {top: 98px;}#content, #notice, #warning, #altlinks, #altlinks, #footer {top: 148px;} }
</style>

When I add it online, I recover a good rendering.

[Ryan J Ollos]

Replying to ntmlod:

No problem on the Forum & Topic list pages but in the message list view the banner is overriding by the main navigation bar and the remaining content of the page.

I guess we need to add common/css/wiki.css to that page. What's the path for the message list view? I haven't worked on the plugin in some time so I'm not familiar with all the views.

[anonymous]

The path is something like this ${Project_URL}/discussion/topic/${Topic_number}

[Ryan J Ollos]

I can't reproduce. wiki.css is included on pages with the path /discussion/topic/<id>. Are you running the latest version of the plugin? If yes, could you post a screen capture of the issue?

[ntmlod]

Yes , I confirm last revision for Discussion plugin (15151) and also Menus plugin (12147).

[ntmlod]

Sorry my mistake, I've got 2 branches in my source directory for this plugin (0.11 and 1.0) because it crashed with 1.0 with an internal error. I will create a separated ticket for that.

So the rendering issue is under the last revision of 0.11 branch (15097).

[Ryan J Ollos]

Thanks for the additional information. The 0.11 branch is no longer supported, but I'll fix #12762.

[ntmlod]

Sorry, I probably led us in the wrong way.
This bug seems to be a side effect of using simultaneously NavigationDisplayPlugin (trunk) for fixing the main menu. With a clean standalone installation, I was able to reproduce it precisely on the topic page messages view (message-list.html template).

It is probably related to CSS file fixed_menu.css included but I don't figure out why it occurs only with this particular page.