Re: [w3c/manifest] Web Manifest Overrides (Issue #1045)

dmurph left a comment (w3c/manifest#1045)

[conversation at TPAC 2025](https://docs.google.com/document/d/1fOjXiGUFf_krkfYaWf5drbqzY7CTxn7EcDYr5ZWjzFg/edit?tab=t.cnzoci72snh#bookmark=id.gpb2aklisri8)

* extensions  
  * each image has properties...  
  * When a browser wants to get an image that satisfies X constraints, then:  
  * the browser starts at the top \- does it suport these conditions? If it does, then use. If not, use the next one  
  * Go until it finds one with matching conditions  
  * allows you to easily stack additional conditions  
* mek@ it's very confusing when there are 6 different constrains, but you only have some icons for each  
  * if you want 512x512 monochrome, but there is only a 256x256 monochrome, what do you do? If you have a full color 512x512....  
* Christian \- we cannot introduce another scheme now.  
  * so if we do    "color\_schemes": \["dark", "light"\]  
  * if user agents don't support this, then it might pick the 'dark' one?  
  * The spec says to pick the first  
  * so spec says you would have to put the dark mode icons at the bottom.  
* Proposal:  
  * 'color schemes' property  
  * spec text around putting at end ....  
  * we know that this can be compatible with browsers / old implementations that dont' support it because browsers consider earlier icons first  
  * change does into.... image resource? or manifest?  
    * Yes \- image resource \- Diego will spec   
  * how to do theme color with color schemes?  
  * "colors": \[  
  *    { "background\_color": "darkred", theme\_color:  
  *  "darkblue", "color-scheme": \["dark"\]}  
  *     { "background\_color": "red", theme\_color: "blue" },  
  * \]  
  * “Colors” might be better than “themes”, since we’re only putting colors in there.  
  * similar format to icons  
    * global "themes" \- array with members that have the color theme, other properties \- and in this case, background color  
    * color-scheme, background\_color, theme\_color  
    * same as icons algorithm \- browser finds the first one that is bestly appropriate  
  * Sam \- this is not necessarily matching for web, this is for the platform. So \- 'material theming' \- that's not in css  
    * it should match semantics of css, maybe not the name?  
    * how do we represent things beyond just light and dark mode  
  * aside "if there is a key in here the user agent doesn't recognize, skip the entry"  
* Carlos  
  * this is implemented in Safari  
  * Chrome is implementing?  
  * unmerged patch on firefox  
    * [https://bugzilla.mozilla.org/show\_bug.cgi?id=1809958](https://bugzilla.mozilla.org/show_bug.cgi?id=1809958)   
  * marcos \- what is the monochrome solution?  
    * it would be a condition, it would fit on a condition  
* Limin  
  * can see a flicker, rending background then turning to black  
  * certain apps.... sometimes when the user selects a theme... the site needs to be able to run javascript before determining the color to render  
  * how to solve?  
    * SW register something?  
  * How do we know the color before rendering?  
  * Dan \- you can do this by using a dynamic manifest  
    * serve a different manifest based on cookies or filename  
    * you can add a query param to the manifest url, and the server can use that to change the contents?  
    * But this might be bad \- other ideas  
      * js api to save color  
* AGREEMENT EVERYONE GETS A STICKER  
  * just for icons  
  * we need a hero for proposal for the theme color / background color thing  
  * [christian.liebel@thinktecture.com](mailto:christian.liebel@thinktecture.com) wants to take a pass  
    * will work with Carlos.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1045#issuecomment-3515109837
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1045/3515109837@github.com>