Jason Quense
Jason Quense
Ya'll i think it's time we stop grumbling in the issue tracker here. I also want to see the project move forward but Maintainers don't owe us anything. The better...
You can dispute whatever you want with npm, they are usually very helpful, you don't need "cause" to contact support over package ownership, it's not a legal proceeding
if you say it's useless before trying that's fine guy. I don't care. I've had luck talking to them about conflicts and they have been very helpful without it having...
The webpack caching mechanism is a black hole...I took a few hours to explore this and it's basically impossible to discern what the code is even doing. AFAICT there is...
I would also love to not pin css-loader anymore, is there anything i can do here to move this along? I don't think this is just an astroturf issue, anything...
For quick refresh: when css-loader hashes classnames, it only looks are resourcePath. which is "wrong" for resources imported with `!=!` match resource, resulting in duplicate classNames for: ``` 'style1.css!=!button.js' 'style2.css!=!button.js'...
You can control this via the modal manager prop. Check out the constructor options to it to disable the overflow.
We can't use dialog elements because they aren't supported by our range of browsers. I will say though that our implementation is NOT a deeply nested set of divs. The...
The normal modal behavior is to focus the modal not the first interactive element. If it's focusing something else you may have `autoFocus` on an input set
probably, but i don't think about it since we cherry-pick