Although they are a visual enhancement, they are quite hard to maintain. The colors have changed in v5 and probably the grid gutters and carousel navigation will follow.

I would prefer to ditch them unless we can easily automate the image generation process.

https://twbs-bootstrap.netlify.com/docs/4.3/examples/#content

Prettier supports EditorConfig, but the docs are almost silent about this fact. In particular:

• the "Options" page must specify which options and how can be set via EditorConfig,
• the "Configuration File" page should mention EditorConfig somewhere.

See also https://gi

When you render an alert within a modal the close classes clash impacting the alert icon.

Device

• Browser [*]
• OS: [*]

To reproduce

Steps to reproduce the behavior:
https://jsfiddle.net/1xejsv5w/

Screenshots

See jsfiddle above.

Is your feature request related to a problem? Please describe.

NES.css doesn't contain layout styles. This puts a burden on developers.
So I think it will be e

I want to use ReLaXed with remote chromium to reduce docker image size. It is posible with browser options --remote-debugging-address and --remote-debugging-port (https://peter.sh/experiments/chromium-command-line-switches/). It would be great add CLI options for puppeteer https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#puppeteerlaunchoptions (especialy for args option).

I didn't see any way to send this feedback from the website, so I'm posting here as an issue.

The installation docs lists the following clone url:

https://github.com/coreui/free-bootstrap-admin-template.git

when in fact it should be this repo's url:

<https://github.com/coreui/coreui-free-bootstrap-admin-template.g

Clearly describe the bug

"false-positive" no-descending-specificity with "empty" definitions (see below)

Which rule, if any, is the bug related to?

no-descending-specificity

What code is needed to reproduce the bug?

    nav {
      display: inline-block;
      a {
        display: inline-block;
      }
    }

    a,
    button,
    label {
      &:focus,

• NPM version (npm -v): 6.13.4
• Node version (node -v): v13.6.0
• Node Process (node -p process.versions):

{
  node: '13.6.0',
  v8: '7.9.317.25-node.26',
  uv: '1.34.0',
  zlib: '1.2.11',
  brotli: '1.0.7',
  ares: '1.15.0',
  modules: '79',
  nghttp2: '1.40.0',
  napi: '5',
  llhttp: '2.0.1',
  openssl: '1.1.1d',
  cldr: '35.1',
  icu: '64.2',
  tz: '2019a',
  u

Instead of embedding normalize gutenberg should probably say it's required in the documentation then users could use a newer version of normalize

Summary

The storybook documentation for React Carbon components is unprofessional. Text ought to be re-written so it is informative and mature.

Justification

It's important people think of a library built by IBM in a professional manner.

Examples

<img width="1278" alt="Screen Shot 2020-04-21 at 12 14 33 PM" src="https://user-images.githubusercontent.com/13704150/79893846-3

I run into this project and want to build more components for it. Can we have a possible guideline for new contributors?

I'm not really sure the link underline goes well with the theme look and feel. I am thinking more of a single squiggly underline would be better. I don't have the skill alter the background-image gradient though through.

Expected Behavior

When visiting the Shards UI demo page, using the left and right tooltip/popover examples places the info on the opposite of the expected side of the element.

Using data-placement="left" should place elements on the left. Similarly data-placement="right" should place elements on the right.

Current Behavior

Example screenshots:

![Screenshot_20190626-135428](http

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

Currently, contributing to this project can be hard especially for beginners like me who do not understand the project structure.

How To Reproduce

Put yourself into a beginner's shoes.

Let's say you want to contribute code to resolve a feature request (something like #1180, which introduces support

I'm using this checkbox library and it looks proper in some places, and in some others it looks unaligned for some reason which I can't figure out. I'm using Bootstrap 3 in my project and whenever I use a checkbox in a .row/col-* I get issues.

This is how it looks like:

![

We document how to release a new version of Bitters in RELEASING.md.

There are a couple of items missing:

1. After a release is published, it should be added as a release to Hub (this link is private to the thoughtbot team)
   • Releases captured in Hub are sent out in our [weekly new

Should it be string[] or list(string) or anything else?

/// @param {string[]} $args - list of strings
@mixin join($args...) {
  // ...
}