Support for splashscreens member (W3C) #45
Comments
Thanks for sharing this! I added it to the backlog to keep it in radar. |
Marcos, |
Hold for a bit, I haven't gotten a straight answer out of the Google guys if they are going to support it or not (need to also check with Microsoft). |
Double check with Alex lu, but from the MS side it seems to make sense for us. |
@boyofgreen great to hear. Will ping Alex also. |
i think we are now ready to implement this, it is a great add |
@boyofgreen, sounds good. Please note that there are some ongoing discussions over at the w3c:
We would really appreciate ManifoldJS team's feedback. |
As far as I can tell, there isn't support for splash screens in either Firefox or Chrome apps at the moment. So, for the time being, this applies only to the Cordova-based apps generated by ManifoldJS and should be implemented in the ManifoldCordova plugin (cordova-plugin-hostedwebapp). I've created a new issue in the plugin's repository to track this (pwa-builder/ManifoldCordova#37). |
We added support for the W3C |
Just a heads-up. It seems that Chrome have chosen not to use the splash_screen and just generate splash screens from the 'background_color' plus an appropriate square icon from 'icons' They are hiding the splash on first paint. |
Just a heads up that we've added a
splashscreens
member to the W3C Web Manifest spec. However, we are still gathering implementer feedback and we currently don't have strong commitment from any vendor to support them (i.e., please don't add them to ManifoldJS just yet! 😄).Will report back with more info soon. Design wise, they take the exact same object as
icons
(an array of image objects), so validation/transformation will be identical.The text was updated successfully, but these errors were encountered: