We use foreman to start all necessary processes for an application, which are declared in a Procfile. This is very...
Building application assets with esbuild is the new way to do it, and it's great, especially in combination with...
Attaching files to a field that is handled by Carrierwave uploaders (or maybe any other attachment solution for Rails) in...
When Capybara locates elements in the DOM, by default it allows only accessing visible elements -- when you are using a...
RSpec Rails can automatically mix in different behaviors to your tests based on their type tag, for example enabling you...
You can use RSpec::Matchers.define_negated_matcher to define a negated version of an existing matcher. This is particularly useful...
Jasmine has spyOnProperty(), but it only works if the property is implemented using getter and setter functions. This is a...
TL;DR When using Cache-Control on a Rails application, make sure the Vary: Accept header is set.
ImageMagick can convert SVGs to raster image formats. Example for PNG: convert input.svg output.png If the SVG has a...
The Interactive Advertising Bureau (IAB) is a European marketing association which has introduced a standard how advertising can be served...
Some users might use Adblock Plus or similar browser plugins to reduce the number of ads displayed. If you run...
Jasmine is a great way to unit test your JavaScript components without writing an expensive end-to-end test for...
A flaky test is a test that is often green, but sometimes red. It may only fail on some PCs...
Within development and test environments, Rails is usually configured to show a detailed debug page instead of 404s. However, there...
You can configure VCR to automatically record/replay cassettes for any RSpec example tagged as :vcr or vcr: true.
RSpec is smart when using the include-matcher in combination with .not_to. One could assume that .not_to include...
You want to use fields in your applications. However, your desktop users may encounter some weird quirks: Aside from allowing...
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...
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...
The RSpec matcher tests if two HTML fragments are equivalent. Equivalency means: Whitespace is ignored Types of attribute quotes are...
Rails has the handy controller method send_file which lets us download files easily. We can decide whether the file...
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.