🦋 Changeset detected

Latest commit: 536317d

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

Preview deployments for this pull request:

storybook - 27. Jan 2026 - 13:16

With the removal of autoprefixer, do we still need browserlist declaration in the package.json?

The more I think about removal of autoprefixer. It might be wise to also document that we expect people to add parsers for targeting browsers in their own build step.

This is potentially also a breaking change downstream for people have users with older browsers, so we need to be very clear about this change.

With the removal of autoprefixer, do we still need browserlist declaration in the package.json?

The more I think about removal of autoprefixer. It might be wise to also document that we expect people to add parsers for targeting browsers in their own build step.

This is potentially also a breaking change downstream for people have users with older browsers, so we need to be very clear about this change.

I agree, but, I also think we should be smart about this;
most people these days have some kind of build step, unless they consume directly from CDN.
Most build stepes automatically do have some sort of processing, so people might have it already too. And what kind of browsers should we support? Maybe, just thinking out loud; we should not remove the autoprefixer, but ensure the things we prefix is actually what we think we need? This job should be done once, by us, not by many? :) Maybe we should have a quick huddle before merging this

I think the only things we use that perhaps should have prefix fallback are mask (several places) and box-decoration-break: clone; (skeleton.css). Don't forget our hard cutoff for support is @layer anyway which is newer than most vendor prefixes. edit: apparently we only set @layer in index.css and not individual component css-files. (Theme file also uses @layer though

seems like "cover 90% in NO", could be the offender, even though it doesnt make sense to me. Perhaps somehting is wrong in the browserlist database. But if i remove the line most of the vendor prefixes goes away

@oddvernes Very much agree! @layer and sever other techniques adds a hard limit anyway. Mask can be prefixed, to fix the ensure 6% more support, and box-decoration-break indeed. Can we make autoprefixer only fix these two? :D

Trying with adding back autoprefixer and removing "cover 90% in NO". This leaves us with 54 mostly relevant -webkit- prefixes and 44 mostly irrelevant outdated -moz- prefixes, I have not been able to get rid of those.

Some of the additional useful -webkit prefixes: -webkit-print-color-adjust and -webkit-user-select