- 🇺🇸United States smustgrave
Since there hasn't been a follow up to #14 going to close for now.
If still an issue please reopen updating issue summary with more detail per 14
Thanks!
Discovered that the unit tests checking the attribute system have conflicting behaviors based on whether the attribute is handled as an array (most importantly CSS Classes), Boolean or not.
Boolean attributes behave as they should.
If the Attribute is an array then it is not to be in the rendered attribute if empty.
All other attributes are required by the test to return attribute="" when empty.
This issue thread is for discussing the ramifications of correcting this bug. For the moment the parent ticket I'm working on will implement the behavior expected in the tests. At a minimum this behavior needs to be documented.
Closed: outdated
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since there hasn't been a follow up to #14 going to close for now.
If still an issue please reopen updating issue summary with more detail per 14
Thanks!