Start sharing components as a team!Share components as a team!Join Bit to build your applications faster.Get Started Free

style

v0.0.12arrow_drop_down
v0.0.12
v0.0.11
v0.0.10
v0.0.9
v0.0.8
v0.0.7
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
STATUS
Passing
DOWNLOADS
1,785
LICENSE
MIT
VISIBILITY
Public
PUBLISHED
11 months ago
SIZE
5 KB
Use a better box model (opinionated).
1 contributor
Install style as a package?
Copied
npm i @bit/nju33.com.style
Set Bit as a scoped registryLearn more
npm config set '@bit:registry' https://node.bit.dev
Component Example
React
React
Vue
Angular
React Native
Add dependency... help_outline
Just
import
any of the 1 million components
and packages in Bit or NPM to the example.
import Button from '@bit/grommet.grommet.button';
import Lodash from 'lodash';
toggle layout
modifieddraft
chevron_left
chevron_right

Use a better box model (opinionated).

Use a more readable tab size (opinionated).

  1. Correct the line height in all browsers.
  2. Prevent adjustments of font size after orientation changes in iOS.

Remove the margin in all browsers.

Improve consistency of default fonts in all browsers. (https://github.com/sindresorhus/modern-normalize/issues/3)

  1. Add the correct height in Firefox.
  2. Correct the inheritance of border color in Firefox. (https://bugzilla.mozilla.org/show_bug.cgi?id=190655)

Add the correct text decoration in Chrome, Edge, and Safari.

Add the correct font weight in Edge and Safari.

  1. Improve consistency of default fonts in all browsers. (https://github.com/sindresorhus/modern-normalize/issues/3)
  2. Correct the odd ‘em’ font sizing in all browsers.

Add the correct font size in all browsers.

Prevent ‘sub’ and ‘sup’ elements from affecting the line height in all browsers.

  1. Remove text indentation from table contents in Chrome and Safari. (https://bugs.chromium.org/p/chromium/issues/detail?id=999088, https://bugs.webkit.org/show_bug.cgi?id=201297)
  2. Correct table border color inheritance in all Chrome and Safari. (https://bugs.chromium.org/p/chromium/issues/detail?id=935729, https://bugs.webkit.org/show_bug.cgi?id=195016)
  1. Change the font styles in all browsers.
  2. Remove the margin in Firefox and Safari.

Remove the inheritance of text transform in Edge and Firefox.

  1. Remove the inheritance of text transform in Firefox.

Correct the inability to style clickable types in iOS and Safari.

Remove the inner border and padding in Firefox.

Restore the focus styles unset by the previous rule.

Remove the padding so developers are not caught out when they zero out ‘fieldset’ elements in all browsers.

Add the correct vertical alignment in Chrome and Firefox.

Correct the cursor style of increment and decrement buttons in Safari.

  1. Correct the odd appearance in Chrome and Safari.
  2. Correct the outline style in Safari.

Remove the inner padding in Chrome and Safari on macOS.

  1. Correct the inability to style clickable types in iOS and Safari.
  2. Change font properties to ‘inherit’ in Safari.

Manually forked from SUIT CSS Base: https://github.com/suitcss/base A thin layer on top of normalize.css that provides a starting point more suitable for web applications.

Removes the default spacing and border for appropriate elements.

Work around a Firefox/IE bug where the transparent button background results in a loss of the default button focus styles.

Tailwind custom reset styles

  1. Use the user’s configured sans font-family (with Tailwind’s default sans-serif font stack as a fallback) as a sane default.
  2. Use Tailwind’s default “normal” line-height so the user isn’t forced to override it to ensure consistency even when using the default theme.

Inherit font-family and line-height from html so users can set them as a class directly on the html element.

  1. Prevent padding and border from affecting element width.

    We used to set this in the html element and inherit from the parent element for everything else. This caused issues in shadow-dom-enhanced elements like

    where the content is wrapped by a div with box-sizing set to content-box.

    https://github.com/mozdevs/cssremedy/issues/4

  1. Allow adding a border to an element by just adding a border-width.

    By default, the way the browser specifies that an element should have no border is by setting it’s border-style to none in the user-agent stylesheet.

    In order to easily add borders to elements by just setting the border-width property, we change the default border-style for all elements to solid, and use border-width to hide them instead. This way our border utilities only need to set the border-width property instead of the entire border shorthand, making our border utilities much more straightforward to compose.

    https://github.com/tailwindcss/tailwindcss/pull/116

Undo the border-style: none reset that Normalize applies to images so that our border-{width} utilities have the expected effect.

The Normalize reset is unnecessary for us since we default the border-width to 0 on all elements.

https://github.com/tailwindcss/tailwindcss/issues/362

Reset links to optimize for opt-in styling instead of opt-out.

Reset form element properties that are easy to forget to style explicitly so you don’t inadvertently introduce styles that deviate from your design system. These styles supplement a partial reset that is already applied by normalize.css.

Use the configured ‘mono’ font family for elements that are expected to be rendered with a monospace font, falling back to the system monospace stack if there is no configured ‘mono’ font family.

Make replaced elements display: block by default as that’s the behavior you want almost all of the time. Inspired by CSS Remedy, with svg added as well.

https://github.com/mozdevs/cssremedy/issues/14

Constrain images and videos to the parent width and preserve their instrinsic aspect ratio.

https://github.com/mozdevs/cssremedy/issues/14

Help and resources