17057 2012-05-15 09:01:47 +0000 '"2x" means "maximum pixel density of 2 device pixels per CSS pixel"' the algorithm actually treats this as a minimum so this note should be reworded. 2012-09-15 21:05:28 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#the-img-element P3 normal Unsorted 1 contributor ian ian mike odinho contributor oldest_to_newest 67709 0 contributor 2012-05-15 09:01:47 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-1.html Multipage: http://www.whatwg.org/C#the-img-element Complete: http://www.whatwg.org/c#the-img-element Comment: '"2x" means "maximum pixel density of 2 device pixels per CSS pixel"' the algorithm actually treats this as a minimum so this note should be reworded. Posted from: 82.161.179.17 by annevk@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.4; U; en) Presto/2.10.229 Version/11.64 67783 1 odinho 2012-05-16 12:51:09 +0000 This also affects the steps taking away entries from the candidates based on width and height. Spec currently says: > If there are any entries in candidates that have an associated width > that is greater than max width, then remove them, unless that would > remove all the entries, in which case remove only the entries whose > associated width is greater than the smallest such width. I believe it should say: > If there are any entries in candidates that have an associated width > that is equal to or less than max width, then remove them, unless that would > remove all the entries, in which case remove only the entries whose > associated width is greater than the smallest such width. And equally for height. 70809 2 contributor 2012-07-18 17:31:55 +0000 This bug was cloned to create bug 18171 as part of operation convergence. 73967 3 ian 2012-09-15 21:05:28 +0000 Can you check the spec again and see if it's ok now? I tweaked this part a few weeks ago and I think it's working as intended now.