feat(preset-mini)!: remove default border-styles on border-x utility

[chu121su12]

Aligns with tailwind; close #1967.

Reference: https://tailwindcss.com/docs/border-width

[netlify]

✅ Deploy Preview for unocss ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	e3f65c4
🔍 Latest deploy log	https://app.netlify.com/sites/unocss/deploys/638ef71f83476f0008b531a2
😎 Deploy Preview	https://deploy-preview-1971--unocss.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[zyyv]

Hi, I'd prefer to keep it as it is and make it more flexible isn't it?

:( Too bad my projects are all using b to have a border and now I have to add b-solid for it. 😭

[sibbng]

Hi, I'd prefer to keep it as it is and make it more flexible isn't it?

:( Too bad my projects are all using b to have a border and now I have to add b-solid for it. 😭

No, you don't need to. solid is the default.

[chu121su12]

I'd argue without the set style is more flexible.

As for the default, solid style is set in both

unocss/packages/reset/tailwind.css

Lines 6 to 11 in cdb4d40

	*,
	::before,
	::after {
	box-sizing: border-box; /* 1 */
	border-width: 0; /* 2 */
	border-style: solid; /* 2 */

and

unocss/packages/reset/antfu.css

Lines 1 to 4 in cdb4d40

	*, ::before, ::after {
	box-sizing: border-box;
	border-width: 0;
	border-style: solid;

[ghost]

Even if adding CSS resets is a solution, there are use cases where one doesn't want to use a reset. For example, in my use-case, I am using unocss as a complementary tool for Naive-UI. Including resets are breaking pretty much everything. There are only 2 options left:

1. either add b-solid everywhere border is used
2. add

*,
::before,
::after {
  border-width: 0;
  border-style: solid;
}

to global css file or preflights with getCSS

Now even if the second option is ok, it is probably not very convenient to do when you are using another UI framework. As far as I can see, it is not overlapping with Naive UI, but might be something to consider.

[sibbng]

@onur-caplena I posted an alternative solution on #2285 (comment)