editorial: Move the definition of display-mode back to APPMANIFEST.

[mgiuca]

This text was moved out of the Manifest spec into CSS mediaqueries-5 in
w3c/csswg-drafts#6343, along with the display-mode media feature. The
actual definition of display mode belongs here, while the display-mode
media feature remains in CSS mediaqueries-5.

Closes w3c/csswg-drafts#7306.

This change (choose at least one, delete ones that don't apply):

• Makes editorial changes (changes informative sections, or changes normative sections without changing behavior)

Person merging, please make sure that commits are squashed with one of the following as a commit message prefix:

• chore:
• editorial:
• BREAKING CHANGE:
• And use none if it's a normative change

---

Preview | Diff

[aarongustafson]

LGTM

[aarongustafson]

CSS will want the export, no?

[marcoscaceres]

Approved, but let's make sure we merge them both a the same time.

[mgiuca]

Thanks for the export suggestions, @aarongustafson . I think you need to approve now that Marcos has merged it in.

Also @marcoscaceres do you know what is going on with this validation error? It doesn't appear to be a problem with the changes to the html file:

  The W3C_API_KEY input is required with VALIDATE_PUBRULES
  Error: Process completed with exit code 1.
  Error: w3c/spec-prod/v2/action.yml (Line: 83, Col: 27):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 83, Col: 27): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 93, Col: 23):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 93, Col: 23): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 113, Col: 24):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 113, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 122, Col: 33):
  Error: w3c/spec-prod/v2/action.yml (Line: 123, Col: 24):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 122, Col: 33): Error reading JToken from JsonReader. Path '', line 0, position 0.,w3c/spec-prod/v2/action.yml (Line: 123, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 132, Col: 35):
  Error: w3c/spec-prod/v2/action.yml (Line: 133, Col: 24):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 132, Col: 35): Error reading JToken from JsonReader. Path '', line 0, position 0.,w3c/spec-prod/v2/action.yml (Line: 133, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 143, Col: 33):
  Error: w3c/spec-prod/v2/action.yml (Line: 144, Col: 24):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 143, Col: 33): Error reading JToken from JsonReader. Path '', line 0, position 0.,w3c/spec-prod/v2/action.yml (Line: 144, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 153, Col: 24):
  Error: w3c/spec-prod/v2/action.yml (Line: 154, Col: 21):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 153, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.,w3c/spec-prod/v2/action.yml (Line: 154, Col: 21): Error reading JToken from JsonReader. Path '', line 0, position 0.
  Error: w3c/spec-prod/v2/action.yml (Line: 163, Col: 24):
  Error: w3c/spec-prod/v2/action.yml (Line: 164, Col: 24):
  Error: The template is not valid. w3c/spec-prod/v2/action.yml (Line: 163, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.,w3c/spec-prod/v2/action.yml (Line: 164, Col: 24): Error reading JToken from JsonReader. Path '', line 0, position 0.

[aarongustafson]

We think it's an issue at the W3C.

[marcoscaceres]

@mgiuca, I filed a bug for that error here: w3c/spec-prod#136

[ewilligers]

Testing various browsers on a Mac, when a page has no manifest, and a browser tab is shown full-screen, browser controls remain visible but the menu bar is hidden. Chrome/Edge and Firefox treat this as fullscreen for Media Query purposes. Safari treats this as browser for Media Query purposes.

[marcoscaceres]

@mgiuca, feel free to merge it?

[mgiuca]

@marcoscaceres I haven't been merging this because I remember (>1 year ago.....) I got blocking comments out of band from @frivoal that I needed to action, and put this on the backburner. I'm trying to dig it up now (hence why I did a rebase) and finish this off.

Edit: Ah yes, here's the relevant request. It's pretty vague but I'll make some changes and ping to see if they're happy.

Edit: Here's the update to the PR on the MediaQueries side. No updates on the Manifest side.

[marcoscaceres]

@mgiuca, let us know how/if/when we can proceed with merging this.

[mgiuca]

Thanks for pinging the other PR. I would like to close this out but we should land both together.

I will try to engage CSS people again... if we literally can't get in touch with them we could maybe just land this or modify it to create a parallel definition ("manifest display mode") but it is not ideal to do so.

[marcoscaceres]

@mgiuca I pinged a few more CSS folks behind the scenes to see how we get it merged. I’ll report back.

[marcoscaceres]

(Worst case, I don’t mind if we make a small mess and just merge this if we don’t hear back)

[mgiuca]

Thanks so much for following this up, @marcoscaceres . It's been a LONG time and I'm glad to have things finally set up properly.

[marcoscaceres]

No problem. Glad I could be of some help.

[dmurph]

Yes, thanks a ton Marcos 👍

[mgiuca]

@marcoscaceres is the WD version of the manifest spec supposed to update automatically? It hasn't for two weeks. From memory, it used to update automatically after about 24h but it seems stuck (it was last generated on April 10, right before this landed, but doesn't include this change).

[marcoscaceres]

Will check what happened.

[marcoscaceres]

Fixed... the publishing system was having issues.