sizzle | A sizzlin ' hot selector engine | Content Management System library

I have finally found the underlying problem. I don't know why exactly but installing both bootstrap and @types/bootstrap installed the deprecated version of @popperjs (v1). I needed to install @popperjs/core (v2) and now have to use normal bootstrap and popperjs seperately

You don't actually need javascript. A simple link will do. You can also do it with javascript, but I see no reason to in this case.

This would work:

While I can certainly change the context of $(this) by using $.call(Object, argument) or doing an Object.assign({}, object) somewhere in the code, to manipulate the $.fn.init(selector, context) of jQuery, I have decided to create an alternative Vanilla solution Framework.

And, while jQuery is worth pursuing, I have built this custom CORE jQuery support library in stead. In other words, this framework mimics everything in the jQuery syntax as shown in the minimum code example. I believe that this is also the missing manual that most developers need that is virtually impossible to search these days in the internet due to jQuery's popularity & search ranking wars.

The goal as mentioned in the OP is to try to include only as little jQuery code as possible or implement an alternative solution with the jQuery snippet as needed because jQuery has grown so huge with newer versions and extensions and most of those code have considerable performance overhead other than the learning curve.

With this new CORE, I can easily extend support for jQuery, with $.fn.extend or $.extend or $.prototype.extend and for future use cases whenever the need arises, do another plugin for some basic routines or re-plug $(function()}) or $(document.ready()}) or implement other custom filters and jQuery-like chores, some of which I have already built and stripped off from this code such as event handlers and the $.ajax.

The good news is, we can even reuse already built favorite jQuery plugins without having to worry about compatibility issues because the power of jQuery is already in our hands! The core also preserved our favorite dot notation among others! :D

Overall, this is very handy whenever building minimal, manageable, reusable, modular Javascript, as well as building on top of the missing Vanilla learning curve and understanding how browsers work, especially because the heart of jQuery which is the $.extend is herein preserved. Some of the mechanics of this library though (about 2% of the code), is ported from jQuery and I'm planning to build on top of this CORE for my projects without having to worry about licenses.

That said, I hope this will be helpful to some developers out there. I'm licensing this code with MIT.

When you do:

You could try and wrap the text that varies in length in a div element and fix it's height, so that the longest text doesn't move the table.

In your html:

The .data() returns a string or JSON as the response. In your case, it should be string. All you need to do is lose the .text().

Sizzle is a pure-JavaScript CSS selector engine designed to be easily dropped in to a host library.

Its a spin-off of jQuery project they say, but when it comes to differnce between jQuery and Sizzle, JQuery is a library build to simplify javascript complex syntax that people found hard to understand and get a grid of specially the begineers. So if you are using JQuery, there is going to be a lot of overhead along with it where as sizzlers offer comparatively less.

Its preferred to use querySelector over Sizzler because its just an added overhead which can very easily be done with VanillaJS so why waste it. They both do the same thing.

there's no need by putting both primefeces folder and vendor>jquery

you can try that architecture:

HTH

It doesn't match because your key / header starts with an invisible character: