# form Published articles for form. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mikrotik Winbox 4.3 is out DevFeed: [Mikrotik Winbox 4.3 is out]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-29T14:38:07Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [MikroTik](), [Windows](), [Zip](), [GUI](), [layout]() Tags: [2026](), [feature](), [file](), [form](), [input](), [layout](), [mikrotik](), [network-engineering-resources](), [performance](), [redesign](), [render](), [right](), [sorting](), [table](), [toolbar](), [ui](), [v3](), [version](), [widget](), [winbox](), [windows](), [zip]() ### AI overview MikroTik WinBox 4.3 is a release update that adds a Windows ARM64 package and introduces or improves table, form, toolbar, settings, font, login, window-selection, layout, and scrolling behavior. ### Source excerpt What's new in 4.3 (2026-Jul-20 10:14): *) app: add Windows for arm64 version in file WinBox_Windows_arm64.zip;*) form: make multiline input field height logic as in WinBox v3;*) table: add quick comment feature (allow multi-row commenting);*) table: allow opening "Table settings" also via right mouse click;*) table: calculate implicit height to fit 16 regular rows including ... Read more The post Mikrotik Winbox 4.3 is out appeared first on Justin Wilson (j2sw). ## Airflow Survey 2025 DevFeed: [Airflow Survey 2025]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2026-01-22T00:00:00Z Content type: article Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [data](), [CSV]() Tags: [2025](), [airflow](), [analysis](), [apache-airflow](), [community](), [csv](), [download](), [form](), [graphics](), [interactive](), [report](), [responses](), [share](), [survey](), [users](), [view]() ### AI overview This page presents the Airflow Survey 2025 interactive report, hosted by Astronomer and sponsored and supported by the Apache Airflow community. The supplied evidence does not include the survey findings. ### Source excerpt The interactive report is hosted by Astronomer. The Apache Airflow community thanks Astronomer for running this survey, for sponsoring it and providing the report in this form, and for their effort in marketing, analysis, and preparing the graphics. View raw data Download survey responses (CSV) ## Cognitive Load and Web Accessibility: Quick Tips for Clearer Content DevFeed: [Cognitive Load and Web Accessibility: Quick Tips for Clearer Content]() Original publisher: [Read original article]() Author: Marissa Published: 2025-07-24T19:45:00Z Content type: tutorial Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [Website](), [Users](), [User interface design]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [autism](), [charts](), [cognitive-load](), [form](), [layout](), [navigation](), [people-with-disabilities](), [quick-tips](), [tips](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview This article explains how cognitive load affects web accessibility, particularly for people with cognitive and learning disabilities. It recommends simplifying complex content, using consistent layouts and navigation, and following the Understandable principle of WCAG. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) is designed to improve experiences for all users with disabilities. That includes people who have cognitive disabilities and learning disabilities -- but those users are often left out of the discussion. ## Creating a Schema-Based Form System DevFeed: [Creating a Schema-Based Form System]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2022-01-31T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [Forms](), [Front end](), [React](), [Structured-data](), [Library]() Tags: [architecture](), [error-handling](), [form](), [forms](), [front-end](), [react](), [schema]() ### AI overview This tutorial presents an example schema-based form system for React. It describes defining a form schema and passing it to a component that handles common values, errors, validation, dirty state, and field components. The example uses Formik for form values and submission and suggests Yup for validation. ### Source excerpt View the Source or Demo for the schema-based form system described in this article. Working with forms on the front end is tedious and... ## Using VueJS + GraphQL to make Practical Magic DevFeed: [Using VueJS + GraphQL to make Practical Magic]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2018-08-27T22:29:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [GraphQL](), [vuejs](), [Content Management System](), [Front end](), [JavaScript](), [axios](), [Bootstrap](), [Jamstack]() Tags: [auto-complete](), [axios](), [bootstrap](), [craft](), [everyday](), [form](), [graphql](), [headless](), [insights](), [jamstack](), [javascript](), [like](), [magic](), [practical](), [problems](), [saving](), [searching](), [solve](), [submission](), [using](), [vuejs]() ### AI overview A practical tutorial showing how to use VueJS and GraphQL with a headless Craft CMS backend to implement auto-complete search and save contact-form submissions. It introduces the frontend and backend tooling used in the examples, including Axios, Bootstrap 4, Craft CMS, and CraftQL. ### Source excerpt Make some practical magic with VueJS + GraphQL to solve everyday problems like auto-complete searching and form submission saving with a headless Craft CMS server ## Uploading files using 'fetch' and 'FormData' DevFeed: [Uploading files using 'fetch' and 'FormData']() Original publisher: [Read original article]() Author: Stanko Published: 2018-03-19T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [fetch](), [API](), [Web Development]() Tags: [api](), [browser](), [fetch](), [form](), [headers](), [json](), [request]() ### AI overview This tutorial explains how to upload files with fetch and FormData. It shows that the request should not manually set the Content-Type header, allowing the browser to add the multipart boundary required for the server to parse the uploaded file correctly. ### Source excerpt Today I learned: To upload files using fetch and FormDataFormData is supported in IE10+. you must not set Content-Type header. const fileInput = document.querySelector('#your-file-input') ; const formData = new FormData(); formData.append('file', fileInput.files[0]); const options = { method: 'POST', body: formData, // If you add this, upload won't work // headers: { // 'Content-Type': 'multipart/form-data', // } }; fetch('your-upload-url', options); Problem I had # My API wrapper class has default content type header set to: 'Content-Type': 'application/json' So I thought, to upload files using FormData, it would be enough to override it with: 'Content-Type': 'multipart/form-data' But alas, it didn't work, server couldn't parse the files I was uploading. I've wasted about half an hour, and then noticed that simple HTML form was setting something else: Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryIn312MOjBWdkffIM It had this boundary thing I didn't know anything about. Then I started searching around the internet and found the solution. To set the correct boundary, I had to explicitly delete Content-Type header. In that case browser will set the correct boundary itself. Adding this line solved it. // Remove 'Content-Type' header to allow browser to add // along with the correct 'boundary' delete options.headers['Content-Type']; Explanation # What is boundary and why I had to delete the header? Multipart form allow transfer of binary data, therefore server needs a way to know where one field's data ends and where the next one starts. That's where boundary comes in. It defines a delimiter between fields we are sending in our request (similar to & for GET requests). You can define it yourself, but it is much easier to let browser do it for you. Example payload: ------WebKitFormBoundaryIn312MOjBWdkffIM Content-Disposition: form-data; name="file"; filename="my-image.jpg" Content-Type: image/jpeg ------WebKitFormBoundaryIn312MOjBWdkffIM Content-Dispos ## How to Add Custom Action Buttons to Django Admin DevFeed: [How to Add Custom Action Buttons to Django Admin]() Original publisher: [Read original article]() Author: Haki Benita Published: 2016-11-01T22:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [Django](), [Forms](), [account](), [audit]() Tags: [articles](), [custom-action](), [django](), [django-admin](), [email](), [form](), [how-to](), [logging]() ### AI overview A tutorial showing how to add custom deposit and withdraw action buttons for individual rows in a Django Admin list view. It uses forms to collect input, execute operations, optionally send notification emails, and handle logging, auditing, success, and failure. ### Source excerpt The built-in admin actions, operate on a queryset and are hidden in a dropbox menu. They are not suitable for most use cases. In this article we are going to add custom action buttons for each row in a Django Admin list view. ## The Refresh Test DevFeed: [The Refresh Test]() Original publisher: [Read original article]() Published: 2014-04-10T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [Ember](), [Website](), [browser](), [App]() Tags: [app](), [browser](), [ember](), [fields](), [form](), [make](), [reload](), [required]() ### AI overview The article argues that web applications should preserve form data and tolerate page refreshes. It uses frustrating account-creation and online checkout experiences to illustrate the problem, then discusses how Ember App Kit's live reloading encouraged the author to make an application refresh-resistant. ### Source excerpt How many times has the following happened to you? You go to a web site and it asks you to create an account. You fill out a form with all the obvious fields and hit submit. The page refreshes and shows you the form again. Phone Number is required Well, that's annoying. There was no indication that the site needed your phone number. You prefer not to give out your phone number to every web site, but this one is run by a company you trust, so you scroll down and fill it out. You submit the form again. ## Object-Form mapping DevFeed: [Object-Form mapping]() Original publisher: [Read original article]() Published: 2010-10-19T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [Forms](), [ASP.NET](), [Ruby on Rails](), [Object-relational mapping](), [business logic](), [PHP](), [unit tests]() Tags: [asp-net](), [business-logic](), [form](), [forms](), [orm](), [php](), [rails](), [ruby](), [unit-tests]() ### AI overview This article discusses object-form mapping between HTML forms and application objects. It describes ASP.NET's FormView and ObjectDataSource approach, compares it with Ruby on Rails conventions and a similar PHP approach, and argues that marshalling form parameters into objects can simplify page flow and support testing business logic. ### Source excerpt I'm pretty sure most developers (web developers anyway) have heard of ORM (Object Relational Mapping) tools like NHibernate that map your database tables and to objects. These ORM tools reduce interaction with the database to just a few method calls, many times just Save(), GetById(), and a few custom query methods. There's a lot written about ORM, but no one really writes about the mapping between HTML forms and the objects that ORM maps.ASP.NET has a great solution for OFM (I'm calling it OFM because google won't give me a real name for it). If you use a FormView in combination with an ObjectDataSource you can bind the properties of your object to form elements. This is pretty cool because it reduces your code to writing an ORM mapping, creating factory methods to get and save the object, and some ASP markup that maps the object to HTML elements.I was playing with Ruby on Rails which has a somewhat different approach to OFM. Basically you write regular HTML and give your form elements names like "account[id]", "account[name]", etc. This seems like a little more work than the ASP.NET way except that on the server side it uses this notation to wrap the query string into an object that can be referenced in object notation from ruby code like "account.id", "account.name", etc. I believe PHP does something similar. I like this method because it's very light on HTTP - there's no obstructively bloated view state being passed around like there is in ASP.NET and you can pass several objects through the query string.Basically, OFM manages some of the page flow by marshalling form parameters into objects that can easily be passed to a factory method. This is awesome because it means I can focus more effort on writing unit tests for business logic that has no dependencies on the web API. It allows me to to keep page flow simple and sets up business logic for creating restful web services (seriously, you could just slap [WebMethod] attributes on the factory methods and voila y