Open bstopp opened 16 hours ago
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed. In case there are problems, just click a checkbox below to rerun the respective action.
Page | Scores | Audits | ||
---|---|---|---|---|
:iphone: | /en-us/fragments/who-we-serve-tabs | |||
:desktop_computer: | /en-us/fragments/who-we-serve-tabs | |||
:iphone: | /en-us/who-we-serve | |||
:desktop_computer: | /en-us/who-we-serve |
@bstopp looks like a good solution and appears to solve the issues. All good from my end.
This PR is intended to fix some issues with authoring both Columns and Tabs blocks.
In an effort to expedite as solution I have split these two blocks into separate logic paths.
Added "Wrap Mobile" Columns Type
This will use the number of authored columns as the maximum allowed at desktop viewport. At smaller views it will use wrapping logic for fewer entries per row. This prevents items from shrinking too small, while allowing for an improved authoring experience.
Only way to get to this logic path is to use the
wrap mobile
keyword variation.Added "Fetch" Tabs Type
In this variation of the block, rather than authoring each tab in a row - you simply specify the URL of the content. The target page will be fetched. Each section in the target page becomes a Tab. The title of the tab is controlled by the Section Metadata "Title" attribute.
Again, the only way to use this type of block is to use the
fetch
keyword variation.Using this approach I should have prevented any impact to existing Column or Tab implementations across the site, while supporting a new feature set.
Fix #441
Test URLs: