menu
Channels
Team
Posts
Members
Info
down-caret

https://reach.tech/router redirects to https://reach.tech

Does anyone know why I'm not able to see the router docs

thumbsup
0
message-simple
2

Is https://reach.tech/ broken?

I can't seem to load anything other than a simple informational page

thumbsup
1
message-simple
5

a11y concerns when using PopperJS instead of / as well as the Reach Popover

I ran up against this issue the other day: https://github.com/reach/reach-ui/issues/631 In general, I've wished for more robust popover management for the MenuButton including: • opening left, right, up, down …

thumbsup
0
message-simple
0

Hi, is there a way to show current value above the SliderHandle?

thumbsup
0
message-simple
1

Should we use Alert when building an accessible Toast component?

I'm using the Toast component for floating-like components used for notifications, or some kind of feedback, or even allowing action items. Quite similar to what Material Design has. Should the underlying component used fo all of these different use cases be the Alert from…

thumbsup
0
message-simple
0

Should it be possible to pass `null` as value to Listbox?

Hi, Looks like it's not possible right now. At least I'm getting the error A ListboxOption must have a value prop. I can't even pass an empty string. Is it a bug or it's expected?

thumbsup
0
message-simple
0

Hi! Is it possible to have trailing slash in <Link> ?

It seems they get removed when the actual <a href> gets generated.

thumbsup
0
message-simple
1

Problems with multiple menu buttons on the same page

I'm seeing a problem both in my app and in my storybook component page for menu buttons. Here's the sequence of events: 1) Click on a menu button Result: the menu opens. …

thumbsup
0
message-simple
0

is it possible to route on a simple html element (<div>)?

Hello. I'm struggling a bit with a very small example that will be the base for the current (big) SPA I'm building. I need to reuse the same component across different routes/parts of the project, so everything needs to be reusable independently from where it is placed. …

thumbsup
0
message-simple
0

Nested routes with default while retaining active link functionality

Let's say I have a route like /resource/:filter where filter could be something like "sent" or "received". Once you're in any of those URLs there's a way to toggle the filter (with NavLinks to /resource/sent or /resource/received). If you access /resource directly a default…

thumbsup
0
message-simple
0