Putting v-can on a button component causes the disabled attribute to be lost

I have a component like this:

<template>
    <button
        class="inline-block font-bold py-2 px-4 rounded text-xs bg-gray-200 text-600"
        :type="type"><slot>Save</slot></button>
</template>

If I import it into another component as SecondarySaveButton, then putting a v-can directive on it oddly causes the disabled attribute to be lost:

<secondary-save-button
    v-can:tag-suggestions
    name="save_tag"
    :disabled="!canSubmitSuggestion">Add and tag</secondary-save-button>

If I wrap the component with a v-can statement, the disabled attribute is rendered as expected:

<span v-can:tag-suggestions>
    <secondary-save-button
        name="save_tag"
        :disabled="!canSubmitSuggestion">Add and tag</secondary-save-button>
</span>

[thomaslichtdotnet]

The disabled attribute is always initialized with false (index.ts line 230). After commenting this line it was working for me.

But I don’t know if this causes other side effects.

      const el_ = el as LooseHTMLElement
      // el_.disabled = false
      el_.readOnly = false`

[mblarsen]

Published version 0.15.4 with fix by @thomaslichtdotnet