- From: Marcos Caceres <notifications@github.com>
- Date: Sun, 21 Jun 2015 22:03:57 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/72/114007504@github.com>
> We haven't really eff'ed up until this reaches CR status... I don't think either Mozilla or Google would be willing to change their implementation (I'm not willing to change my Gecko implementation, at least). Technically, we are at CR in all but spec background-image (because we can't update the spec live if we move it to CR, so we are not interested in moving the spec to CR until the W3C addresses that flaw in the process) + we've started adding new features. However, core set of members has been stable for a long time. > I'm saying that vendors could support both for a short period (perhaps with a deprecation notice), giving users time to switch over. I don't think it's worth pain, tbh. > Lastly, I'd be happy to update all the documentation & articles for you. I'm not sure how much I can do for the various implementations, but for the ones that are open-source - I can probably help with those too. That's very kind of you to offer, but no. This is really not something I'm willing to change at this point - even with help. It's not worth the pain. If you want to help, it would great if you could read over the spec and let me know if anything is not clear. We haven't had anyone give it a good read in a while and that would be really helpful. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/72#issuecomment-114007504
Received on Monday, 22 June 2015 05:04:28 UTC