Closed WHITE-developer closed 2 years ago
I hit this today, too.
Thanks for covering this off @brandonkelly
Will have a look and see if anything can be improved our end, we use the field macro without an input to cp keep styling consistent.
@samhibberd What exactly is the point of rendering a field without an input?
@brandonkelly by the looks of it we are using it as a heading to group multiple fields, and take advantage of the instructions and error params. All with a view to keep styling consistent.
No doubt there will be a better way to achieve this.
Yeah… semantically a <label>
is not a heading, which is a problem for screen readers, so it would be a good idea to fix that regardless. I’m not sure when the next Craft release is going to go out, so it’s probably a good idea to just fix this on Link It’s end.
@samhibberd any hot fixes for this?
@samhibberd @siebird From what I've been able to test, running Craft 3.7.24+ (tested individually at 3.7.24, .25, .26) the errors are no longer present, and I'm able to edit fields as expected.
Craft covered for this in 3.7.25, although we will address the label / heading stuff to help with screen readers, as mentioned by Brandon, in our next release (currently being tested).
After upgrading to Craft 3.7.24 Linkit is broken when creating a new linkit/editing matrix that contains a linkit. Maybe more Craft bug as the method it fails on is there since 3.7.24.
Stacktrace: