What it decides
- Rule
SPO-MODERN-003- Applies to
sharepoint·site- Default severity
- low
- Basis
- convention
On what authority
Microsoft provides seattle.master and oslo.master, permits replacing them on sites that allow custom script, and documents the Design Manager for doing exactly that. There is no rule against it. Our position is that a replaced master page is a fact somebody should know before planning any change to the site, and an organisation with a maintained custom master page can reasonably decline this rule.
This basis carries no external source, and that is the type saying so: a convention is this product's own threshold rather than a vendor's, and attaching a page that does not state it would be worse than admitting authorship.
What it needs to decide
web.custom_master_page_file
Without these facts the rule answers unknown, which is not a pass and is not a failure: it is the rule saying the evidence could not settle the question.
Where the evidence comes from
modernity: how one site is built: template, branding, publishing · live-validated
What a pass does not establish
A site on seattle.master can be as classic as any other: classic pages, classic web parts, alternate CSS and script editor web parts all survive a default master page. This rule reads one file name.
- The comparison is on the file name rather than the path, and deliberately so. On the root site the default reads `/_catalogs/masterpage/seattle.master`, and on a subsite the same default reads `/sites/x/_catalogs/masterpage/seattle.master`. Comparing paths would report every site that is not the root.
- A file named seattle.master that somebody edited in place passes this rule. The name is not a checksum.
Source
The rule as the Engine holds it, at the revision this page was generated from: 1.0.0b6@b4bf9c325233.
Generated from capability-manifest/1.0.0 at1.0.0b6@b4bf9c325233, contract1.0.0b6. Every fact on this page is the Engine's; this site publishes it and does not maintain it.