WebExpress 2.0.0‑alpha – Removal of Bootstrap and Popper.js

The release of WebExpress 2.0.0-alpha initiates a radical architectural shift that finally casts off the legacy burdens of past years. The declared goal of this transformation is a drastic reduction in external dependencies, a noticeable performance optimization, and a consistent alignment with modern, native web standards. To achieve this milestone, both Bootstrap and Popper.js are being completely removed from the framework. What seems like a major cut at first glance actually frees WebExpress from unused CSS and external JavaScript dependencies that have simply become redundant in today's browser landscape thanks to modern standards.


However, this deep restructuring brings significant technical challenges, particularly affecting the migration of familiar interactive components. One of the biggest undertakings is the complete transition of modals to the native HTML5 dialog element. Previously, dialog windows had to be painstakingly controlled via nested div structures, Aria attributes, and JavaScript classes to reliably guarantee accessibility and focus management. By switching to the native dialog element, the browser itself now takes over these tasks, which massively cleans up the code but conversely requires a completely new styling and animation concept. Since the native element behaves differently in combination with the backdrop pseudo-class, and CSS transitions during opening and closing are historically challenging to implement, this adjustment demands a precise rethink in the layout process.

Yet the greatest technological challenge of the new framework update lies in completely abandoning external libraries when implementing dropdowns and popover menus. Instead of solving positioning mathematically via JavaScript calculations, the architecture relies on the future-oriented and purely native CSS Anchor Positioning API. Here, the trigger button is defined as a physical anchor in the CSS layout, to which the menu attaches fully automatically via new properties like position-anchor and position-area. WebExpress even hands over the critical flipping of the menu when screen space is tight directly to the browser's rendering engine via the position-try-fallbacks directive. The challenge for developers consists of completely restructuring existing stylesheets and breaking away from the old mindset that layout logic must take place in JavaScript.

Despite eschewing a powerful library like Floating UI, the new path by no means marks the end of JavaScript in WebExpress, but rather an extreme simplification. From now on, the framework's JavaScript no longer calculates pixel distances, but concentrates exclusively on purely functional interaction as well as accessibility, and continues to provide functional controls. Since the native HTML popover attribute already handles opening, closing, and canceling via the Escape key without any custom intervention, a new, ultra-lightweight framework script merely controls keyboard navigation with the arrow keys within open menus. Other dynamic components like the popular carousel also function completely without the usual Bootstrap logic, as they rely on high-performance CSS Scroll Snap, which in turn requires creative tricks when cloning elements to implement infinite loops. Through this resolute step, WebExpress becomes significantly faster, noticeably reduces loading times on mobile devices, and sets a clear signal for clean, standard-compliant code.

The migration path is long and takes place gradually over several phases, which is why active accompaniment along this forward-looking path remains a valuable part of development from the very beginning. Initial feedback, bug reports, and suggestions for handling the new native functions in this early alpha phase are now warmly welcome on the familiar channels to jointly optimize upcoming releases.

Comments

Popular posts from this blog

WebExpress 0.0.10-alpha – A Step Back for Reflection

WebExpress – A Moment to Recharge

WebExpress – The Journey