Debugging in CSS means figuring out what might be the problem when you have unexpected layout results. We’ll look...

The gem better_errors offers a detailed error page with an interactive REPL for better debugging. I had the issue...

Inspired by recent "git shortcut" cards I figured it would be nice to have one of these for rebasing a...

Event delegation is a pattern where a container element has a single event listener that handles events for all descendants...

Sometimes a link or input field has no visible label. E.g. a text field with a magnifying glass icon 🔎 and...

Besides their default styling properties, HTML elements have a semantic meaning. For example, an h1 tag is usually styled with...

Most browsers have built-in drag and drop support for different page elements like text and images. While this may...

git --fixup is very handy to amend a change to a previous commit. You can then autosquash your commits with...

Ruby lets you re-use existing RegExp objects by interpolating it into new patterns: locales_pattern = /de|en|fr|es/i...

The RSpec matcher tests if two HTML fragments are equivalent. Equivalency means: Whitespace is ignored Types of attribute quotes are...

We are using Spring in our tests for sequential test execution but not for parallel test execution. And Rails requires...

Bookmarks for directories will be most helpful if you are forced to work in deeply nested projects. Then it's...

With cd .. you can navigate one directory up from the one you are at now. If you use that a...

The tree command will show you the contents of a directory and all its sub directories as a tree:

There is an option you can set so that when using the cd command, small typos are automatically corrected. Add...

age is a simple, modern and secure file encryption tool, format, and Go library. It features small explicit keys, no...

Rails has the handy controller method send_file which lets us download files easily. We can decide whether the file...

It is generally discouraged to load your JavaScript by a tag in the : The reason is that a tag will pause the DOM parser until the script has loaded and executed. This will delay the browser's first contentful paint. A much better default is to load your scripts with a tag: A deferred script has many...

The attached compiler() function below applies JavaScript behavior to matching HTML elements as they enter the DOM. This works like...

Given you have a strict CSP that only allows elements from your own domain: Content-Security-Policy: script-src 'self' This will block JavaScript handlers inlined as attribute into your HTML elements. Clicking on the following link will only log an error with a strict CSP: click me click me Solution 1: Move the handler into your JavaScript The recommended solution is to move the handler from the HTML to the allowed JavaScript file that we loaded via . In the example above we could invent a new [data-alert] attribute with the alert message: click me Then our JavaScript intercepts clicks on elements with that attribute: document.addEventListener('click', function(event) { let link = event.target.closest('[data-alert]') if (link) { let message = link.dataset.alert alert(message) event.preventDefault() } }) Solution 2: Allow that one handler in your CSP Some browsers allow the CSP directive script-src-attr. This lets you allow the hashes of actual JavaScript code. The SHA256 hash of alert('hello') is vIsp2avtxDy0157AryO+jEJVpLdmka7PI7o7C4q5ABE= (in Base64). We can allow this one event handlers like this: Content-Security-Policy: script-src 'self'; script-src-attr 'unsafe-hashes' 'sha256-vIsp2avtxDy0157AryO+jEJVpLdmka7PI7o7C4q5ABE=' Note the sha256- prefix. This event handler now works when clicked: click me But any other script will still be blocked: click me Dealing with legacy browsers Currently (November 2023) about 75% of browsers support script-src-attr. Here is a forward-looking compromise that many users use with new CSP features: Have a liberal CSP with old directives supported by all browsers Make your CSP stricter with new, more specific directives for browsers that support it The CSP spec supports that approach in that using newer, more specific directives disable older, more general features. In our case this means: For old browsers, allow all inline scripts For new browsers, disallow inline scripts but allow inline handlers with given hashes Here is a CSP directive that works like this: Content-Security-Policy: script-src 'self' 'unsafe-inline'; script-src-elem 'self'; script-src-attr 'unsafe-hashes' 'sha256-vIsp2avtxDy0157AryO+jEJVpLdmka7PI7o7C4q5ABE=' Old browsers will only use script-src. New browsers will use script-src-elem (for tags) and script-src-attr (for inline event handlers), which override the more liberal rules from script-src.

Often people need links which are not linked directly, but should trigger execution of JavaScript. ❌ Bad workarounds

The linked article provides a description of commonly found problems with TLS and hints on debugging / solving them.

tl;dr: Avoid to memoize methods with default (keyword) arguments! When you are using Memoized with default arguments or default...