Please add Order to all the elements at all the breakpoints. To create accessible and semantically correct post card layouts, the image should not be first in the DOM order and often pre-header text should visually appear first, but should be a secondary element for the same reasons.
If the 100% Width Padding field is left blank, all padding values in the builder options are ignored. In Live Builder, when you hover over the container, they appear, but the content is not affected (like it is absolutely positioned).
This is a combination of bug and feature request, but I used the feature request because it works as coded but needs to change. My logs on every site I build are filled with sanitization errors. PHP Warning: A non-numeric value encountered in /srv/htdocs/wp-content/themes/Avada/includes/lib/inc/class-fusion-sanitize.php on line 510 PHP Warning: A …
Add fallback font settings to custom fonts.
Native support for variable fonts in the custom typography with the appropriate setting or a field for entering font-variation-settings.
Please add native support for captcha alternatives like Turnstile (preferred) and hcaptcha. Reliance on all things Google is problematic for many.
Please add a "clickable parent" feature to the post card design. Clickable parent allows the hyperlinked title to own the entire box (article) without breaking accessibility.. This is done using absolute positioning. It may require some recoding because of the overuse of divs in Avada. SCSS sample can be found …
Add the ability to select multiple post types within a post cards element.
Create a dynamic table (fully WCAG compliant) that can be used as an output for the post cards element. It might be wise to rename the post cards element or create another element to reflect the fact it is a query loop builder.
Since the post cards element is really nothing but a query loop builder, add the ability to use the post cards element within a post card layout.
Please upgrade the Font Awesome library to the current free version. Add support for the pro version of all font styles. Related, please fix compatibility with the Font Awesome plugin - Avada calls the entire library on load, breaking the auto-subsetting.
The new responsive image feature that gives you the option to choose a different image on a smaller screen, must give us a way to remove the image completely. As of right now, that option does not exist, or it is unclear how to make that happen.
