Feature Requests

Expanding the grid exporter capabilities within Ext JS so developers can define export-only columns (e.g., identifiers like broker, month, and year that are hidden in the UI but required in reports), respect summary row ignore configurations so exports do not display unwanted default values such as summary zeros, and provide richer export style options for numeric formatting (including comma separators and no decimals) without requiring custom renderers.
It also suggests preserving numeric data types during export even when renderers are used avoiding Excel warnings and maintaining spreadsheet usability and adding support to strip HTML from column headers or define separate export text so rich UI formatting does not carry over into exported documents.
Collectively, these enhancements would improve data fidelity, reporting flexibility, and user experience by allowing exports to include the right contextual information and formatting while keeping the application interface clean and optimized for on-screen presentation.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Introducing native support for dynamically hiding and showing the grid summary row, similar to how the filter bar plugin can be toggled. In many real-world scenarios, developers reuse the same grid component for multiple contexts, for example, displaying a full list with filters and summaries in one view, and then reusing that same grid to show a filtered subset of records based on a user action. While it is currently possible to hide the filter bar and programmatically apply filters, there is no straightforward built-in way to toggle the summary row’s visibility without additional customization. Providing simple methods such as hideSummaryRow() and showSummaryRow() would improve component reusability, reduce duplication, simplify view management, and make grids more flexible for dynamic UI scenarios.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Add the ability to define a separate label for grid column menus, independent of the column header configuration. In scenarios where column headers contain HTML for formatting or styling purposes, the column menu currently displays the raw HTML tags, which can lead to a cluttered or unpolished user experience. Providing a built-in option to either automatically strip HTML from the menu label or explicitly override the menu text would offer greater flexibility and cleaner presentation. This enhancement would improve usability, maintain visual consistency, and reduce the need for custom overrides, making grid configurations more adaptable for modern, richly formatted interfaces.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Add native support to print a Panel or ideally any component or combination of components - directly as a formatted HTML document or, even better, as a PDF. While exporting grids or pivot tables to XLSX or CSV makes sense for structured data, many real-world applications include highly customized Panels with rich HTML layouts that users need to print or share. Currently, achieving this requires significant custom JavaScript and CSS to format the output properly. Providing built-in printing and PDF export capabilities would streamline development, reduce complexity, and deliver a more seamless experience for end users who need polished, printable versions of custom views.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Expanding the capabilities of the date picker field to support additional built-in restrictions beyond the existing maxDate configuration, such as automatically disabling weekend selections (Saturday and Sunday) and preventing users from choosing dates after today. While maxDate effectively limits future dates, having a simple, declarative way to exclude weekends - similar to how the Calendar component can hide Saturdays and Sundays - would significantly improve usability and reduce the need for custom validation logic.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

This feature suggestion proposes adding built-in support for configurable password policies at the password field level, enabling developers to enforce security standards more easily and consistently across applications. Ideal capabilities would include setting a minimum password length, requiring specific character types (such as uppercase letters, lowercase letters, numbers, or special characters), preventing password reuse (where feasible), and optionally defining or integrating with a specific encryption algorithm. Providing these options natively would streamline implementation, reduce custom validation logic, promote best security practices!

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Enhance the Pivot Grid Drill Down plugin to support working seamlessly with bound stores or allowing the drill-down store to be redefined so that drilled data always matches dynamically loaded datasets (such as displaying data for the current year), while also supporting custom drill-down columns. In addition, it would be highly valuable to allow the drill-down viewer title to be configurable or dynamically generated instead of always displaying a static label like “Drill Down.” For example, developers could define a contextual title such as “Account Details” or dynamically generate a title like “Account Details for Company ABC, Jan 25,” where the company name and date are derived from the selected pivot cell. These enhancements would significantly improve flexibility, contextual clarity, and overall user experience in real-world, data-driven applications.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Enhance the GridFilterBar plugin so that boolean filter types display their preconfigured default values directly in the filter bar, just like string and date filters do. While boolean filters are currently applied correctly at the data level and indicated via column header styling, the selected default value (e.g., true or false) is not visually reflected in the filter control itself. Automatically initializing and displaying the selected state for boolean filters would improve UI consistency, increase transparency around active filters, reduce user confusion, and deliver a more intuitive and predictable filtering experience overall.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Available via npm, this library reimagines how developers build applications with ExtJS by introducing modern, reactive principles. It blends the structured power of ExtJS with contemporary component-driven patterns to create a smoother and more efficient development experience.

Designed with productivity in mind, it helps developers:

• Write cleaner and more maintainable code
• Structure applications in a more scalable way
• Apply reactive concepts within the ExtJS ecosystem
• Reduce boilerplate and increase development speed
• Build user interfaces in a clear and elegant manner

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit

Add a saveFormat configuration option to Ext.form.field.Date that automatically formats date values when calling form.getValues() or form.getSubmitData(). Currently, dates must be manually formatted field-by-field, but a saveFormat config would allow developers to specify the serialization format (e.g., 'Y-m-d') independently from the display format, enabling seamless bulk operations and consistent date formatting across form submissions.

* Your feedback will only be visible to Sencha.

* Your Feedback contains offensive words.

Submit