Closed HalvorHaugan closed 1 week ago
Latest commit: 9ff0bf003e0640b5dc87e2fd2f133009d5bd9b46
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
0d58f9f20 | 91 komponenter | 138 stories
Seems to work. But this is reverting some changes done recently, isn't it? Do we now break something those changes fixed?
And is it possible to write a test that catches this problem? I've been thinking about adding a test case with more content exactly for these types of issues, so maybe this is the time for it?
@it-vegard Yes, it reverts this: https://github.com/navikt/aksel/pull/3299 But setting scroll-margin-top
to 48px instead of 50px seems to be a better fix for that issue than changing scrollIntoView.
@it-vegard I will investigate if it's possible to catch it in a test. I think it should be possible in a Storybook interaction test, but I'm having doubts about vitest. But maybe Storybook is sufficient if we manage to run those tests in CI 🤔
Component Checklist 📝
@navikt/core/css/config/_mappings.js
)@navikt/core/css/tokens.json
)@navikt/aksel-stylelint/src/deprecations.ts
)@navikt/core/react/src/index.ts
and@navikt/core/react/package.json
)@navikt/core/css/index.css
)<Component>: <gitmoji?> <Text>.
E.g. "Button: :sparkles: Add feature xyz.")