- From: Marcos Caceres <marcos@marcosc.com>
- Date: Sat, 28 Sep 2013 15:17:42 +0100
- To: Jatinder Mann <jmann@microsoft.com>
- Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
On Saturday, September 28, 2013 at 2:38 AM, Jatinder Mann wrote: > I don't see this as overstepping boundaries. In order to solve this performance problem, I think it makes sense to start by specifying the end to end solution in one document and making sure the Web Performance working group feels that this solution solves the problem we set out to solve. Once we feel that our solution satisfies the performance issue, we can then evangelize this feature with the HTML, CSS, and SVG working groups to get more feedback. We can also consider at that time if it makes more sense to split up Section 4.4 and 4.5 into the latest HTML, CSS, and SVG specs. It would be good to have this stated in the document. > > That being said, I feel that specifying all the different technologies impacted by this feature in one document is actually quite useful to web developers trying to understand and use this feature and browser vendors trying to implement it. Other specs have done similar things. For example, the Composting and Blending spec [1] defines blend modes and compositions for SVG, CSS, and Canvas in one spec. At the very least, this spec should point to all the different pieces. > Ok, can you please then add the HTML <picture> element to the Resource Priorities spec: http://www.w3.org/TR/html-picture-element/ Thanks!
Received on Saturday, 28 September 2013 14:17:56 UTC