Author:
Source
Back in March I started to look at sponsors for the time I’m spending working on the Drupal core issue queue. It’s
been a few months and I wanted to go back on all the sponsored commits I made as a Frontend Framework Manager, to
show how the sponsorships helped Drupal for the past few months.
The sponsorship offer is simple: you send me a fixed monthly fee of 2500€, and I share the issue credit
of every Drupal core commit that I make. I’m very thankful to Palantir.net and OPTASY
who are sponsoring me. Thanks to them I was able to increase the amount of commits I can make to Drupal core. In the
last 3 months I committed 61 issues (worth 610 weighted issue credits) and the more sponsors I have,
the more time I can spend reviewing and committing issues.
- Differentiate visually dragging with and without hierarchy A nice improvement for editors working a lot with lists and trees
- Sticky table header is not sticky if –drupal-displace-offset-top is not defined
- [jQuery 4] ajax.js and jquery.form.js use deprecated function $.parseJSON() Preparing for the next release of jQuery 4 with some cleanup.
- cspell check is broken in commit-code-check.sh Sometimes we break the CI and it needs to be fixed 🤷
- CKEditor admin toolbar config buttons using ::before to add content: have invalid screen reader text It takes dedication to land those accessibility fixes, kudos to our accessibility contributors.
- Linking in CKEditor 5: URLs with top-level domain but without protocol should get a protocol added automatically
- #states disable property has stopped working for submit button and other elements Sometimes when we clean-up code, we clean too much and break some other parts of the code
- Setting width for sticky-header is broken
- Negotiate max width/height of oEmbed assets more intelligently
- States API doesn’t work with multiple select fields This was a a 13 years old issue! It _always_ feels good to close an issue that old.
- Add deprecation/bc support for library-overrides when files are moved Making sure backwards compatibility is working and useful
- Remove default event from collpased nav-tabs button
- [DrupalHtmlEngine] HTML-reserved characters (>, <, &) in <script> and <style> tag are converted to HTML entities It happens that we fix things for uses cases that stretch the reasonable (like having whole script tags in a WYSIWYG field)
- Olivero: Show content preview checkbox is not center aligned with the layout builder buttons. Even a minor issue of a misaligned text by a few pixels is worth fixing
- Drupal.theme.progressBar() does not escape output correctly
- filter_autop should ignore twig.config debug html comments Making sure Developer experience doesn’t impact regular users
- tablePositionSticky should not be called on a non-array variable
- CKEditor 5 table cell vertical align “middle” doesn’t work
- Move system/base component CSS to respective libraries where they exist A surprising performance improvement. There are still some low hanging fruits to improve the default frontend performance of Drupal
- Remove country setting from the installer When you don’t need a piece of data, just don’t collect it
- Media Library widget display doesn’t return to first page on applying filters
- Deprecate and remove the AJAX replace method That was a leftover D7 era deprecation
- Claro should use libraries-extend for views_ui.css Even in core it happens that we don’t use the right way to do something
- Removal :tabbable usage in dialog.js Some more jQuery 4 preparation
- Close icon is ovrlapping the title text in modal in claro Yes, typos can make it in the commit log
- Convert Olivero’s teaser into a single directory component Slowly but surely we’re adding Single directory components to Drupal core
- Refactor (if feasible) uses of the jQuery animate function to use Vanilla/native More CSS awesomeness making JavaScript code disapear
- [11.x] Update to jQuery 4.0.x beta Drupal staying on the bleading edge of frontend developement 🙂
- Refactor some uses of the jQuery parents function to use vanillaJS Did a small post earlier about this, CSS is really very good
- [regression] Uncaught TypeError: Cannot read properties of null (reading ‘style’) (toolbar.js)
- JSDoc for ajax command “changed” is incorrect There was a bunch of documentation fixes around this time
- menu_heading_id variable is not set in menu-region–footer.html.twig
- Add @file documentation to navigation.html.twig layout template
- Add @file documentation to menu-region–footer.html.twig template
- Views UI action buttons create janky layout shift on page load Polishing the loading of pages with heavy JS usage is important to show we care about UX
- Remove bottom radius on hover state of expanded sub menu item
- Setting empty URL when making embedded media a link in CKEditor5 causes JS errors
- Update color of submenu title text
- Collapsed nav-tabs status not exposed to screen reader There is a good number of accessibility fixes after this one, always nice to commit
- Incorrect padding on child menu items
- Claro: Form labels that are disabled have too low color contrast
- Claro should not hardcode decimal list style type for <ol>
- Some of string comparisons should use String.prototype.startsWith() or String.prototype.endsWith() Removing regular expressions as much as we can is a noble goal
- Location of “Skip to Main” link below admin toolbar in Claro is problematic for screen magnifier users
- Focus states on mobile second level navigation items can get cut off in Olivero
- Regression: Shortcuts menu flickers when the page is loaded Those toolbar flickering issues are tricky. Thankfully the new navigation module code is simpler than the existing Toolbar code, so it’s much much easier to deal with
- escapeAdmin.js functionality should be removed(it not used anymore) Removed the feature that removed the overlay… for now, escapeAdmin will be back one way or another)
- Navigation module offsets the Olivero skip link element
- Umami page.tpl.php breaks block placeholders Sometime themes can break really nice Drupal features (like bigpipe)
- Claro CSS for dropbutton items adds large gap of white space
- Replace dialogContentResize jQuery event with CustomEvent Those events issues are really exciting, we’re moving away slowly from jQuery for event management
- Umami views should use responsive grid Another case of core not using the awesome features we provide, not anymore 🙂
- Claro highlighted row not communicated to keyboard users
- Fix overflow visibility for wrapper content in navigation CSS
- Claro details component does not have the right class
- Make drupal.tableheader only use CSS for sticky table headers I will always welcome CSS-removing-JS patches
- Mismatch between implementation and description for Drupal.Message.prototype.remove().
- “Skip to main content” link skips over content that is essential to the page, banner role should be for global content
- Add pdureau as a co-maintainer for the Theme API with a focus on SDC Adding new maintainers is too rare. In this case the community is better for having him around
- Choose an icon for the Announcements link
- Remove deprecated moved_files entries in core
Many of these issues are maintenance focused, it’s not shiny, it’s not exciting, and it needs to be done.
Sponsoring big initiatives like Starshot is exciting, let’s not forget the unexciting day to day that keeps things
running. If you’re interested in supporting my work on Drupal core and keep the frontend fixes coming,
consider sponsoring me.