I had a nice issue description before github/related issues-beta ate it, here's the gist:

https://getbootstrap.com/docs/4.3/utilities/flex/#justify-content

The flex justify documentation examples only display equal-width items (<div>Flex Item</div>).
It might be wise to add one or two examples with non-equal-width divs and more than 3 cols.

Specifically to illustrate that the middl

Consider the following snippet run in the main process where one wants to listen for "will-prevent-default" events and after some asynchronous operation (do_something, a call which returns a Promise) initiated by the event listener, depending on the result (result) of the operation, call preventDefault on the even

Related to #902, we also should provide some guidelines for Contributing and templates for Issues and Pull request.

Describe the bug
I have no idea how to use FA kit scripts in AMP pages to display icons.

Expected behavior
Explanation in README or a guide "How to use FA in AMP pages"

Bug report checklist

• I have filled out as much of the above information as I can
• I have searched for existing issues and to the best of my know

This is about the Docs.

Overview of the problem

on the documentation page it says that a live example is the fixed table of contents, however when we click the demo it gives another example which is , in my opinion, rather rare in real life.

https://materializecss.com/pushpin.html

I've tried to replicate the fixed toc but to no avail, I've put pinned in the toc div so that it doesn't move but I don't think it's the right solution.

but

🙋 feature request

https://github.com/parcel-bundler/parcel/blob/d24e09a9797af41a9d2c6c733b1c6cf6671d60c7/packages/core/workers/src/Profiler.js#L2

The inspector module not always available, it depends on build param --without-inspector

🤔 Expected Behavior

Compatible with --without-inspector mode.

😯 Current Behavior

Direct import

💁 Possible Solution

Not pretty

• I am on the latest Hyper.app version
• I have searched the issues of this repo and believe that this is not a duplicate

🧐 问题描述

[问题]如何修改区块获取的资源路径，想使用公司自己的github?哪里有相关介绍吗？

目前指向：https://gitee.com/ant-design/ant-design-blocks/

🚑 其他信息

Environment

Vue 2.5.22

Reproduction link

https://jsfiddle.net/ckbq21uL/7/

Steps to reproduce

1. click the change clearable button.
2. close button will disappear.
3. but we can also clear value in panel when type is equal to datetime

What is expected?

clearable means we can or cann't clear this value.
so we shouldn't show clear

When a property is accessed on an object and if the property is not found on that object, the JavaScript engine should looks at the object's __proto__(different browser has their own implement) .Or, looks at the prototype of its constructor.

At least some of the effects in the Border Transition category (like the underline or overline) leave some traces in Safari. This behavior is very random.

Please refer to the following screen shots:

![screen shot 2018-01-29 at 16 43 02](https://user-ima

In response to @ai's comment here, I suggest we use JSDoc annotations to provide type information in JavaScript files w/o a TypeScript build step.

Related

• postcss/postcss#452

bootstrap的打包结构

├── css
│   ├── bootstrap-theme.css
│   ├── bootstrap-theme.css.map
│   ├── bootstrap-theme.min.css
│   ├── bootstrap-theme.min.css.map
│   ├── bootstrap.css
│   ├── bootstrap.css.map
│   ├── bootstrap.min.css
│   └── bootstrap.min.css.map
├── fonts
│   ├── glyphicons-halflings-regular.eot
│   ├── glyphicons-halflings-regular.svg
│   ├── glyphicons-halflings-regu

The responsive menu at http://purecss.io/layouts/tucked-menu-vertical/ does not adjust height as one would expect.

When viewing in a screen smaller than 768px, the "responsive" menu has a fixed height that could potentially cause issues with long menus (or in really small screens with wrapping text).

This can be fixed by replacing the hardcoded height: 14em; at line 69 with height: auto;.

The development documentation is not being updated anymore. I checked out the dev branch and can run it locally but when I try to create a build of this it doesn't reflect the dev branch.

Is your feature request related to a problem? Please describe.
UIApplication#openURL(_:) is deprecated since iOS 10. It appears to be available still in iOS 12, but it will eventually need to be replaced and I could not find an issue for this.

This is used by tns-core-modules/utils's openUrl [here](https

NodeJs v10.15.2
NPM v6.13.1

I'm testing postcss with autoprefixer, and also gulp-autoprefixer.
browserslist setting is default.

Source scss:

body {
    appearance: none;
    user-select: none;
}

@-moz-document domain('example.com') {
    body {
        appearance: none;
        user-select: none;
    }
}

Output css:

body {
    -webkit-appearan

If you're floating content you need to be able to clear the floated item, so could use regular clear-left, clear-right, and clear-both classes.

I was trying to use the pathLength property Stylefire provides, with no luck. Stylefire's documentation reads:
These are all set as a progress of the total path length, from 0 to 100, which is automatically measured by Stylefire.
This seems to be wrong, it should be '0 to 1'.

采用尤大大的回答：

1. 原生 DOM 操作 vs. 通过框架封装操作。

这是一个性能 vs. 可维护性的取舍。框架的意义在于为你掩盖底层的 DOM 操作，让你用更声明式的方式来描述你的目的，从而让你的代码更容易维护。没有任何框架可以比纯手动的优化 DOM 操作更快，因为框架的 DOM 操作层需要应对任何上层 API 可能产生的操作，它的实现必须是普适的。针对任何一个 benchmark，我都可以写出比任何框架更快的手动优化，但是那有什么意义呢？在构建一个实际应用的时候，你难道为每一个地方都去做手动优化吗？出于可维护性的考虑，这显然不可能。框架给你的保证是，你在不需要手动优化的情况下，我依然可以给你提供过得去的性能。

2. 对 React 的 Virtual DOM 的误解。

React 从来没有说过 “React 比原生操作 DOM 快”。React 的基

Not sure if this is a bug or a feature request, but it'd be nice if this Less would try to assume .less even if there's a . in the filename.

For example:

css/bootstrap.less

//...
@import 'bootstrap.theme';

I was hoping it'd import bootstrap.theme.less, but instead it throws this error:

css/bootstrap.less: [L68:C0] 'bootstrap.theme' wasn't found. Tried - css

飞冰物料web3.0-组件-dynamic-icon文档跳转地址错误

Hello, I would like to know Ratchet for Android, WP, iOS, and other platform version of the situation, thank you!