I've used CSS in the past extensively to remove the .activity-navigation bar from the bottom of certain activities, especially ones that have their own navigation built-in (i.e. Lesson, Quiz). Usually this is no problem, but with Questionnaire, it is problematic.
It appears that Questionnaire uses two pages primarily (from a student standpoint) - "view" and "complete". The body IDs are "page-mod-questionnaire-view" and "page-mod-questionnaire-complete", respectively.
The problem is that both of these pages are used in multiple states of questionnaire completion, some of which need to have the activity-navigation bar apparent, and others where we would like it not to.
In essence, I cannot find a CSS-inherent way to target these different states. I tried to look at the massive wealth of code that is the Questionnaire module, to see if I could add body classes appropriately, but I've come up short.
Does anyone know how I can best accomplish this? The bottom line, is that when a student is in a multi-page questionnaire, they essentially have two sets of nav buttons - Questionnaire provides Next and Previous pages, but just below that are the Activity Navigation, which would essentially take the student out of the Questionnaire by clicking on them. Not only is it confusing for the student, it doesn't make much sense to have them there while within a Questionnaire.
Can't figure out why this problem has never been raised before?...
Thanks for any help.
(We have hidden the "Continue" button as well, as you can see, because the users hated being taken back into their finished questionnaire when they assumed that "continue" meant "continue to the next topic".
This is why your solution doesn't work for us, and why I mentioned the view and complete pages have different "states". If I have those different states write CSS selectors to the page, then it would be trivial to target them appropriately. As it is now, the CSS display:none; works all-or-nothing.
