ui
Here are 6,248 public repositories matching this topic...
Describe the bug
In the config.js addParameters function, if I set isFullscreen: true and open the webpage, it is fullscreen on startup. But if I set isFullscreen: false and open the webpage again, it is still full-screen on startup.
To Reproduce
- Set
isFullscreen: true, open the webpage, - Close the webpage or stop the server
- Set
isFullscreen: false, open the webpa
A table may be divided each row into separate cells
Something is very strange with that sentence :P It's not proper grammar, but more than that I don't understand what is trying to be said either.
Describe the bug
The content of the the svelte file is a large HTML chunk, withouy any script logics or styling being involved. Max stack size exceeded error while compiling.
To Reproduce
https://svelte.dev/repl/a9dfcc17551c4aeb95e8fe748a97061d?version=3.20.1
Expected behavior
Compiling should not break
Information about your Svelte project:
Svelte 3.20.1, Rollup, Wind
Environment
Vuetify Version: 2.2.20
Vue Version: 2.6.11
Browsers: Chrome 80.0.3987.163
OS: Mac OS 10.15.2
Steps to reproduce
- open console
- focus input
- check console for 'handleFocus'
- click 'no data'
- check console for 'handleBlur'
- re-focus input field
- handleFocus doesn't trigger again
Expected Behavior
v-autocomplete/v-combobox `@b
layui.js中,getPath方法探测layui所在目录代码存在bug,只有layui.js在页面中最后引入时,才能正确找到layui路径。
,getPath = function(){
var jsPath = doc.currentScript ? doc.currentScript.src : function(){
var js = doc.scripts
,last = js.length - 1
,src;
for(var i = last; i > 0; i--){
if(js[i].readyState === 'interactive
希望打包的结构能简单点
Some changes have been made to the main Readme (which appears when landing on the github webpage) and the FAQ. This is a post to notify people, gather some interest and suggestions.
Thanks to @ker0chan for her help on the Readme (lots more feedback that I haven't processed yet) and @ButternCream for his help working on the FAQ.
- Created a [FAQ wiki page](https://github.com/ocornut/imgui/wik
my eyesight are worse, i am using glasses and with brightness... is even worse. for me the documentation feels a bit too bright and its hard to read the documentation. well maybe not that hard but still a bother to the eye, so if it can be granted, my wish, please grant my wish! i beg of you!!
if cannot then i apologize for being dramatic. feel free to close this issue or just delete it
Is your feature request related to a problem? Please describe.
readme is lengthy, verbose, not up to date and difficult to navigate.
Describe the solution you'd like
Add a separate set of docs host on github pages or in the wiki.
Describe alternatives you've considered
This is the alternative.
Additional context
Missing API's, missing examples, missing common solution
Analytics snippets?
Question
Genuinely confused how to add some analytics to the page. I know this is gatsby under the hood, and gatsby has analytics plugins (never use two lines of HTML when you could use a whole plugin, hey Gatsby?) but I really just want somewhere I can customise the raw HTML template for my site.
In the end, I was able to drop in:
New Issue Checklist
- I have looked at the Documentation
- I have read the F.A.Q.
- I have filled out this issue template.
Issue Info
| Info | Value |
|---|
Environment
- Package version(s):
@blueprintjs/core ^3.22.3 - Browser and OS versions: Mac OS X Chrome 79.0.3945.88
If possible, link to a minimal repro (fork this code sandbox):
Steps to reproduce
Spotted this while building a <ControlGroup> that contained buttons, selects, and some dividers.
`
Is your feature request related to a problem? Please describe.
The drop down list for adding/editing volumes on the add/edit container page doesn't have a logical order.
Describe the solution you'd like
A simple alphabetical order would make things easier.
Users using react: 16.9.0 and react-native: 0.61.5 should not be dragging the fonts folder into the project in xcode. They only need to update the PList.
inline toolbar order
-
Updated
Jul 16, 2020 - TypeScript
Is there any way to implement horizontal radio button group?
-
Updated
Apr 1, 2020 - TypeScript
Versions
- Python: 3.6.3
- OS: linux
- Kivy: master
- Kivy installation method: git clone && pip install --editable in virtualenv
Description
when BorderImage's display_size option is used, it overrides the auto_scale parameter, simply because it first computes the value auto_scale would need, and then look if there is a dispaly_border setting, and overrides the values if
- I have searched the issues of this repository and believe that this is not a duplicate.
Version
1.4.10
Environment
Chrome stable v79.0.3945.79
Reproduction link
What would be super nice, is if the headings were linked, so I could share a URL to a specific section of a page, like it does here on GitHub:
Thank
- components:
Input,CustomInput,CustomFileInput - reactstrap version
#8.4.1 - import method
es - react version
#16.12.0 - bootstrap version
#4.3.1
What is happening?
Input's that are invalid (i.e. have the invalid prop set to true), do not have the aria-invalid attribute applied.
What should be happening?
Invalid input's have aria-invalid attribute.
Ste
I think an "added value" to Linux Dash should be the ability to facilitate the creation of custom plugins besides official ones but I haven't found any "getting started" tutorial about this.
Do you think it would be a great idea, too?
Thanks!
It would be great if I could run brew install ungit on OSX. This would install a plist which would automatically start ungit on login.
More resources:
- https://github.com/Homebrew/brew/blob/master/docs/Formula-Cookbook.md
- https://github.com/Homebrew/brew/blob/master/docs/How-to-Create-and-Maintain-a-Tap.md
- https://github.com/FredrikNoren/ungit/wiki/Startup-Script-for-Mac-OS-X
Thank
Improve this page
Add a description, image, and links to the ui topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ui topic, visit your repo's landing page and select "manage topics."



React extension version: 4.4.0
Steps To Reproduce
The current behavior
Extension reports: "This page does not appears to be using React"
The expected behavior
React is detected (just like it is currently in Chrome/Chromium)