confirming this for unstable and backports 5.3.3 versions and also the
bookworm 5.2.3 version.
I also tested if the behaviour matches the upstream binary, e.g. from
https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js
and with the upstream version there is no problem to get the example dropdown
from the docs at
https://getbootstrap.com/docs/5.3/components/navbar/#supported-content
When using the packaged version instead, i get
Uncaught TypeError: n.createPopper is not a function
_createPopper dropdown.js:241
show dropdown.js:139
toggle dropdown.js:121
<anonymous> dropdown.js:446
i event-handler.js:118
R event-handler.js:184
on event-handler.js:216
<anonymous> dropdown.js:444
<anonymous> bootstrap.bundle.min.js:6
<anonymous> bootstrap.bundle.min.js:6
as i understood from the previous messages that poppler 2 solves this, i tried
to build a version from the source package that includes poppler2, so i tried
changing the build dependency to version 2.
As i could not get the debian/node/extlink working with poppler2, I removed
it, then the build succeeded, but the resulting deb is always the same, either
with popper 1 installed as build dependency and the extlink active, or with no
popper2 or no popper at all installed and extlink inactive.
The result when using the bootstrap.bundle.js file is always the same error,
and the deb files have the same md5sum.
I might be getting something wrong but to my amateurish eyes with not much
clue about javascript deb packaging it looks like no popper at all is used in
the whole process, nor included in the bootstrap.bundle.js file.
Would like to help fixing this but right now I'm out of ideas how to get
popper 2 used in that build process and included in the bundle ;)
