If hc-file-explorer is in a hc-form-field and you set the [tight] property on the file explorer initially, it won't have an effect. If you set it dynamically (after load) as in the example on the Cashmere site, it works fine. The issue is that hc-form-field, which file-explorer extends, has a parent tight property that overrides the init value on file-explorer.
So the workaround is to set tight on the form-field instead, but it's a confusing bug.
If
hc-file-explorer
is in ahc-form-field
and you set the[tight]
property on the file explorer initially, it won't have an effect. If you set it dynamically (after load) as in the example on the Cashmere site, it works fine. The issue is that hc-form-field, which file-explorer extends, has a parenttight
property that overrides the init value on file-explorer.So the workaround is to set tight on the form-field instead, but it's a confusing bug.