ui-components
Here are 2,121 public repositories matching this topic...
-
Updated
Dec 20, 2020 - JavaScript
Environment
Vuetify Version: 2.3.16
Vue Version: 2.6.12
Browsers: Safari 14.0
OS: Mac OS 10.15.7
Steps to reproduce
Just try select part of text with mouse
Expected Behavior
Selected part of text
Actual Behavior
not selected text
Reproduction Link
-
Updated
Feb 17, 2021 - JavaScript
-
Updated
Feb 18, 2021 - TypeScript
-
Updated
Feb 17, 2021 - JavaScript
-
Updated
Feb 18, 2021 - TypeScript
-
Updated
Feb 17, 2021 - JavaScript
Marko Version: 4.18.4
Details
I use some facebook markup that I let facebook parse from DOM:
<fb:login-button
auto-logout-link="false"
button-type="continue_with"
size="large"
scope="public_profile,email"
use-continue-as="true">
</fb:login-button>
In my onMount I then let the facebook API do it's thing with th
-
Updated
Feb 12, 2021 - SCSS
-
Updated
Feb 14, 2021 - Swift
This is frequently asked question about the cascader component. Adding a FAQ section would help more users who have the same problem.
-
Updated
Jan 25, 2021 - Objective-C
-
Updated
Feb 9, 2021 - JavaScript
-
Updated
Sep 4, 2020 - Java
-
Updated
Jan 20, 2021 - JavaScript
-
Updated
Nov 23, 2020 - Vue
-
Updated
Feb 15, 2021 - JavaScript
Hi,
When I use multiple iframe in my web page with pNotify and do submit or a button click in the page, I am getting error "Uncaught TypeError: Cannot read property 'opener' of undefined" in at PNotify.position (pnotify.js:641).
I am getting this error when I am changing a iframe src in a text box change event and do submit the page. This is happening only in Chrome browser.
Please help me
-
Updated
Jan 7, 2021 - JavaScript
使用XUI的APP产品信息收集
-
Updated
Aug 6, 2020 - JavaScript
-
Updated
Jun 4, 2019 - Objective-C
-
Updated
Jan 20, 2021 - Vue
Improve this page
Add a description, image, and links to the ui-components topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ui-components topic, visit your repo's landing page and select "manage topics."

Is your feature request related to a problem? Please describe
I am writing cypress tests for my Storybook documentation, and have leveraged control ids for boolean and radio controls. But I have noticed for other control types these ids are not generated
As an example for radio buttons each input is given the id {controlName-optionName}, which is nice and predictable
A couple of control