Fixes breadcrumb wrapping and overlapping the select all box

[AllanOXDi]

Summary

This PR fixes the overlapping of the breadcrumbs
Closes #4829

Before

Screen.Recording.2025-03-27.at.21.43.45.mov

After

Screen.Recording.2025-03-27.at.21.42.04.mov

References

#4829

[akolson]

I think this would not only partially resolve the issue but would also introduce responsiveness concerns. Besides, if we really need to override the width of the component, it makes more sense do so within a wrapper instead, I think (this styling has been defined within the component itself). Better still, we can make the change in the Breadcrumbs component where I suspect the issues resides. It appears to me that the finickiness is due to the way we are handling the overflow calculations, so it will require some digging around to establish what is causing the issue.

studio/contentcuration/contentcuration/frontend/shared/views/Breadcrumbs.vue

Lines 95 to 111 in 4dc29f2

	handleOverflow() {
	const maxWidth = this.$refs.breadcrumbs.$el.offsetWidth;
	let totalWidth = 0;
	this.breadcrumbStartingIndex = 0;
	this.$nextTick(() => {
	if (this.$refs.breadcrumb) {
	for (var i = this.$refs.breadcrumb.length - 1; i >= 0; --i) {
	totalWidth += this.$refs.breadcrumb[i].$el.offsetWidth + 40;
	// Bounds exceeded, go back to previous index
	if (totalWidth >= maxWidth - 48) {
	this.breadcrumbStartingIndex = Math.min(this.items.length - 1, i + 1);
	break;
	}
	}
	}
	});

[akolson]

Hi @AllanOXDi. Left a few comments

[akolson]

Not too sure we want to commit this deleted file?

[akolson]

https://github.com/learningequality/studio/pull/4976/files#r2054022451

[akolson]

Unfortunately, this still doesn't fix the issue. If anything, it would be a partial fix--in some screen sizes it works on others it doesn't

[akolson]

Hi @AllanOXDi Could you please retarget this to unstable? (You might have to rebase your branch on unstable)

[akolson]

Changes look correct to me. I have also done some manual QA (for some time now) on the fix but haven't been able to replicate the issue again. (More manual QA required). Thanks @AllanOXDi for your persistence on this issue!