You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a table on our app (OCM) with an actions column. One of the actions is an external link. When we implemented this with the usual Dropdown kebab toggle (before we heard of the actions column), this worked well - a Dropdown item is an <a> by default, so we can just specify an href, and it works well.
Now we want to use the actions column feature of the Table component.
The ActionColumn allows me to specify a list of actions. The IAction interface is defined as a superset of the DropdownItem props.
This means that it should, in theory, accept an href, and it does indeed render this correctly. However, the onSelect event handler in the ActionsColumn calls event.preventDefault();, which disable's the browser default link behavior, making the link non functional.
Since the default onSelect event handler is always called we have no way to work around this behavior, making this a blocking bug for us.
The text was updated successfully, but these errors were encountered:
We have a table on our app (OCM) with an actions column. One of the actions is an external link. When we implemented this with the usual Dropdown kebab toggle (before we heard of the actions column), this worked well - a Dropdown item is an
<a>
by default, so we can just specify anhref
, and it works well.Now we want to use the actions column feature of the Table component.
The ActionColumn allows me to specify a list of actions. The IAction interface is defined as a superset of the DropdownItem props.
This means that it should, in theory, accept an
href
, and it does indeed render this correctly. However, the onSelect event handler in the ActionsColumn callsevent.preventDefault();
, which disable's the browser default link behavior, making the link non functional.Since the default
onSelect
event handler is always called we have no way to work around this behavior, making this a blocking bug for us.The text was updated successfully, but these errors were encountered: