Skip to content
#

ui

Here are 5,460 public repositories matching this topic...

bvaughn
bvaughn commented Feb 10, 2020

The DevTools Profiler occasionally encounters the error:

Could not find commit data for root "..." and commit ...

This issue is intermittent and we do not currently know hot to reproduce it. If you can reproduce it we would love to get any of the following information from you:

  • Info about how you reproduce it. (Share your code or site with us?)
  • An exported Profiler JSON that contai
rorycawley
rorycawley commented Jan 21, 2020

Title (Put in field above)

Lack of easy start in the 'Getting Started' docs (my suggestion included)

Steps

On this page: https://semantic-ui.com/introduction/getting-started.html

Add instructions similar to this 2 step guide to getting started immediately with semantic UI:
Find the URL for the latest minimized CSS for semantic UI on this page:
https://cdnjs.com/libraries/se

storybook
levelingup
levelingup commented Dec 24, 2019

I tried to follow the initial steps from here: https://www.learnstorybook.com/intro-to-storybook/react/en/get-started/

running:

npx create-react-app taskbox
cd taskbox

Then when I ran:
npx -p @storybook/cli sb init

I get the error TypeError: Cannot set property 'storybook' of undefined

This is the full message in my terminal:

 sb init - the simplest way to add a
svelte
srishak34
srishak34 commented Apr 2, 2019

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

imgui
ocornut
ocornut commented Oct 15, 2019

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.

docz
darioajr
darioajr commented Dec 4, 2019

Bug description
Don´t show table correctly

Expected behavior
A Table view normal

Steps to reproduce the issue:
Crreate a container with large ENV variable

Technical details:

  • Portainer version: 1.21.0
  • Docker version (managed by Portainer): 18.09.3
  • Platform (windows/linux): linux
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):
TalAmuyal
TalAmuyal commented Feb 28, 2019

Looking for help from the community regarding this issue.

Issue:
Unclear CI test failure.

Expected behavior:
Failed test would indicate the failure with some extra info for investigation.

Actual behavior:
Prints Expected: true, Actual: false which is less than optimal.

Steps to reproduce:
Run a failing test.

Would help to have more verbose logging for the tests

editor.js
PaulKinlan
PaulKinlan commented Jan 3, 2020

The current behaviour of the onChange event mandates that the callback needs to be in a closure on the config object because the editor instance isn't available from the onChange event any other way.

e.g

let editor = new EditorJS({
  ...
  onChange: changeHandler
})
changeHandler = () => {  editor.save()  } 

I don't always have access to the editor instance in some abstraction

tshirtman
tshirtman commented Jan 4, 2020

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

evergreen
reactstrap
twgraham
twgraham commented Feb 4, 2020
  • 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

Mobe91
Mobe91 commented Feb 12, 2020

With version 1.13.12 and Bootstrap 3, setStyle fails if newElement.parentNode is a document fragment because classList is undefined in this case. This used to not be a problem with version 1.13.5.

Also, the call to buildData() in refresh() should come before render() like it is done in init().

Improve this page

Add a description, image, and links to the ui topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the ui topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.