Category: News

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.

1. Differentiate visually dragging with and without hierarchy A nice improvement for editors working a lot with lists and trees
2. Sticky table header is not sticky if –drupal-displace-offset-top is not defined
3. [jQuery 4] ajax.js and jquery.form.js use deprecated function $.parseJSON() Preparing for the next release of jQuery 4 with some cleanup.
4. cspell check is broken in commit-code-check.sh Sometimes we break the CI and it needs to be fixed 🤷
5. 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.
6. Linking in CKEditor 5: URLs with top-level domain but without protocol should get a protocol added automatically
7. #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
8. Setting width for sticky-header is broken
9. Negotiate max width/height of oEmbed assets more intelligently
10. 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.
11. Add deprecation/bc support for library-overrides when files are moved Making sure backwards compatibility is working and useful
12. Remove default event from collpased nav-tabs button
13. [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)
14. 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
15. Drupal.theme.progressBar() does not escape output correctly
16. filter_autop should ignore twig.config debug html comments Making sure Developer experience doesn’t impact regular users
17. tablePositionSticky should not be called on a non-array variable
18. CKEditor 5 table cell vertical align “middle” doesn’t work
19. 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
20. Remove country setting from the installer When you don’t need a piece of data, just don’t collect it
21. Media Library widget display doesn’t return to first page on applying filters
22. Deprecate and remove the AJAX replace method That was a leftover D7 era deprecation
23. 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
24. Removal :tabbable usage in dialog.js Some more jQuery 4 preparation
25. Close icon is ovrlapping the title text in modal in claro Yes, typos can make it in the commit log
26. Convert Olivero’s teaser into a single directory component Slowly but surely we’re adding Single directory components to Drupal core
27. Refactor (if feasible) uses of the jQuery animate function to use Vanilla/native More CSS awesomeness making JavaScript code disapear
28. [11.x] Update to jQuery 4.0.x beta Drupal staying on the bleading edge of frontend developement 🙂
29. Refactor some uses of the jQuery parents function to use vanillaJS Did a small post earlier about this, CSS is really very good
30. [regression] Uncaught TypeError: Cannot read properties of null (reading ‘style’) (toolbar.js)
31. JSDoc for ajax command “changed” is incorrect There was a bunch of documentation fixes around this time
32. menu_heading_id variable is not set in menu-region–footer.html.twig
33. Add @file documentation to navigation.html.twig layout template
34. Add @file documentation to menu-region–footer.html.twig template
35. 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
36. Remove bottom radius on hover state of expanded sub menu item
37. Setting empty URL when making embedded media a link in CKEditor5 causes JS errors
38. Update color of submenu title text
39. Collapsed nav-tabs status not exposed to screen reader There is a good number of accessibility fixes after this one, always nice to commit
40. Incorrect padding on child menu items
41. Claro: Form labels that are disabled have too low color contrast
42. Claro should not hardcode decimal list style type for <ol>
43. 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
44. Location of “Skip to Main” link below admin toolbar in Claro is problematic for screen magnifier users
45. Focus states on mobile second level navigation items can get cut off in Olivero
46. 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
47. 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)
48. Navigation module offsets the Olivero skip link element
49. Umami page.tpl.php breaks block placeholders Sometime themes can break really nice Drupal features (like bigpipe)
50. Claro CSS for dropbutton items adds large gap of white space
51. Replace dialogContentResize jQuery event with CustomEvent Those events issues are really exciting, we’re moving away slowly from jQuery for event management
52. Umami views should use responsive grid Another case of core not using the awesome features we provide, not anymore 🙂
53. Claro highlighted row not communicated to keyboard users
54. Fix overflow visibility for wrapper content in navigation CSS
55. Claro details component does not have the right class
56. Make drupal.tableheader only use CSS for sticky table headers I will always welcome CSS-removing-JS patches
57. Mismatch between implementation and description for Drupal.Message.prototype.remove().
58. “Skip to main content” link skips over content that is essential to the page, banner role should be for global content
59. 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
60. Choose an icon for the Announcements link
61. 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.

In the first part of a two-part series, we’ll introduce how to set up DigitalOcean and AppSignal for a Ruby on Rails application: https://blog.appsignal.com/2024/05/29/getting-started-your-ruby-on-rails-app-hosted-on-digitalocean-with-appsignal.html

