-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support breadcrumbs without ul/li #156
Comments
@tom-acceleratecompliance May I ask why are you using some element other than |
Hi @saadeghi - 100% recognise this might be too much of an edge case to include in the library. In our case, our breadcrumbs are automatically generated from the users requirements using custom svelte components, due to that we need the tag to be: <svelte:component this={CustomClass} class="breadcrumbs">
<svelte:component this={DifferentClass} class='breadcrumb-item'>
Item 1
</svelte>
</svelte:component> This is the same reason for the request #151 - which again I fully understand is an odd requirement, however, with the emergence of web components it may be something that becomes more common. Thanks! |
To follow on - lots of pushback in the svelte community to fix this at the svelte level, which would support:
But unfortunately still hasn't been actioned in the last year. |
@tom-acceleratecompliance Does <ul>
<svelte:component this={CustomClass}>
<svelte:component this={DifferentClass}>
<li>Item 1</li>
</svelte>
</svelte:component>
</ul> |
Ah sorry, you're 100% correct, we have some other restraints around how our visual builder works, but the combination of those 2 factors makes this well and truely a niche problem, sorry for wasting your time! |
@tom-acceleratecompliance No problem. I'd be happy to help. |
Hello, apologies for the issue spam today.
I was wondering if it's worth extending the breadcrumbs to work without requiring the ul/li elements. I can take the core styles and adapt them to work for my own project, but just wanted to float the suggestion.
Thanks!
The text was updated successfully, but these errors were encountered: