We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
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.
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
Coming up with the right name may be tricky.
A InvalidPageContent exception is now thrown now when a content name that conflicts with any of these properties is used.
No branches or pull requests