Ruby 3.3.2 has been released.

This release includes many bug-fixes.
See the GitHub releases for further details.

Download

• https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.2.tar.gz

  SIZE: 22095824
  SHA1: b49719ef383c581008c1fd3b68690f874f78557b
  SHA256: 3be1d100ebf2a0ce60c2cd8d22cd9db4d64b3e04a1943be2c4ff7b520f2bcb5b
  SHA512: a15ba8d6c2830fcd1f2b36f671acf9028c303ec78608fd268da0585db8e95ddd971666e8029bcfa2584da2184a6534e1f2f2da07fa7ca4494e8d842eed206f00
  

• https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.2.tar.xz

  SIZE: 16349500
  SHA1: 5c9f7d5cf55d9e45b24c613014cbe2b605de009d
  SHA256: b5e8a8ed4a47cdd9a3358b5bdd998c37bd9e971ca63766a37d5ae5933fdb69f1
  SHA512: 70dd8eb933956f894c52a8ede42e8ee74ff0e062bd8134a0bfb6bffc83a2848a658b62c8df5530b4dd64087b2d5373909c48917528facb1e6f4e99e79b6ad449
  

• https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.2.zip

  SIZE: 26981906
  SHA1: ee641ef4a0c5b9d12456c565d402841ae2ec5ab2
  SHA256: 06bf1aa3336afed66e2f89b0be3542c980fcdd76ffad0be284a860f25edea5b1
  SHA512: e2bbff1fbe5d9a892bd9c21fe9f10ea7b23f111f3876538bffea3d5451645e155f9ddc61345a44e409d44f83e190ffe30b9c90cd75905dc079cf8803f2f8ccdf
  

Release Comment

Many committers, developers, and users who provided bug reports helped us make this release.
Thanks for their contributions.

Posted by k0kubun on 30 May 2024

Google is killing off a messaging service! This one is the odd “Google Business Messaging” service—basically an instant messaging client that is built into Google Maps. If you looked up a participating business in Google Maps or Google Search on a phone, the main row of buttons in the place card would read something like “Call,” “Chat,” “Directions,” and “Website.” That “Chat” button is the service we’re talking about. It would launch a full messaging interface inside the Google Maps app, and businesses were expected to use it for customer service purposes. Google’s deeply dysfunctional messaging strategy might lead people to joke about a theoretical “Google Maps Messaging” service, but it already exists and has existed for years, and now it’s being shut down. ↫ Ron Amadeo at Ars Technica When it comes to Google, it’s often hard to distinguish meme from reality.

A year into the job, David Risher talks innovation at Lyft, plus lessons learned from the recent earnings error.

In questo video, vi mostrerò come regolare la luminosità di una lampadina a bassa potenza (12V) utilizzando un transistor NPN 2N2222 e un Arduino. Questo progetto è ideale per chi vuole imparare a controllare la potenza fornita a un carico variabile utilizzando un transistor e il controllo PWM (Pulse Width Modulation) di Arduino.

Cosa Imparerai:
Componenti Necessari:

Arduino (qualsiasi modello)
Transistor NPN 2N2222
Lampadina a 12V
Resistenze (per limitare la corrente)
Breadboard e cavi di collegamento
Alimentatore 12V (o batteria)

Principio di Funzionamento:

Come funziona un transistor NPN
Concetti di base del controllo PWM per regolare la luminosità
Connessioni Elettriche:

Schema di collegamento tra Arduino, transistor 2N2222, e lampadina
Come collegare correttamente il transistor per gestire la potenza della lampadina
Codice Arduino:

Scrivere il codice per generare segnali PWM con Arduino
Esempi di codice per variare la luminosità della lampadina tramite un potenziometro o comandi digitali
Test del Progetto:

Come caricare il codice sull’Arduino
Verifica del funzionamento del sistema: dimostrazione della regolazione della luminosità della lampadina

Avvertenza:
Assicurati di seguire tutte le precauzioni necessarie quando lavori con l’elettronica per evitare danni ai componenti o a te stesso.

Se questo video ti è stato utile, non dimenticare di lasciare un like, condividere e iscriverti al canale per altri progetti interessanti! Buona visione!