-
@tnajdek I encountered an issue with the native select in default mode in the tablet size: native selects always have the width of the longest option, thus the text of shorter options (_Editor_) doesn…
-
Stylable Intelligence should offer support for all existing features when consuming a 3rd party package (from `node_modules`).
- [x] Completions
- [x] extend
- [x] CSS mixin
- [x] var valu…
-
maybe something like this.
```css
/* stylable-ignore-diagnostics */
```
-
### Existing situation
When using an extended class we can run into three different use-cases.
1. Using a class in the same scope
2. Accessing a class name through a pseudo-element (no explicit i…
-
When I import a theme from `stylable-components` (for instance) I import its theme in my st.css file like so:
```css
:import {
-st-theme: true;
-st-from: "../node_modules/stylable-compon…
-
This throws no error. Though the file test.st.css exists, it doesn't have a 'someVar' symbol
:import {
-st-from: "./test.st.css";
-st-named: someVar;
}
-
Running `npm run storybook` with `wix-ui-core` using yoshi2 , webpack 4, stylable-webpack-plugin version 1.0.19, throws:
```
ERROR in chunk preview [entry]
static/[name].bundle.js
RuntimeTemplat…
-
# Acceptance Criteria
* I can compare two revisions and see visual differences on each of their CMS fields
* I can enter the "compare mode" through a visual trigger
* I get clear indications t…
-
WARNING in Stylable:
Pagination.st.css cannot find formatter:
```css
@media all and (-ms-high-contrast: none), (-ms-high-contrast: active)
```
-
This happens specially when running diagnostics on custom selectors.
Reconstruct bug:
1. Install Stylable Intelligence
2. type `@custom-selector: --l`
3. You will notice that the diagnostic ap…