Perhaps I'm an idiot, but it wasn't immediately clear to me that the examples were actually examples. They looked like images. I only discovered that they were interactive after I got frustrated that I couldn't find the 'examples' section. Here's the page I'm referring to: http://fezvrasta.github.io/popper.js/ Anway, looks like a great project :)
Oh... Any idea to make them look more like examples?
Show HN: Popper.js, a 3KB library to manage tooltips and popovers
11–20 of 62 posts
Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#12Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#13Warning: [react-router] You cannot change ; it will be ignored
Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#14Has anyone tested it with react? It messes with my routes for some reason. Warning: [react-router] You cannot change ; it will be ignored
Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#15Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#16Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#17I've heard, secondhand, from disabled people that tooltips are particularly troublesome for screen readers, keyboard traversal, etc. Might be worth looking into things that would reduce the pain, like associating the tooltips with their "parent" element via or aria tags, etc.
Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#18The is the CSS only option from Primer (GitHub design guideline). If you use in your project is the tiniest that i've ever seen and it's easy to customize via SASS. (the time that is default it's not good in my opinion, but you can change, it's a SASS variable. http://primercss.io/tooltips/
Re: Show HN: Popper.js, a 3KB library to manage tooltips and popovers
#19I've heard, secondhand, from disabled people that tooltips are particularly troublesome for screen readers, keyboard traversal, etc. Might be worth looking into things that would reduce the pain, like associating the tooltips with their "parent" element via or aria tags, etc.
Surely must be done something for this problem. But Popper.js wants just to position your popper in the page. The rest is up to the developer.
var popper = new Popper(referenceElement, onBottomPopper, {
placement: 'bottom'
});
Popper.js already knows that referenceElement is the association, so it seems reasonable to consider if it should (maybe optionally) create the or aria association between the two.Similar for default keybindings that make sense.