- From: Marcos Caceres <notifications@github.com>
- Date: Fri, 05 Jun 2015 19:26:07 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/9/109503588@github.com>
> The background-color fields in image is interesting but I'm not sure that's what we want here. Maybe we should have background-color on splashscreen? The idea was really about knowing the background colour of the content that would be printed after the generated splash screen. I need the background color for both the splash screen and for the icons. However, I think I made a mistake having `background_color` be on the image object. It makes processing non-trivial for me in the gecko implementation. For tiles, this is what I'm doing to determine what image to use: 1. Create an HTML image element in Gecko's parent process. 1. convert the list images from `icons` to string of "srcset"s . 1. set image.srcset = converted list of icons. In the above, I lose the background color :( That is, I know which `img.currentSrc` is used, but I can't then go back reliably to find which background color was associated with an image object (there could be two sources that use the same background-color). Would anyone object to removing background color from image object and moving it to it's own members: ```` "icons_background_color": "papayawhip", "splashcreen_background_color": "blue" ``` PS: I hate JSON. It's an inflexible pile of crap. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/9#issuecomment-109503588
Received on Saturday, 6 June 2015 02:26:35 UTC