# background Published articles for background. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Релиз рабочего окружения GNOME 51 A Coruña DevFeed: [Релиз рабочего окружения GNOME 51 A Coruña]() Original publisher: [Read original article]() Author: denis-19 Published: 2026-09-17T08:31:45Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [input](), [Wayland](), [SVG](), [API]() Tags: [2026](), [background](), [capture](), [files](), [gnome](), [gnome-51](), [input](), [panel](), [settings](), [svg](), [tag-08a48a9394c3](), [tag-cb5ff012b3f0](), [wayland]() ### AI overview GNOME 51, codenamed A Coruña, was released on September 16, 2026. The release improves performance and settings, adds new GNOME Circle applications and elements, and introduces features including monitor brightness restoration, elogind support, a QR-code generation API, input capture portal support, improved screen recording, SVG-based cursors, and Wayland background effects. ### Source excerpt 16 сентября 2026 года состоялся релиз рабочего окружения GNOME 51 под кодовым названием A Coruña. В проекте оптимизирована производительность и настройки, добавлены новые элементы и приложения в GNOME Circle. Читать далее ## Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums DevFeed: [Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums]() Original publisher: [Read original article]() Author: depesz Published: 2026-04-15T18:05:36Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql clusters](), [async](), [IO]() Tags: [async](), [background](), [background-work](), [checksums](), [data-checksum](), [io](), [pg19](), [postgresql](), [uncategorized](), [vacuum](), [waiting]() ### AI overview This article examines a PostgreSQL 19 patch that allows data checksums to be enabled or disabled while a cluster is running. The command is immediate, but rewriting every table and index occurs in the background and can require substantial I/O. The article also discusses cost-delay options for controlling the background worker. ### Source excerpt On 3rd of April 2026, Daniel Gustafsson committed patch: Online enabling and disabling of data checksums This allows data checksums to be enabled, or disabled, in a running cluster without restricting access to the cluster during processing. Data checksums could prior to this only be enabled during initdb or when the cluster is ... Continue reading "Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums" ## Apply blur to iOS status bar in PWA DevFeed: [Apply blur to iOS status bar in PWA]() Original publisher: [Read original article]() Author: Stanko Published: 2025-04-11T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [PWA](), [CSS](), [iOS](), [Web Development]() Tags: [background](), [code](), [css](), [ios](), [pwa]() ### AI overview This tutorial describes a CSS-based workaround for applying a blurred overlay to the iOS status bar area in a standalone PWA. The workaround uses a fixed element positioned outside the viewport and backdrop filtering, but an August 2026 update states that it no longer works on recent iOS versions because of WebKit changes. ### Source excerpt Update August 2026: This workaround no longer works on recent iOS versions. WebKit changed how standalone PWAs handle the status bar area. The fixed overlay positioned outside the viewport no longer renders under the status bar. I haven't found a workaround for this yet. If you find a solution please let me know. On my current project, I'm making a Progressive Web App (PWA) and I was really annoyed that the status bar on iOS was completely transparentAlthough the option is called black-translucent. When the content scrolls behind it, it blends with the status bar elements, and it doesn't look great. I couldn't find a native solution, so I tried using CSS instead. To my surprise, my idea worked on the first try. Here is my solution next to the default iOS status bar: After applying the CSS solutionDefault If you are impatient, feel free to jump to the demo. The solution # I think the solution is pretty simple - a fixed div that covers the status bar area and applies a blur effect to the background. But there's a catch, the div needs to be positioned outside of the viewport. Here is the code, HTML first:
and the CSS: body { --bg-color: 186 230 253; background-color: rgb(var(--bg-color)); } .statusbar { position: fixed; left: 0; right: 0; top: -80px; height: 80px; overflow: hidden; z-index: 100; } .statusbar::before { content: ''; position: absolute; left: 0; right: 0; top: 0; height: 150%; -webkit-backdrop-filter: blur(8px); backdrop-filter: blur(8px); background-color: rgb(var(--bg-color) / 0.6); } The CSS can be even simpler - we can remove the ::before element and just apply the blur to the .statusbar element itself. But this gives a nicer, more natural blur effect - check Josh Comeau's blog post in which he explains it in detail. Demo # You can check the live demo, just remember that you'll need an iOS device to see the effect. Not just that - for the effect to be visible, you'll need to add the app to your home screen. If you don't w ## How to reliably update widgets on Android DevFeed: [How to reliably update widgets on Android]() Original publisher: [Read original article]() Published: 2022-02-12T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [Android](), [Jetpack](), [App]() Tags: [android](), [android-jetpack](), [background](), [battery](), [implementation](), [setup](), [widget](), [workmanager]() ### AI overview This tutorial explains why Android widgets may not update reliably using android:updatePeriodMillis alone, particularly on devices whose vendors restrict background processing. It presents Android Jetpack WorkManager as a way to schedule periodic work that updates widget instances through AppWidgetManager. ### Source excerpt The default solution with android:updatePeriodMillis doesn't always work. ## Controlling TextView MinWidth DevFeed: [Controlling TextView MinWidth]() Original publisher: [Read original article]() Published: 2021-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Android](), [constraintlayout](), [Code]() Tags: [android](), [android-layout](), [background](), [constraintlayout](), [gravity](), [layout](), [properties](), [textview](), [xml]() ### AI overview A technical explanation of how Android TextView minimum-width APIs interact. Setting minWidth or minimumWidth alone may not reset a dimension declared in XML; both properties must be cleared, and a background can still impose a minimum width. ### Source excerpt Introduction Sometimes we might need our TextView with wrap_content width to occupy more space than it will based on amount of characters it displays. For that we can set minimum width. Usually, we do that via XML like this: Having setup like this we ensure that our TextView will occupy a minimum of 200dp. Also, we can control minimum width programmatically via: TextView#setMinWidth. But controlling minimum width programmatically has one caveat that I'd like to describe below. ## GSoC NTFS 2017 Update 6 DevFeed: [GSoC NTFS 2017 Update 6]() Original publisher: [Read original article]() Published: 2017-07-24T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Code](), [file](), [Operating system]() Tags: [background](), [code](), [files](), [free](), [gsoc](), [make](), [open-source](), [os](), [react](), [reactos](), [technical](), [win32](), [winapi]() ### AI overview A GSoC NTFS update for ReactOS describes implementing code to write a B-Tree node to disk, allowing the driver to create dozens of files until an index node fills. The article also explains how NTFS stores directory indexes and file metadata. ### Source excerpt Hello again! :) Last week, I finished the code that writes a B-Tree node to disk. Specifically, it lets me write the node to an index buffer within the index allocation of the parent directory. Don't worry if that doesn't make sense, I'll explain it more below. From a user's perspective, this means that the driver now has the ability to create dozens of files. My tester will create 39 files before filling the index node. ## Styling the Shadow DOM: Encapsulation, Host Styling, and Style Boundaries DevFeed: [Styling the Shadow DOM: Encapsulation, Host Styling, and Style Boundaries]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2015-09-29T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [Document Object Model (DOM)](), [CSS](), [Web Development]() Tags: [background](), [change](), [color](), [css](), [input]() ### AI overview This article explains how the Shadow DOM encapsulates the implementation and styles of custom elements, preventing styles from leaking in or out. It also describes styling the host element while keeping the element's internal implementation isolated. ### Source excerpt One of the beefs (and there aren't many) that I have with CSS is that it has a very weak opinion about style encapsulation. That opinion is basically "well, name your classes well" or else bad things happen. Know this: I come from C++, land of rules and disappointed compilers; this hand waviness drives me crazy. This matters because now you have to trust the people that write your css libraries to have common sense. If my website needs two kinds of fancy buttons, which live in shiny-button.css and bouncy-button.css, which are both libraries written by silly people who want me to use the .button class to get their style, I'm hosed. Enter the Shadow DOM The Shadow DOM fixes this problem by building a little castle (a dome, get it?) around each custom element, locking in its implementation and styles. This is a proper castle, with a proper moat, so now styles can't get in and out of it. This means that if was a custom element instead of a pile of CSS, its .button class was scoped to the element itself, and wouldn't stomp over 's similarly creatively named .button class. This shouldn't surprise you too much, as native elements have been doing this in secret for yeaaaaars. styles the date picker somehow, but you've never worried what class names it might use to do so. You know why? Because you can't get to its castle, that's why. The struggle is real So what happens if you do want to style ? What if it's a perfectly respectable button, but it uses Helvetica as its font and you really need it to be Comic Sans because Helvetica is so 2014? You can always style the host of the element. Think of the host as the castle walls; it's the thing that holds all the actual contents of the custom element. It still plays by CSS rules, so some of the styles you set on the host could actually trickle down to some child elements. For example: shiny-button { color: white; background-color: tomato; border-radius: 3px; width: 400 ## Introducing the ReactOS project blog DevFeed: [Introducing the ReactOS project blog]() Original publisher: [Read original article]() Published: 2013-04-29T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development]() Tags: [background](), [blog](), [developers](), [free](), [introduction](), [open-source](), [os](), [react](), [reactos](), [win32](), [winapi]() ### AI overview A ReactOS community member introduces himself, outlines his background and roles in the project, and explains the purpose of the new blog as an informal platform for developers and team members to share their work and experiences. ### Source excerpt Despite my involvement with the project for several years, I do not believe I have ever actually introduced myself. While the developers and a few other members of the community know about me, in general the rest of the community knows me as the guy that writes the newsletters and sometimes posts snarky comments on the forum whenever I see something that I think is a bad idea. As such, this might be a good time to introduce myself and provide some background.