- From: Brian Manthos <brianman@microsoft.com>
- Date: Wed, 22 Feb 2012 00:11:22 +0000
- To: "L. David Baron" <dbaron@dbaron.org>, "www-style@w3.org" <www-style@w3.org>
Hi David. My understanding is as follows: -1- technically "repeat repeat" should be computed to "repeat repeat" and then be inherited as such -2- all interrogation of the internal state follows the rules of OM minimization, and thus all you can ever obtain is "repeat" As such, you can't actually "see" -1- directly to provide / disprove that the OM is storing it as such. -Brian -----Original Message----- From: L. David Baron [mailto:dbaron@dbaron.org] Sent: Tuesday, February 21, 2012 2:54 PM To: www-style@w3.org Subject: [css3-background] computed value of 'background-repeat' http://dev.w3.org/csswg/css3-background/#the-background-repeat lists the Computed Value of background-repeat as "as specified". Since the Computed Value line describes the information that the implementation must retain (or not) in the computed value (which is then inherited), this seems to imply that implementations must retain the distinction between "repeat" and "repeat repeat" while inheriting. This seems wrong; I don't think that distinction should be retained in the conceptual computed value. (However, when serializing, since implementations should prefer serializing a computed value to its longer-established form [1], both should get serialized as "repeat".) At least, based on my understanding of what the "Computed Value" line means, I think this should change. But I'm not sure how well my understanding is reflected in the relevant specifications. -David [1] In my opinion, this rule is more important than serializing to the shortest form. In this case, both lead to the same result. -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla http://www.mozilla.org/ 𝄂
Received on Wednesday, 22 February 2012 00:12:03 UTC