feat: header improvements #3007
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#3007
Loading…
Reference in New Issue
No description provided.
Delete Branch "dpschen/frontend:feature/header-improvements"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Based on
feature/feat-sw-and-header-improvements
@ -26,0 +14,4 @@
v-if="currentList.id"
class="list-title-wrapper"
>
<div class="list-title">{{ currentList.title === '' ? $t('misc.loading') : getListTitle(currentList) }}</div>
Isn't
<h1>
supposed to only contain text?I never heard that. Where do you take that info from? My idea here was that if a user jumps the page structure he'll automatically find headline text and the related buttons together. I could also switch the
div
(wrapping the txt) and theh1
.Not sure where exactly that comes from, might as well be wrong. It just "feels" wrong to put a lot of other stuff in a headline element.
I think semantically it'd be cleaner to switch the
div
andh1
.I was able to find this: https://www.quora.com/Is-the-usage-of-DIV-within-an-H1-tag-bad-for-SEO-If-yes-why
But it's about SEO which is not relevant here.
CSS-Tricks has another little one here: https://css-tricks.com/can-include-a-certain-html-element-within-another-certain-html-element/
Yeah, fuck SEO :D
I replaced it because of semantics. That I agree more with.
In reality I guess no browsers nowadays really has an issue with the
h1
being a wrapper.The caniinclude site also doesn't seem to be up-to-date.
E.g. https://caninclude.glitch.me/caninclude?child=h1&parent=a
While not without problems, it got really common to wrap stuff with a link for example for block links.
AFAIK most browsers support this.
Hi dpschen!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3007-feature-header-improvements--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
01e52b956c
to5ebf77fce1
Looks like the list title is not centered anymore:
5ebf77fce1
to6508ce1ccd
Fixed
Looks good
Looks like the tests need adjustments as their selectors changed.
6508ce1ccd
toeb4d8aad6b
I don't understand why this doesn't run through. For me the tests succeed locally.
Do you have an idea?
The test looks for a
.list-title h1
but the element is now ah1.list-title
.eb4d8aad6b
to19709978b3
19709978b3
toe8db2c2b45
Okay, was some local caching issue with cypress…