Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

expose popper "strategy" config to dropdown

See original GitHub issue

In regards to the issue: https://github.com/twbs/bootstrap/issues/32947

It would be nice if this could be solved with a simple data attribute by exposing a data attribute for popper for strategy, like data-bs-strategy.

Popper documentation: https://popper.js.org/docs/v2/constructors/#strategy Example using existing javascript: https://jsfiddle.net/4gpy025q/1/

Thanks

Issue Analytics

State:
Created 2 years ago
Reactions:2
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

Raucecommented, Jun 10, 2021

I fully agree with this suggestion.

I’ve just upgraded to BS 5 in my Blazor app. In BS 4, the data-boundary attribute worked great for my dropdown needs, but I’m stuck in BS 5, and still haven’t come up with a solution.

Having to use new bootstrap.Dropdown(...) for dropdown popper configuration in a Blazor app is highly inconvenient, as Blazor does not lend itself towards executing JS as DOM elements come in and out of existence during re-renders. The attribute approach, however, works perfectly.

1reaction

719mediacommented, May 26, 2021

PR in #34120