Issue 60426

Summary: ux-ctest: Insert-Footer/Header-<PageStyleNames> confuses users
Product: Writer Reporter: hans_werner67
Component: uiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: frank.loehmann, issues, nesshof, rb.henschel, thorsten.ziehm
Version: currentKeywords: oooqa, usability
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: FEATURE Latest Confirmation in: ---
Developer Difficulty: ---

Description hans_werner67 2006-01-12 09:12:25 UTC
Under some circumstances not obvious to the user, there are more Submenu items
to Insert/Footer: “Alle” (all), “Standard” (Default), “Endnote” (Endnote) etc.
which confuses users.

Recommendation: Do not list names of all page styles and always use page style
of current visible page.
Comment 1 frank.loehmann 2006-01-12 14:39:19 UTC
Keyword: ux-ctest
Comment 2 frank.loehmann 2006-03-14 16:51:38 UTC
FL: We have to simplify this feature as follows: 

1. The Insert-Footer and Insert-Header sub menu entries get removed
2. The "Header" and "Footer" menu entry gets a checkmark if set for current
(cursor position) page style.
2. The "Header" just creates a header for the page style where the cursor
currently stands in. 
3. The "Footer" just creates a header for the page style where the cursor
currently stands in.

No string changes required. General behavior i.e. query dialog on deleting will
be kept unchanged.
Comment 3 frank.loehmann 2006-03-14 16:53:55 UTC
Correction: 3. The "Footer" just creates a FOOTER for the page style where the
cursor
currently stands in.
Comment 4 lohmaier 2006-03-14 21:03:09 UTC
I doubt that this will satisfy the users.

Most users only want to toggle the header/footer for the *current* (one single)
page only, not for the page-style (=probably all pages of the document) (since
they're not used to the concept of page-styles at all).
Comment 5 frank.loehmann 2006-03-15 08:34:59 UTC
FL: Maybe, but Writer does not work like that. And think about users writing a
document longer than one page, do you think those users would be happy to turn
on the header for each single page? But surely the user does not understand the
current geeky implementation thats a fact based on usability testing. 
Comment 6 frank.loehmann 2006-03-17 09:02:37 UTC
Set target to OOo 2.0.3
Comment 7 lohmaier 2006-03-31 14:12:16 UTC
> But surely the user does not understand the current geeky implementation thats 
> a fact based on usability testing. 

So changing the name of a menu entry will make them understand the logic? Sure.

> but Writer does not work like that.

So why are you trying to make OOo look like it would work like that?
Comment 8 Regina Henschel 2006-04-01 19:39:31 UTC
Seems to be similar to issue 33543 for me.
Comment 9 frank.loehmann 2006-04-03 16:57:44 UTC
Please find the most current version of the spec. here:
http://specs.openoffice.org/writer/menus/Insert_Header_and_Footer_Entries.odt
Comment 10 frank.loehmann 2006-04-04 16:57:55 UTC
Set target to OOo 2.0.4 due to lack of resources and due to upcoming GUI freeze.
Comment 11 Regina Henschel 2006-04-04 18:54:19 UTC
I read the spec draft and think, that it doesn't solve the problem which is
basis of this issue.
The user sees "standard" and it is not clear to him that this is a page style.
So solution must be to tell him that it is a page style. Therefore don't reduce
the functionallity but change the label.
Indeed a submenu is not necessary, if only one page style is in use. But to
solve this, the proposal in issue 33543, "If the document has only one page
style, the Insert-Header and Insert-Footer menu should not contain a submenu,
but insert a header/footer for that page style directly." is better than
changing the whole behavior.
Comment 12 Oliver Specht 2006-06-06 10:37:00 UTC
Target changed to 2.x, added fl to cc
Comment 13 michael.ruess 2006-07-26 13:30:20 UTC
*** Issue 67780 has been marked as a duplicate of this issue. ***
Comment 14 Oliver Specht 2006-08-16 11:27:27 UTC
->FL: I don't like the reduction of the submenu either. 
Dropping the submenu in case of one used style is not easy to implement but
possible. If the submenu contains more than one name the user should be able to
understand that Standard/Default is a page style name.
Comment 15 Mathias_Bauer 2006-11-27 20:22:00 UTC
I think having the functionality based on styles only is not what at least
beginners don't understand. We need to have something like:

- switch on header/footer for all pages
- only for current page
- starting with current page
- only for style "xyz" (list of styles->current functionality)

Each and everything can be done today also but in some cases it needs a lot of
single steps including the creation of new page style and addition of page
breaks that IMHO could be done by Writer automatically if needed to achieve the
desired functionality.

I don't have a concrete idea how the UI should look like (dialog?) but I'm sure
that this will serve both the beginners and the experienced users that know what
a page style is.
Comment 16 frank.loehmann 2007-09-06 16:22:50 UTC
Set target to OOo 3.0.
Comment 17 frank.loehmann 2008-02-11 15:14:20 UTC
Set target to 3.x.
Comment 18 frank.loehmann 2011-02-17 16:53:34 UTC
FL->CLU: One for better defaults? I propose to take the specification as is,
because the 'Insert' menu always uses the current context/cursor position and
this menu command is not made for those users already making use of different
page styles.

Issues like 'no header on first page' or 'no header on current page' could be
addressed by a function to insert page numbering and by a dialog, if a
footer/header is turned off. This dialog could ask, if the header/footer should
be deleted on the current page only. Today the user is only asked, if the header
is not empty.

Spec. http://specs.openoffice.org/writer/menus/Insert_Header_and_Footer_Entries.odt
Comment 19 thorsten.ziehm 2011-03-07 15:26:57 UTC
Changed to priority 3. This isn't a stopper for a release.
(Issues with p1/p2 with keyword 'accessibility' and/or 'usability' are one category for stoppers. See http://wiki.services.openoffice.org/wiki/OOoRelease34#Release_relevant_issues)