# dialog The HTML dialog element is an interactive element defined in the HTML Standard. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Dialog Can Now Be a Native Desktop Window DevFeed: [A Dialog Can Now Be a Native Desktop Window]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-05T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [dialog](), [Accessibility](), [Operating system](), [macOS]() Tags: [accessibility](), [bug](), [can](), [code](), [component](), [desktop](), [dialog](), [keyboard](), [macos](), [native](), [release]() ### AI overview Codename One adds an option for dialogs to open as native modal desktop windows while retaining lightweight in-window dialogs. The release also fixes top-level window ownership and updates focus, input routing, repainting, popup behavior, and accessibility handling across separate windows. ### Source excerpt Codename One dialogs can stay inside a secondary window or become native modal windows, while sheets, popups, overlays, tooltips, HTML, and accessibility now resolve the correct top level. ## Using and Styling the Dialog Element DevFeed: [Using and Styling the Dialog Element]() Original publisher: [Read original article]() Author: Geoff Graham Published: 2026-08-07T14:06:43Z Content type: tutorial Language: en Sources: [CSS-Tricks]() Topics: [dialog](), [HTML](), [JavaScript](), [Web Development]() Tags: [architecture](), [articles](), [articles-guides](), [dialog](), [guides](), [html](), [html-elements](), [javascript](), [web]() ### AI overview A practical guide to using the native HTML element, covering basic markup, opening dialogs with JavaScript, modal behavior, backdrops, focus, closing methods, declarative HTML approaches, and experimental invoker commands. ### Source excerpt There's a lot of nuance to the element, a seemingly little piece of web architecture. I've got some notes from digging into it. Using and Styling the Dialog Element originally handwritten and published with love on CSS-Tricks. You should really get the newsletter as well. ## Give your site the Cmd+K menu users expect DevFeed: [Give your site the Cmd+K menu users expect]() Original publisher: [Read original article]() Author: Marko Published: 2026-08-01T10:15:27Z Content type: tutorial Language: en Sources: [Marko Denic Tech]() Topics: [dialog](), [Code](), [coding](), [browser](), [Chrome](), [Firefox]() Tags: [blog-for-developers](), [browser](), [build-faster](), [chrome](), [code](), [code-productivity](), [code-smarter](), [coding](), [content-monetization](), [css](), [css-animation](), [css-performance](), [developer-growth](), [developer-resources](), [dialog](), [email-newsletter-for-coders](), [firefox](), [front-end-development](), [github](), [github-profile-automation](), [html](), [html-tips](), [javascript](), [javascript-tricks](), [learn-to-code](), [responsive-design-tips](), [ui](), [web-dev-newsletter](), [web-development](), [web-development-tips](), [weekly-dev-tips](), [workflow-optimization]() ### AI overview This tutorial explains how to build a dependency-free Cmd+K command palette for a multi-page website using the dialog element, a keydown listener, and a text filter. It covers keyboard handling across Mac and Windows, browser-specific behavior, modal focus and scrolling, and use cases such as admin panels and documentation sites. ### Source excerpt Linear and GitHub both have it. Build the same command palette with the dialog element, one keydown listener, and a filter. No libraries. ## 2026.6: Pick a card, any card DevFeed: [2026.6: Pick a card, any card]() Original publisher: [Read original article]() Author: Franck Nijhof Published: 2026-06-03T00:00:00Z Content type: release Language: en Sources: [Home Assistant]() Topics: [Home Assistant](), [dashboards](), [Automation](), [dialog](), [Matter]() Tags: [2026](), [apps](), [automation](), [core](), [custom-dashboard](), [dialog](), [features](), [integrations](), [matter](), [release](), [release-notes]() ### AI overview Home Assistant 2026.6 introduces a new card picker that recommends dashboard cards based on the device or entity users want to display, with live previews using their data. The release also adds zone triggers and conditions, live condition-test indicators, target counts, step notes, new tile card features, improved smart-lock support, a friendlier Apps page, and additional community integrations. ### Source excerpt Home Assistant 2026.6! 🎉 I'm going to put my hand up right away: ✋ I am not a dashboard person. Not because I don't like them; I love seeing what you all build. But designing a beautiful one is a kind of visual creativity I just don't have. That's a big part of why I love the built-in Home dashboard so much, it does the designing for me. But when I do build a custom dashboard, I usually stare at that "add a card" dialog for way too long, picking cards almost at random just to see if they look good with the data I have. So you can imagine my excitement for my personal favorite of this release: the new card picker. Instead of asking "which card type do I want?", it now asks "which thing in your home do you want to show?", and then suggests cards that actually make sense for it, with live previews using your own data. For someone like me, that's not just easier; it's genuinely inspiring. It nudges me towards combinations I would not have thought of on my own. 💡 This fits into a bigger direction I keep getting more excited about: Home Assistant getting better at starting from the thing you want to do, instead of asking you to first learn the building blocks. The same idea is what makes purpose-specific triggers and conditions in Home Assistant Labs feel so right, and this release brings them a big step closer to graduating out of Labs with brand new zone triggers and conditions. 📍 A close second favorite for me this release is everything happening around that in the automation editor: live test indicators on your conditions, target counts on every device, area, floor, and label, and proper notes you can attach to any step. Individually they are small quality-of-life touches; together, they make building automations feel a whole lot more transparent. ✨ And there is plenty more to love in this release: new tile card features, Z-Wave smart locks catching up with their Matter siblings, a friendlier Apps page, and another big batch of new integrations from our community. 🚀 E ## QuickQWERTY 1.2.3 DevFeed: [QuickQWERTY 1.2.3]() Original publisher: [Read original article]() Published: 2026-05-03T00:00:00Z Content type: release Language: en Sources: [Susam Pal]() Topics: [browser](), [bug](), [dialog](), [Code](), [GitHub]() Tags: [browser](), [bug](), [bug-fixes](), [code](), [dialog](), [github](), [release](), [update](), [web](), [website]() ### AI overview QuickQWERTY 1.2.3 is a release of the browser-based touch typing tutor. It fixes an incorrectly updated licence link and removes an unnecessary dialog that appeared when selecting the already active number-key split. ### Source excerpt QuickQWERTY 1.2.3 is now available. QuickQWERTY is a web-based touch typing tutor for QWERTY keyboards that runs directly in the browser. This release includes two small bug fixes. In the previous release, QuickQWERTY source code management moved from GitHub to Codeberg. During that update, the licence link in the footer was updated incorrectly. The broken licence link has now been fixed. Further, there was a minor bug that caused a redundant dialog box to appear while switching between 6-7 split and 5-6 split. Units 16 to 20 contain two links labeled '6-7 split' and '5-6 split' which allow you to select how you want to split the number keys between left and right hands. Clicking either of those links brings up a dialog that explains what the two splits mean and prompts you to confirm in order to make the switch. Say, the '6-7 split' was already the chosen split. Clicking the '6-7 split' label triggered the dialog box unnecessarily. A dialog was unnecessary in that case since if you were already on the '6-7 split', clicking the '6-7 split' label resulted in no switch. This unnecessary dialog has now been eliminated. To try out QuickQWERTY, please visit quickqwerty.html. The source code of QuickQWERTY is available under the terms of the MIT licence at codeberg.org/susam/quickqwerty. Read on website | #web | #programming ## Interop 2026: Continuing to improve the web for developers DevFeed: [Interop 2026: Continuing to improve the web for developers]() Original publisher: [Read original article]() Author: Rachel Andrew GitHub LinkedIn Mastodon Bluesky Homepage Published: 2026-02-12T08:00:00Z Content type: article Language: en Sources: [web.dev: Blog]() Topics: [Web platform](), [interoperability](), [web-standards](), [CSS](), [dialog](), [view transitions](), [browsers](), [dashboards]() Tags: [browsers](), [css](), [developers](), [dialog](), [interop](), [interoperability](), [view-transitions](), [web](), [web-platform]() ### AI overview Interop 2026 is an effort by browser-engine contributors to improve web-platform interoperability. It focuses on high-priority issues for web developers and users, including anchor positioning, container style queries, dialogs and popovers, scroll-driven animations, and view transitions. ### Source excerpt Learn about the features included in Interop 2026. ## and popover: Baseline layered UI patterns DevFeed: [and popover: Baseline layered UI patterns]() Original publisher: [Read original article]() Author: David A Herron Homepage Published: 2025-11-25T08:00:00Z Content type: article Language: en Sources: [web.dev: Articles]() Topics: [dialog](), [aria](), [browsers](), [Web](), [web applications](), [modern web development](), [JavaScript]() Tags: [aria](), [article](), [browsers](), [dialog](), [how-to](), [javascript](), [modal](), [ui](), [user-experience](), [user-interface](), [web-applications]() ### AI overview This article explains how to build modal and popover UI patterns with features built into modern web browsers. It demonstrates a sign-up modal that appears when a user tries to save an image to a favorites list without being logged in, and discusses the accessibility behavior required for modal dialogs. ### Source excerpt Learn how to build UI patterns for modal windows and prompts using the and popover web features. ## Vanilla JavaScript support for Tailwind Plus DevFeed: [Vanilla JavaScript support for Tailwind Plus]() Original publisher: [Read original article]() Published: 2025-07-25T14:30:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [Vanilla JavaScript](), [ui](), [JavaScript](), [HTML](), [aria](), [dialog](), [cross-platform](), [Web platform]() Tags: [aria](), [component](), [cross-platform](), [dialog](), [framework](), [html](), [javascript](), [tailwind](), [ui]() ### AI overview Tailwind Plus now provides fully functional, accessible, and interactive UI blocks for projects that do not use React or Vue. Its new Elements library offers headless custom elements for building interactive interfaces with HTML, utility classes, or custom CSS. ### Source excerpt Every UI block in Tailwind Plus is now fully functional, accessible, and interactive, even if you don't use a framework like React or Vue. ## Headless UI v2.1: Simplified transition API and improved multi-dialog support DevFeed: [Headless UI v2.1: Simplified transition API and improved multi-dialog support]() Original publisher: [Read original article]() Published: 2024-06-21T15:00:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [React](), [dialog](), [React UI animations]() Tags: [compatibility](), [components](), [dialog](), [documentation](), [install](), [react]() ### AI overview Headless UI v2.1 for React simplifies transition APIs with a new prop and data attributes for transition stages. It also supports rendering multiple sibling dialogs, with the most recently opened dialog closing on Escape or outside clicks. ### Source excerpt We just released Headless UI v2.1 for React, which dramatically simplifies our transition APIs and adds support for rendering multiple dialogs as siblings. We've made transitions way easier in v2.1 by adding a new prop to all of the built-in components you might want to transition, and adding data attributes for each transition stage so you can add transition styles by just throwing some classes on the target element: There are four data attributes you can use to target the different stages of... ## Custom Dialog Animation in Jetpack Compose DevFeed: [Custom Dialog Animation in Jetpack Compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2023-10-17T04:42:08Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [dialog](), [Code]() Tags: [animation](), [article](), [code](), [compose](), [compose-animation](), [dialog](), [jetpack-compose]() ### AI overview A tutorial on creating custom dialog animations in Jetpack Compose. It explains how to build a dialog, remove the default window animation and scrim, and use custom animation logic, including AnimatedVisibility, to control showing and dismissing the dialog. ### Source excerpt Create custom dialog animations using Jetpack Compose animation composables such as AnimatedVisibility ## Zed Plans to Open Source Its Code Through Collaborative Coding Channels DevFeed: [Zed Plans to Open Source Its Code Through Collaborative Coding Channels]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2023-06-14T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Open Source](), [dialog](), [Code]() Tags: [chat](), [contribute](), [dialog](), [open-source](), [workflows]() ### AI overview Zed's remote team describes a plan to open source Zed through the Zed platform. The initial phase involves public coding channels for watching, listening to, and discussing development, followed by persistent code annotations and async contributions. ### Source excerpt Our plan for open-sourcing Zed on Zed, starting with synchronous conversations in the #zed channel. ## Dialogs in Jetpack Compose: Types and Usage DevFeed: [Dialogs in Jetpack Compose: Types and Usage]() Original publisher: [Read original article]() Author: Alex Styl Published: 2023-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [dialog](), [Jetpack Compose](), [ui]() Tags: [dialog](), [how-to](), [jetpack-compose](), [tutorial](), [ui]() ### AI overview A tutorial on dialogs in Jetpack Compose, covering how dialogs differ from AlertDialogs, the available dialog variants, visibility state, custom layouts, shapes, and colors. ### Source excerpt Dialogs, AlertDialogs and DIYDialogs. ## Headless UI v1.6, Tailwind UI team management, Tailwind Play improvements, and more DevFeed: [Headless UI v1.6, Tailwind UI team management, Tailwind Play improvements, and more]() Original publisher: [Read original article]() Published: 2022-05-27T15:00:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [React](), [Vue.js](), [dialog](), [Remix]() Tags: [css](), [dialog](), [react](), [release-notes](), [remix](), [tailwind](), [ui](), [update](), [v1](), [vue]() ### AI overview The article announces Headless UI v1.6 and describes new features for React and Vue components, including multiple selection, clearing combobox values, hidden inputs for form submission, object serialization, and improvements to dialog scrolling and outside-click behavior. ### Source excerpt It's been a while since I've written about what we've been working on so I have a lot to share! Too much honestly -- so put your swim suit on, sit back in your lounge chair, and prepare to soak up some vitamin CSS. ## Better permissions on Android DevFeed: [Better permissions on Android]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2020-03-08T14:41:21Z Content type: tutorial Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Android](), [Authorization](), [Kotlin](), [App](), [Code](), [dialog]() Tags: [android](), [android-permission-tutorial](), [android-permission-using-kotlin](), [android-permissions](), [best-practices](), [dialog](), [kotlin](), [manifest](), [permission-rationale-dialog-on-android](), [permissions](), [runtime-permissions-on-android](), [user-deny-permission-android]() ### AI overview A Kotlin Android tutorial explains how to handle denied permissions by using shouldShowRequestPermissionRationale to display a rationale dialog before requesting permission again. The example uses READ_CONTACTS and covers manifest declaration, permission checks, dialog display, and result handling. ### Source excerpt Gracefully handle permission denial on Android permission dialogs and leverage permission rational dialogs to enhance the user experience of your application. ## New Sheet Positioning DevFeed: [New Sheet Positioning]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2020-02-27T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [dialog](), [Mobile]() Tags: [desktop](), [dialog](), [mobile](), [navigation](), [screen](), [update]() ### AI overview Codename One's Sheet component now supports positioning along the north, east, west, south, or center of the screen, with different positions configurable for tablets and desktop versus phones. ### Source excerpt Not so long ago, we released a Sheet component that acts like a non-modal dialog box that slides up from the bottom. It occupies only the amount of space required to house its contents, and it provides built-in navigation controls to go "back" to the previous sheet. By default Sheets are displayed along the bottom of the screen, but we have recently added an update that allows you to position it along the north, east, west, south, or center of the screen, as shown below: ## Picking a Dialog Type DevFeed: [Picking a Dialog Type]() Original publisher: [Read original article]() Author: Shai Almog Published: 2020-01-09T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [dialog](), [ui]() Tags: [developers](), [dialog](), [layout](), [ui]() ### AI overview This tutorial explains the differences between Codename One's Dialog and InteractionDialog, including modality, event handling, layout behavior, text-field and virtual-keyboard issues, and when to use each type. ### Source excerpt The duality of InteractionDialog and Dialog is often confusing to the Codename One newcomer (and to some degree to veteran developers too). This is in part due to the multiple behavior differences that extend far beyond the "official" functionality difference. This has its roots in history that predated Codename One. In this post I'll try to clarify the process of picking the "right one" and the tradeoffs involved. ## Icon Fonts, Popups and Infinite Scroll DevFeed: [Icon Fonts, Popups and Infinite Scroll]() Original publisher: [Read original article]() Author: Shai Almog Published: 2019-09-06T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Icon font](), [dialog](), [infinite scroll]() Tags: [api](), [dialog](), [fonts](), [icons](), [integration]() ### AI overview This partial Codename One update describes easier arbitrary icon-font integration, updated material font constants, and a graphics-based popup arrow API with improved customization and cross-platform behavior. It also introduces infinite-scroll changes, although the supplied text is incomplete. ### Source excerpt As I mentioned in the last post there are a lot of new features we need to go over and it will take time to cover everything. In fact this is still a partial list and there's a lot more on the way... Easier Icon Font Integration First off Thomas submitted a PR for a few new font icon methods: Specifically in Label he added: public void setFontIcon(Font font, char c); public void setFontIcon(Font font, char c, float size); And in FontImage he added: ## Hands-on with Material Components for Android: Dialogs DevFeed: [Hands-on with Material Components for Android: Dialogs]() Original publisher: [Read original article]() Author: Nick Rout Published: 2019-07-29T14:00:13Z Content type: tutorial Language: en Sources: [Stories by Nick Rout on Medium]() Topics: [dialog](), [Android](), [material-components](), [Material Design](), [Gradle]() Tags: [android](), [android-app-development](), [dialog](), [gradle](), [material-components](), [material-design](), [material-theming]() ### AI overview A practical guide to Material Components for Android dialogs. It explains alert, simple, confirmation, and full-screen dialog types, their shared characteristics, basic implementation with MaterialAlertDialogBuilder, configuration-change behavior, and customization options. ### Source excerpt Part 7 of a series covering practical usage of Material Components for Android This post will be covering the features and API of Dialog components. To find out how to handle initial setup of Material Components for Android (including the Gradle dependency and creating an app theme), please see my original post: Setting up a Material Components theme for Android Dialogs are components, typically with modal windows, that are displayed in front of app content. They are used to inform users about a task that may contain critical information and/or require a decision. They purposefully interrupt the current flow and remain on screen until dismissed or action has been taken, so they should be used sparingly. From a design perspective, there are three main types of dialogs which can be used in different scenarios: Alert dialog: The simplest of dialogs, despite the name. Used to interrupt a user with urgent information that typically requires user action/confirmation. Characterized by a title, optional supporting text and action buttons. Simple dialog: Used to present the user with a list of actions that, when tapped, take immediate effect. Should not contain action buttons. Confirmation dialog: Used to present a list of single- or multi-select choices to a user. Action buttons serve to confirm the choice(s). All of the above share common characteristics: a background scrim that obscures app content (which can be optionally tapped to dismiss the dialog) and a surface container. Note: A fourth type exists: Full screen dialog. To implement this, the official documentation recommends using a DialogFragment along with resource qualifiers to determine how it is presented. This is outside the scope of this article and won't be covered. Basic usage 🏁 All of the aforementioned dialog types can be implemented using MaterialAlertDialogBuilder. This builder class configures and instantiates an AlertDialog with Material Design specifications and theming. The basic method of showing a ## RAPPS Enchancements: GSoC 2017 Edition Volume 3 and 4 DevFeed: [RAPPS Enchancements: GSoC 2017 Edition Volume 3 and 4]() Original publisher: [Read original article]() Published: 2017-07-21T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [App](), [dialog](), [C++]() Tags: [2017](), [app](), [bug](), [c-plus-plus](), [dialog](), [download](), [free](), [gsoc](), [improvements](), [open-source](), [os](), [queue](), [react](), [reactos](), [screenshots](), [translation](), [win32](), [winapi]() ### AI overview A GSoC 2017 progress update for ReactOS's RAPPS application manager. The update describes a modeless download dialog, simultaneous app downloads, translation and license information, multi-selection for batch installation, a flicker bug fix, and ongoing conversion of RAPPS code to C++. ### Source excerpt Whoosh! Two weeks flew by in no time! Fortunately, I've done many things and have some screenshots to show! Before we start, I have an anouncement: I'm going to Hackfest and FroSCon this August! I may not be very useful there, but I can discuss things related to the project, meet my mentor Mark Jansen and other devs. I will also learn from the ReactOS developers and FrOSCon workshops. ## GSOC Project TSE Week 4 DevFeed: [GSOC Project TSE Week 4]() Original publisher: [Read original article]() Published: 2017-06-29T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [Toolbar](), [browser](), [file](), [navigation](), [Icons](), [ui](), [dialog](), [Shell]() Tags: [browser](), [dialog](), [enumeration](), [file](), [free](), [gsoc](), [icons](), [implement](), [interface](), [navigation](), [open-source](), [os](), [project](), [react](), [reactos](), [toolbar](), [ui](), [win32](), [winapi]() ### AI overview A week-four GSoC progress report describes a working prototype of ReactOS's Quick Launch band. The author implemented shell-folder initialization and enumeration, added folder-browsing UI, displayed file and folder names and icons as buttons, and integrated a context menu with the taskbar menu. ### Source excerpt Hi, everyone!! So you all are still with me? Good!! ;) As I had told last week, that this week will be rather an exciting one, and yes it indeed was. And the reason is, finally, you all will see a working (prototype) of the quick launch band. (yay!!) Let me go through chronologically, what I did this week. The first thing was to Implement the IShellFolderBand. This is a very important interface as it helps to initialize the IShellFolder and PIDL (via its InitializeSFB method) required to enumerate the folder objects. ## TIP: Don't Put Text Fields in Dialogs DevFeed: [TIP: Don't Put Text Fields in Dialogs]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-06-12T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [dialog](), [ui](), [Mobile](), [Android](), [simulator]() Tags: [android](), [dialog](), [keyboard](), [mobile](), [native](), [simulator](), [ui]() ### AI overview This tutorial explains why text fields in dialogs can behave poorly when the virtual keyboard appears. Dialogs may not resize, move, or scroll adequately, leaving fields unreachable, especially on Android. It recommends testing by rotating a phone simulator and suggests using a deeper form instead of a dialog for editing groups of fields. ### Source excerpt Text input is a very special case. Besides mixing the native and Java code we also need to deal with the appearance of the virtual keyboard which doesn't act consistently across platforms. This creates many complex edge cases that are just as problematic on native OS platforms as they are in Codename One. When we show a virtual keyboard there are two main scenarios that can take place: ## Using a "Don't Ask Again" Checkbox in Confirmation Dialogs DevFeed: [Using a "Don't Ask Again" Checkbox in Confirmation Dialogs]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-06-04T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [dialog]() Tags: [dialog](), [figure](), [mac](), [mac-os](), [os]() ### AI overview The article discusses confirmation dialogs for reversible actions, comparing macOS behavior with systems that repeatedly ask for confirmation. It proposes a dialog with a "don't ask again" checkbox as a compromise between safety and user convenience. ### Source excerpt One of my favorite things about Mac OS is something subtle that took me a while to notice: it doesn't ask stupid questions. If you delete a file on a Mac it goes to the trashcan immediately, no question. Even though other OS's copied the trashcan concept they didn't embrace it in the same way, most of them still ask whether you are sure about this action even though the action is reversible. ## Sidemenu On Top DevFeed: [Sidemenu On Top]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-05-15T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [ui](), [Development](), [dialog]() Tags: [development](), [dialog](), [event](), [implementation](), [legacy](), [performance](), [ui]() ### AI overview This article describes an in-development on-top side menu for a UI framework. The implementation moves the feature into the Toolbar class, uses an interaction dialog and pointer event listeners for drag-based expansion and collapse, and has known differences and limitations including possible positioning bugs, lack of shadow support, and lower performance. ### Source excerpt This feature is still undergoing development but I wanted to share the progress here so we can start getting bug reports and suggestions. One of the frequent requests for the side menu UI is to provide a way for it to render on top of the UI instead of shift the UI. The old side menu was written when the facebook app was the chief application that used that UI paradigm so it was built to match that approach. ## ReactOS investigates SHFileOperation and considers an IFileOperation implementation DevFeed: [ReactOS investigates SHFileOperation and considers an IFileOperation implementation]() Original publisher: [Read original article]() Published: 2014-10-19T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [file](), [implementation](), [function](), [dialog](), [Windows](), [Code]() Tags: [copy](), [file](), [files](), [free](), [implementation](), [interface](), [microsoft](), [moving](), [open-source](), [operations](), [os](), [problems](), [react](), [reactos](), [tests](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS developer reports testing SHFileOperation by moving, copying, and deleting folder structures, but could not reproduce the suspected file-writing problem. The article then examines whether to fix SHFileOperation directly or implement it around IFileOperation, including Microsoft's internal approach. ### Source excerpt Hello again! As I mentioned in the last report, I had been writing tests to find the problems in SHFileOperation. All I knew was that in some situations it would end without fully writing some file, so I wrote tests moving, copying and deleting a folder structure, and comparing the copy with the original. I tried with empty files first, then with files of random sizes, then with really big files, and also with a lot of files of relatively small size. [Next page]()