- From: Marcos Caceres <w3c@marcosc.com>
- Date: Mon, 7 Oct 2013 15:27:06 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: public-respimg@w3.org, simonp@opera.com
On Monday, September 30, 2013 at 5:02 PM, Simon Pieters wrote: > > Reversing the order creates a problem: the algorithm can't be run during > parsing until the </picture> end tag is seen. This is bad and something > that HTML tries to avoid (<video> avoids it, but <object> has to do it > because plugins need all parameters at init time). > > Consider the following case: > > <picture> > <source ...> > <source ...> > <!-- packet boundary here, and data is a bit slow to arrive --> > > With reverse order, the browser can't start downloading any source because > there might come other <source>s that need to be checked first. > > The same thing can happen if there's a lot of fallback content in the > <picture>. > I guess this also affects src-n, as the "-n" is significant when doing the evaluation to find the src ? -- Marcos Caceres
Received on Monday, 7 October 2013 14:27:37 UTC