Bug 72825 - FORMATTING: make master slides hierarchy with inheritance
Summary: FORMATTING: make master slides hierarchy with inheritance
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected)
Hardware: Other All
: medium normal
Assignee: Not Assigned
Keywords: needsDevEval
Depends on:
Reported: 2013-12-18 09:50 UTC by Jerome Fenal
Modified: 2015-12-18 10:35 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Fenal 2013-12-18 09:50:14 UTC
Problem description: 

When creating templates, you usually start with a basic branding which is after declined over variations (backgrounds for instance), but should retain the main attributes, such as styles, etc.

It would really be interesting, as with styles, to have a hierarchy of slide masters, with the same workflow as styles (create new master from this master), identical, which you can change the needed attributes only.

Currently, without the ability to even copy slide masters, the workflow is to write down every single step of customisation for a master, and restart all over again for another one with only different attributes (such as style list, frame placement or just background).

With inheritance, it would enable to modify the top-most slide master, and have attributes such as fonts, colors (to adapt to a different background image for instance) et al. modified on all children, the same way it works with styles.

Steps to reproduce:
1. Go to View => Master => slide master
2. Try to create a new slide master from an existing one
3. Modify the new slide master for the only attributes needed.

Current behavior:
not possible. You cannot even copy an existing slide master. (BZ#45617 at https://bugs.freedesktop.org/show_bug.cgi?id=45617)

Expected behavior:
There should be a context sensitive entry in the Slide pane on each slide master, that enables the "Copy slide master" or better "Create new slide master from this one" which would retain inheritance.

Operating System: ALL
Version: not available in
Comment 1 Owen Genat (retired) 2014-07-18 06:24:24 UTC
(In reply to comment #0)
> It would really be interesting, as with styles, to have a hierarchy of slide
> masters, with the same workflow as styles (create new master from this
> master), identical, which you can change the needed attributes only.

This will likely require a change to the ODF specification. Currently ODF v1.2, Part 1, §10.2.4 states:

> The <draw:page> element is a container for content in a drawing or
> presentation document.
> ...
> The <draw:page> element has the following attributes: ... draw:master-page-name 19.194 ...

ODF v1.2, Part 1, §16.9 states:

> In drawing and presentation documents, the <style:master-page> element is
> used to define master pages as common backgrounds for drawing pages. Each
> drawing page is directly linked to one master page, which is specified by 
> the draw:master-page-name attribute of the drawing pages style.
> ...
> In drawings and presentations, master pages can be assigned to drawing 
> pages using a style:parent-style-name attribute.[1]
> ...
> The <style:master-page> element has the following attributes: 
> draw:style-name 19.219.27, style:display-name 19.472, style:name 
> 19.498.2, style:next-style-name 19.499.2 and style:page-layout-name 19.504.

[1] Note that the wording here may be inaccurate ("style:parent-style-name" should probably read "draw:master-page-name"). Refer https://issues.oasis-open.org/browse/OFFICE-3679

In other words <draw:page> (Draw/Impress page) can have a master page (via the draw:master-page-name attribute) but there does not appear to be any mechanism (parent attribute) by which a <style:master-page> element (master page) can have a parent of another <style:master-page> element. Doing so would also likely complicate ODF documents considerably. 

Status set to NEEDINFO until developers / OASIS expert can comment further on the feasibility of this enhancement.
Comment 2 QA Administrators 2015-02-19 04:41:57 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

Message generated on: 2015-02-18
Comment 3 QA Administrators 2015-05-06 14:22:03 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team
Comment 4 Robinson Tryon (qubit) 2015-12-18 10:35:13 UTC
Migrating Whiteboard tags to Keywords: (needsDevEval)