Releases: jadu/pulsar
Releases · jadu/pulsar
8.2.2
⚠️ Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
- Changes to the markup of core elements which may break BDD/TDD tests within Continuum products which target specific selectors
| Component | PR | Details |
|---|---|---|
| Datatables | #896 | Position of the sorting arrow in a column header has changed to the right hand side of a column instead of being immediately after a label |
🔴 Major / breaking changes
None in this release
💚 Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Datatables | #896 | Change position of column sorting arrows to the right hand side of the column, this improves the ability of the sorting arrow to respond to varying label lengths and viewport sizes |
| Navigation | #896 | Make sure quaternary nav (used when accessing submenus from the 'more' menu) works when the nav link is a button instead of an a |
8.2.1
⚠️ Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
- Changes to the markup of core elements which may break BDD/TDD tests within Continuum products which target specific selectors
None in this release
🔴 Major / breaking changes
None in this release
💚 Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Date Helper | #887 | Add Placeholder Initialization Functionality for Date Helpers |
8.2.0
⚠️ Changes which may alter expected/established behavior
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
- Changes to the markup of core elements which may break BDD/TDD tests within Continuum products which target specific selectors
| Component | PR | Details |
|---|---|---|
| Base template | #multiple | The tab index of common base elements has been modified to meet WCAG criteria, this may affect BDD tests which attempt to navigate the DOM by triggering tab keypresses |
| Settings sidebar | #854 | Link colour contrast has been increased to maintain WCAG contrast compared to the grey settings sidebar background |
| Toggle switches | #881 | This change restores the ability for a toggle switch to be toggled by clicking the control label, this represents a change to currently observed behaviour |
| Navigation | #834 | Primary navigation links and the close nav link now use <button data-target="#fragment"> instead of <a href="#fragment"> for a11y reasons, this may break Continuum tests which target these elements |
🔴 Major / breaking changes
None in this release
💚 Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Toggle switches | #881 | Various toggle switch accessibility improvements |
| CMS | #879 | CMS Fixes for Pulsar 8.1.0 |
| Date Helper | #873 | Date helper does not support international date formats |
| Navigation | #834 | Fix a11y issues in primary navigation helper |
| Forms / Colour picker | #823 | There is a hidden input (by display:none) which has no label and is not required to be interacted with, this has been changed to type="hidden" to allow it to continue unlabelled |
| Forms / Toggle Switch | #823 | There are two label elements in this control, both were using the same value passed to the helper. One of them now appends to the passed value, e.g. 'toggle $value' to stop the error regarding duplicated labels |
| Help Text Component | #823 | Change the open/close controls to use <button> rather than <a> |
| Navigation | #823 | Change the default href for the main branding image (top left) to be / instead of # |
| Notifications | #823 | Change the notification toggle (bell icon), 'dismiss all' and 'view all' actions to use <button> rather than an <a> |
| User Guides | #823 | Change the user guides button to use a <button> rather than an <a> |
8.1.1
8.1.0
Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals, but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
Unless marked as [MAJOR] these are not considered to be breaking changes within the scope of Pulsar and expected Pulsar implementations within the Continuum Platform.
| Component | PR | Description |
|---|---|---|
| Datatables | #870 | The no-wrap rule which was applied to table headings has been removed to improve the responsiveness of all tables. This may result in columns being different widths pre/post patch and may be raised by test/QA as a difference |
| Navigation | #865 | The tabbing order of the main navigation and toolbar has been altered to meet WCAG 2.1 criteria for logical tabbing order, this change may be noticed by people using the keyboard to navigation the UI |
Major changes
None in this release 🎉
Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Navigation | #868 | Secondary navigation items (in the blue flyout) will now be read by screen readers using the 'module' name also, e.g. 'Documents, Publishing'. This is to meet WCAG guidance and improve the navigation experience for assistive technology users |
| Navigation | #867 | Make sure nav helper correctly parses CMS heading IDs |
| Tabs | #866 | Restore tab functionality with the presence of the new bypass block markup |
| Styles | #855 | Addition of Timeline styles from to Pulsar |
8.0.0
Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals, but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
Unless marked as [MAJOR] these are not considered to be breaking changes within the scope of Pulsar and expected Pulsar implementations within the Continuum Platform.
| Component | PR | Description |
|---|---|---|
| Main layout | #840 | An explicit white background has been added to the body element, this may cause unintended effects to non-standard Pulsar layouts (all Pulsar common patterns have been tested) |
| Form helpers | #836 | Only certain helpers will now use the disabled boolean attribute, others will use aria-disabled instead, this may affect third party code which relies on invalid disabled attributes |
| Modals | #828 | The size of modal titles has been increased to maintain a visual hierarchy, this may be noticed by test/QA as a visual difference and questioned |
| Tabbed navigation | #832 | Disabled tabs will now be present in the tabindex, this is a change to the current behaviour which prevents disabled tabs from being tabbed to via keyboard navigation |
| Notification menus and user guide images | #862 | Required for Pulsar UIs to meet WCAG 1.1.1 Non-text Content: (Level A). The html.media helper will now add role="presentational" if no image alt attributes exist. Notification menus in continuum products will need to manually add role="presentational" to notification menus where needed. |
| Input groups and Select2 display issues | #864 | Selects2 and input groups now display correctly. Select2s now work as expetced with form group sizes. |
Major changes
| Component | PR | Description |
|---|---|---|
| Form helpers | #827 | 🚨Breaking change🚨Form field help and error text is now correctly read by screen readers. Form helpers now use a new twig extenstion. Products will need to include the new HelperOptionsModifierExtensionwithin their Twig config. |
| Skip to content link | #863 | Required for Pulsar to meet WCAG 2.4.1 Bypass blocks (level A), a skip link has been added to allow users to jump to a pages main content area. Products which do not use views/pulsar/layouts/base.html.twig will need to add this manually along with a wrapping div. See the #863 for examples. |
Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Modals | #828 | Modal Titles and Table Details Pattern Title Font Size Increase |
| Misc | #830 | Fixed an issue with builds failing due to an invalid filename on Windows |
| Tabbed navigation | #832 | Disabled tab links no longer use tabindex="-1" and now use aria-disabled rather than disabled to correctly announce theirs state to assistive devices |
| Radio simple | #850 | Add missing ‘:’ in the Radio Simple Docs |
| Misc | #851 | Correct the SVG focus the CMS logo |
| Table Details | #853 | Close the table details panel when clicking outside of the details container |
| Footer | #860 | Increase contrast ratio of year text in footer |
7.0.9
Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals, but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
Unless marked as [MAJOR] these are not considered to be breaking changes within the scope of Pulsar and expected Pulsar implementations within the Continuum Platform.
Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Misc | #830 | Fixed an issue with builds failing due to an invalid filename on Windows |
7.1.1
Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals, but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
Unless marked as [MAJOR] these are not considered to be breaking changes within the scope of Pulsar and expected Pulsar implementations within the Continuum Platform.
| Component | PR | Description |
|---|---|---|
| Forms | #818 [patch] | The form.choice helper previously had overflow:hidden on the form__group which caused issues where the new Pulsar radio input outline would be clipped by the container. The overflow has been removed now which fixes the radio outline and hasn't caused any visual regressions that we've observed, but may cause unintended issues elsewhere |
Major changes
None in this release 🎉
Minor / patch changes
| Component | PR | Details |
|---|---|---|
| Forms | #818 [patch] | Remove overflow:hidden from the form.choice container to stop radio buttons having their outline clipped |
| Table Detail | #818 [patch] | Fix issue where the table detail content would break out of the detail container when scrolling |
Add default padding to table detail body container, removing the need for <div class="padded"></div> |
||
Change table detail title to a h1 |
||
| Utility classes | #818 [patch] | Add new u-margin-bottom and u-margin-bottom--large utility classes |
7.1.0
Changes which may alter expected/established behaviour
The following changes are estimated to have the highest potential to introduce unwanted change within any software package updating to this version of Pulsar. This type of potential change includes, but is not limited to:
- Actual visual regressions outside of the scope of the intended Pulsar component (aka 'leaky styles')
- Perceived visual regressions (where the change implements/restores expected visuals, but may cause QA/users to question the change)
- Errors in non-Pulsar javascript which rely on Pulsar components or interactions to behave a certain way
Unless marked as [MAJOR] these are not considered to be breaking changes within the scope of Pulsar and expected Pulsar implementations within the Continuum Platform.
| Component | Issue | Description |
|---|---|---|
| General | #810 [patch] | At some point (possibly a bad merge) the has-danger state class (and has-error alias) were removed. These have now been restored but any third party components which piggyback on these classes, and don't expect the default error styling, may suddenly present with different error styling than expected |
| Forms | #807 [patch] | If an input has multiple appended buttons these will now be separated rather than conjoined, while this is restoring documented/expected styling it may be interpreted as splitting a single button into two separate controls |
| #796 [patch] | If an element with a tooltip contains a disabled element (e.g. <div rel="tooltips" title="my tooltip"><input type="text" disabled /></div>) then pointer events will now be turned off on the disabled elements. This is to maintain the expected behaviour of tooltips but may introduce unwanted behaviour on any non-Pulsar javascript that relies on disabled elements remaining interactive |
|
| Main Navigation | #805 [minor] | Opening the secondary navigation panel now triggers the popover('close') method to close all open popovers, this may cause unexpected behaviour in UIs which rely on popovers remaining open |
| Modals | #791 [minor] | The first interactive form field in a modal now captures keyboard focus when that modal is opened, this may be a noticeable difference to users who expect to manually select the first field in a modal form |
| Popovers | #805 [minor] | Opening the secondary navigation panel now triggers the popover('close') method to close all open popovers, this may cause unexpected behaviour in UIs which rely on popovers remaining open |
| Tooltips | #796 [patch] | If an element with a tooltip contains a disabled element (e.g. <div rel="tooltips" title="my tooltip"><input type="text" disabled /></div>) then pointer events will now be turned off on the disabled elements. This is to maintain the expected behaviour of tooltips but may introduce unwanted behaviour on any non-Pulsar javascript that relies on disabled elements remaining interactive |
Major changes
None in this release 🎉
Minor / patch changes
| Component | Issue | Details |
|---|---|---|
| General | #810 [patch] | Restore missing has-danger & has-error state classes |
| Documentation | #811 [patch] | Add code of conduct file to repository |
| Forms | #808 [patch] | Stop select elements needing two clicks to open in Firefox |
| #800 [patch] | Form field help text is now announced correctly by screen readers | |
| #805 [minor] | Stop mulltiple appended buttons from overlapping each other | |
| Main Navigation | #794 [patch] | Fix quaternary navigation width in IE9 |
| #805 [minor] | Close open popovers when opening the secondary navigation | |
| Tooltips | #796 [patch] | Fix issue causing tooltips to remain open when the mouse cursor was moved quickly off the element |
| Modals | #791 [minor] | Opening a modal will now focus the first available form input field within it |
| #802 | Modals have now proper accessibility attributes and can be navigated better with the keyboard | |
| Progress Bars | #792 [minor] | Addition of Stepped Progressbar component for use when the horizontal space is limited (like modals) |
7.0.8
This release improves the accessibility of the primary navigation helper and the way screen readers interact with the navigation elements as well as improvements to the sign-in panel and some other minor elements within the base layout. The navigation changes are quite comprehensive so we recommend reading through the notes on the #789 pull request to see what has changed.
The default colour of the sign-in panel and primary navigation has been darkened to maintain compliance with WCAG 2.0 colour contrast rules, because of the visual nature of this change it may be flagged/questioned by testing/QA teams, but should not be treated as a failure.
| Sign-in | Primary navigation |
|---|---|
 |
 |
Documentation styles have been updated to work better on small screen devices.
Minor changes / bugfixes
| Ref | Details |
|---|---|
| #789 | Accessibility overhaul of primary navigation |
| #785 | Increase contrast of sign in panel |
| Increase contrast of primary navigation | |
| Increase contrast of back to top link | |
| #788 | Move greeter brand image references to _config.branding.scss |
| #779 | New documentation styles |
| #784 | Moved default navigation colours into _config.theme.scss |
| #778 | Move signin variables into _config.variables.scss |
| #777 | Changed the way normalize.css is loaded to make it more compatible with sass |
| xxxx | Add hidden label to the add filter button within FilterBarComponent to prevent WCAG error |