Originally created by Kevin Richards.
If you have a form, module or page which contains the attributes width, height, x, y then they are broken in the 0.6.0 release.
An example would be a domain object for an Image with attributes url, width, height.
form.width now returns the width of the form NOT the value of the input field.
Similar problems for x,y,height exist.
I'd suggest that these shortcuts are only honoured IF there are no page/module/field attributes which match.
Originally posted by Luke Daley.
I think we should introduce an object that contains these 4 properties. So if we were to call it display.
Coming up with the right name may be tricky.
Throw an exception when a name rendering a content definition inacces…
…sible is being used.
A InvalidPageContent exception is now thrown now when a content name that conflicts with any of these properties is used.