89204 2012-06-15 06:44:25 -0700 [chromium] Normalize scale-related names 2012-06-20 11:14:57 -0700 1 1 1 Unclassified WebKit WebKit Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 86882 89212 1 vollick vollick danakj enne jamesr nduca shawnsingh oldest_to_newest 650124 0 vollick 2012-06-15 06:44:25 -0700 We have members that exist in many different spaces, and their names are often confusing. Things will become even more confusing as the device scale factor is applied. We need to agree on names for these spaces, identify which member is in which space, and rename the members so it is clear at a glance which space they belong to. Where possible, conforming to this document would be a good idea http://trac.webkit.org/wiki/ScalesAndZooms. Please comment if you have suggestions for names, or names that definitely need changing. 650158 1 danakj 2012-06-15 07:26:56 -0700 This largely depends on what device scale approach we use. Assuming we scale in LRC and keep the rest in CSS pixels.. - Surface "contentRect" is actually "surfaceRect" (analogous to layer-space) - Framebuffer space was introduced to say physical pixels before viewport/window transforms, but is no longer physical pixels after the change, and just becomes screenSpace again. - We could rename layer/surface space to layout space possibly. 650505 2 jamesr 2012-06-15 14:23:10 -0700 (In reply to comment #1) > This largely depends on what device scale approach we use. Assuming we scale in LRC and keep the rest in CSS pixels.. nit: I think we want to keep the rest in logical pixels (not CSS pixels) - i.e. page zoom is already baked in to the values we get on GraphicsLayers, etc. > - Surface "contentRect" is actually "surfaceRect" (analogous to layer-space) > - Framebuffer space was introduced to say physical pixels before viewport/window transforms, but is no longer physical pixels after the change, and just becomes screenSpace again. > - We could rename layer/surface space to layout space possibly. 653669 3 vollick 2012-06-20 11:14:57 -0700 It seems that there is no longer as urgent a need for renaming given 86882. contentBounds, means the bounds of the texture the layer (or render surface) manages. For example, for an image, it's the dimensions of the image, and for a render surface, it's the dimensions of the texture backing the surface. I am going to close this for now.