There was little to no abstraction of styles to utility classesĪnother goal of the refactor was to make the off-canvas dialog easily themable through the use of CSS custom properties (aka CSS Variables) which can be easily overridden by a theme or module.The selectors used were frequently overly specific and non-functional.Not all elements were nested under the #drupal-off-canvas element. In addition to a barely functional CSS reset, the off-canvas dialog suffered from a complicated CSS API for those poor souls that go down the road of attempting to override its look and feel. Furthermore, focus styles were all over the place, which led to a host of WCAG accessibility violations. The reset was meant to prevent this from happening.Įxamples of bad usability and accessibility include the tabledrag widget and drop-buttons, which were borderline non-functional in many front-end themes (including Olivero). When that happened, it polluted the visual styles causing all types of usability and accessibility issues. This means that styles would (and frequently did) leak down from the parent theme info the off-canvas dialog. The off-canvas dialog is an administrative component that is typically nestled within a front-end page. More specifically, Drupal core’s commitment to support IE11.Ĭhief among the many problems to fix was a lack of a proper reset. Why refactor?Īs with most problems in life, the problems started with Internet Explorer. The off-canvas dialog slides out from the right to show options for Layout Builder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |