# HTML5 and CSS3 tricks
Web development techniques that use HTML5 markup and CSS styling features to build and present web pages.
This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.
## Why regex isn't email validation
DevFeed: [Why regex isn't email validation]()
Original publisher: [Read original article]()
Author: WorkOS
Published: 2026-08-24T00:00:00Z
Content type: article
Language: en
Sources: [WorkOS Blog]()
Topics: [Parsing](), [Forms](), [HTML5 and CSS3 tricks](), [Library](), [Internet]()
Tags: [advice](), [deliverability](), [domain](), [email](), [forms](), [framework](), [html5](), [internet](), [library](), [regex](), [validation]()
### AI overview
The article explains that email syntax validation with regexes, HTML5 checks, or framework libraries does not establish deliverability or confirm that a mailbox exists. It recommends a loose syntax check and stopping there, while recognizing that stronger checks address separate, less reliable questions.
### Source excerpt
Checking that an address looks right and checking that it can receive mail are different problems. Most signup forms only solve the first one.
## One-Shot Any Web App with Gradio's gr.HTML
DevFeed: [One-Shot Any Web App with Gradio's gr.HTML]()
Original publisher: [Read original article]()
Author: yuvraj sharma; hysts; Freddy Boulton
Published: 2026-02-18T00:00:00Z
Content type: article
Language: en
Sources: [Hugging Face - Blog]()
Topics: [web applications](), [modern web development](), [HTML5 and CSS3 tricks](), [React UI animations]()
Tags: [3d](), [app](), [artificial-intelligence](), [claude](), [community](), [css](), [gradio](), [html](), [html5](), [javascript](), [object-detection](), [python](), [react](), [spaces](), [speech](), [three-js](), [transcription](), [vibe-coding]()
### AI overview
The article shows how Gradio's gr.HTML can create interactive, single-file Python web apps without a separate frontend build step. Examples include timers, a kanban board, visual ML result viewers, 3D controls, and live speech transcription.
### Source excerpt
We're on a journey to advance and democratize artificial intelligence through open source and open science.
## Python 3.12.12, 3.11.14, 3.10.19 and 3.9.24 are now available!
DevFeed: [Python 3.12.12, 3.11.14, 3.10.19 and 3.9.24 are now available!]()
Original publisher: [Read original article]()
Author: Thomas Wouters
Published: 2025-10-09T00:00:00Z
Content type: release
Language: en
Sources: [Python Insider]()
Topics: [releases](), [HTML5 and CSS3 tricks]()
Tags: [complexity](), [html5](), [python](), [python-3-10](), [release](), [releases](), [security]()
### AI overview
Python 3.12.12, 3.11.14, 3.10.19, and 3.9.24 are security releases. The supplied notes cover libexpat and setuptools updates, ZIP validation, and HTML parsing fixes.
### Source excerpt
[](https://discuss.python.org/t/python-3-12-12-3-11-14-3-10-19-and-3-9-24-are-now-available/104273#p-273973-old-timer-release-party-1)Old-timer Release Party...
## Sass Pixel Art
DevFeed: [Sass Pixel Art]()
Original publisher: [Read original article]()
Published: 2015-05-03T00:00:00Z
Content type: tutorial
Language: en
Sources: [Una Kravets]()
Topics: [Sass](), [HTML5 and CSS3 tricks](), [pixel](), [Programming]()
Tags: [blog-post](), [css3](), [how-to](), [pixel-art](), [sass]()
### AI overview
This tutorial explains how Sass lists, matrices, maps, and list functions can generate pixel art using CSS3 multiple box shadows. It examines how individually positioned box shadows form pixels and how Sass data structures organize them.
### Source excerpt
Pixel art is so much fun! This blog post walks through how to read a matrix-like list with Sass and generate Mario pixel art from box shadows.
## Building Year in Review 2014 with SVG and Rails
DevFeed: [Building Year in Review 2014 with SVG and Rails]()
Original publisher: [Read original article]()
Author: Tessa Thornton
Published: 2015-02-11T14:43:00Z
Content type: tutorial
Language: en
Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]()
Topics: [modern web development](), [Web Development](), [interactive website](), [HTML5 and CSS3 tricks]()
Tags: [css](), [data](), [javascript](), [shopify](), [svg](), [web-graphics](), [year-in-review]()
### AI overview
A tutorial on building Shopify's Year in Review with SVG, JavaScript, Rails helpers, and d3.js. It explains why SVG suited the project's graphics and animations, including data visualizations and scroll-driven path drawing.
### Source excerpt
As we have for the past 3 years, Shopify released a Year in Review to highlight some of the exciting growth and change we've observed over the past year. Designers James and Veronica had ambitious ideas for this year's review, including strong, bold typographic treatments and interactive data visualizations. We've gotten some great feedback on the final product, as well as some curious developers wondering how we pulled it off, so we're going to review the development process for Year in Review and talk about some of the technologies we leveraged to make it all happen.
## Data Synchronization - Touchlab
DevFeed: [Data Synchronization - Touchlab]()
Original publisher: [Read original article]()
Published: 2013-03-10T20:59:00Z
Content type: tutorial
Language: en
Sources: [Touchlab | Enterprise Mobile Innovation & Development]()
Topics: [data](), [HTML5 and CSS3 tricks](), [web applications](), [Image](), [Mobile]()
Tags: [android](), [data](), [development](), [html5](), [mobile](), [synchronization](), [thoughts](), [web-app]()
### AI overview
This article introduces offline data synchronization for HTML5 and web applications. It explains that synchronization can involve local edits, server updates, conflicts with other users' data, database relationships, business logic, and image uploads. It outlines a workflow of periodically updating from the server, editing data locally, and pushing changes back.
### Source excerpt
Synchronizing data is a big topic. It means different things to different people, and is obviously framed by projects they've worked on.
## Why moving elements with translate() is better than pos:abs top/left
DevFeed: [Why moving elements with translate() is better than pos:abs top/left]()
Original publisher: [Read original article]()
Author: Paul Irish
Published: 2012-12-20T08:00:00Z
Content type: article
Language: en
Sources: [Paul Irish]()
Topics: [CSS](), [modern web development](), [developer tooling](), [Chrome](), [HTML5 and CSS3 tricks]()
Tags: [chrome](), [css](), [examples](), [html5](), [laptop](), [layout](), [performance](), [pixel](), [update](), [writeup]()
### AI overview
This article compares moving elements with CSS 2D transforms such as translate() against absolute positioning with top/left. Using Chrome DevTools evidence, it explains that transforms can move an element on a GPU-composited layer, reducing per-frame paint work and producing smoother animation, while noting that pixel snapping can sometimes make top/left appear visually preferable.
### Source excerpt
Update (2016): The more canonical writeup of this technique is at High Performance Animations - HTML5 Rocks. TL;DR: Only transform & opacity; never top/left! In modern days we have two primary options for moving an element across the screen: using CSS 2D transforms and translate() using position:absolute and top/left Chris Coyier was asked why you should use translate. Go read his response which covers well why it's more logical to move elements for design purposes (with transform) independent of your element layout (with position). I wanted to answer this with Chrome and get some good evidence on what's going on. I ended up recording a video on the experience: It's a good watch and dives into Chrome DevTools' Timeline, compositing, paint cost, accelerated layers, and more... but if you want the abbreviated text version, read on: First thing, Chris made some simple demos to try things out: This sorta works, but there is such low complexity in this situation that it's all going to look pretty great. We need something closer to a complex website to properly evaluate the two (thx joshua for the macbook!): Now we're starting to get closer, but immediately I get distracted by something. Distraction: Pixel snapping If you run the demo above you might notice the top edge of the MacBook looks a little bit better in the top/left one. (And here I am writing a post about why translate is better! Preposterous!) So this is due to the absolute positioned macbook sticks to pixel positions, whereas the translate()'d one can interpolate at sub-pixel positions. One of the Chrome GPU engineers, James Robinson, called this the "dubstep effect", as these pixels appear to be getting pounded by bass. Here's a closeup of the effect... watch the top white edge of the macbook in each: On the left, you see stair-stepping down three pixels and back up again. This pixel snapping may result in a less distracting transition in this case, though this wouldn't be so noticeable if you were moving object
## Wave Raid powered by Timed Comments
DevFeed: [Wave Raid powered by Timed Comments]()
Original publisher: [Read original article]()
Published: 2012-04-05T00:00:00Z
Content type: tutorial
Language: en
Sources: [SoundCloud Backstage Blog]()
Topics: [SDKs](), [HTML5 and CSS3 tricks]()
Tags: [announcements](), [api](), [app](), [event](), [gaming](), [html5](), [scripting]()
### AI overview
The article shows how SoundCloud timed-comment events in its JavaScript SDK can drive an HTML5 game, using comments as collectible coins. It also suggests synchronized visualizations, transcripts, and real-time rich-media applications.
### Source excerpt
One of the SoundCloud API's most powerful features is the timed comment. At its core it seems simple enough: a piece of text associated with a point in time for a particular track. But where you see timed opinions, I see a light-weight game scripting engine. So when Johannes Wagener told me he was adding an event to our JS SDK, I immediately began work on Wave Raid: Quest for the Timed Comment.
## HTML5 Widget API
DevFeed: [HTML5 Widget API]()
Original publisher: [Read original article]()
Published: 2012-03-22T00:00:00Z
Content type: release
Language: en
Sources: [SoundCloud Backstage Blog]()
Topics: [HTML5 and CSS3 tricks](), [Web Development](), [modern web development]()
Tags: [announcements](), [api](), [documentation](), [html5](), [javascript](), [playground]()
### AI overview
SoundCloud announces a JavaScript API for its HTML5 widget, enabling access to and control of widget properties.
### Source excerpt
Today we're officially announcing our JavaScript API for the new HTML5 SoundCloud Widget. To use it, just insert the script tag on a page...
## Semantics in practice and mapping semantic value to its consumers
DevFeed: [Semantics in practice and mapping semantic value to its consumers]()
Original publisher: [Read original article]()
Author: Paul Irish
Published: 2011-11-14T18:25:00Z
Content type: article
Language: en
Sources: [Paul Irish]()
Topics: [Accessibility](), [HTML5 and CSS3 tricks](), [aria](), [HTML](), [web-standards]()
Tags: [accessibility](), [aria](), [browsers](), [html](), [html-elements](), [html5](), [implementation]()
### AI overview
The article argues that practical accessibility should take priority over intricate or unstable HTML semantics. It discusses HTML5 elements, document outlining, heading structure, screen reader behavior, ARIA, browser implementation, and assistive technology accessibility APIs.
### Source excerpt
Divya Manian kicked off a good bout of discussion of HTML semantics with her post Our pointless pursuit of semantic value. It called into question the amount of time we spend on identifying the Right and Best ways of marking up our content while highlighting details of some of the consumers of semantics like assistive technology (AT). Jeremy Keith responded in Pursing Semantic Value. I wanted to chime in on Jeremy's post so, I've published below my comment from the original post: Thanks Jeremy for raising a practical example. This discussion is a tough one as much of HTML5 has clear semantics (nav/header/footer), but then parts have underdeveloped semantic meaning or add confusion to authors. Jeremy's gist is a great example, in fact, of a poor time investment in semantics. It ascribes value to the new method of document outlining, which recently sees different styling for h1's depending on section nesting. Recent browsers do indeed style the h1's different; but if you actually structure your document as such, you do it to the detriment of your screenreader users: they will either get these h1's all as top level headlines or a mishmash of heading nesting levels that don't match any expected behavior (As an aside, this is completely unrelated but if anyone's curious what CSS it takes to make that new h1 styling work across browsers... feast your eyes on this beauty) Additionally, is on the chopping block and is not supported by JAWS. Suffice it to say, Now is not a smart time to invest your time understanding the unwieldy document outlining algorithm. Luke's comment digs in deeper to the messy semantic state of the outlining algorithm. semantics are hard...let's go shopping and CREATE EPIC SHIT... -- patrick h. lauke (@patrick_h_lauke) November 14, 2011 The practicalities of making accessible web content are messy, but important. The fact that we seem to spend more time on div vs article vs. section than on learning ARIA is a crime. (Furthermore, learning ARIA isn'
## Experiment 02: Destroying SoundCloud & Instagram
DevFeed: [Experiment 02: Destroying SoundCloud & Instagram]()
Original publisher: [Read original article]()
Published: 2011-05-11T00:00:00Z
Content type: article
Language: en
Sources: [SoundCloud Backstage Blog]()
Topics: [HTML5 and CSS3 tricks]()
Tags: [api](), [content](), [experiment](), [hacks]()
### AI overview
The article describes a map-based SoundCloud experience for Moby's album, built with Rails, jQuery, CSS3, and PolyMaps. It integrates SoundCloud and Instagram APIs to play the album and add fan-submitted photos.
### Source excerpt
I was fortunate enough to be given the opportunity to help Moby premiere his new record via SoundCloud. I didn't know what to expect from...
## Add HTML5 Data Attribute Support to XHP
DevFeed: [Add HTML5 Data Attribute Support to XHP]()
Original publisher: [Read original article]()
Author: Codebeforethehorse
Published: 2011-04-21T01:18:00Z
Content type: tutorial
Language: en
Sources: [Stefan Parker]()
Topics: [PHP](), [HTML5 and CSS3 tricks](), [aria](), [Accessibility](), [Web Development]()
Tags: [accessibility](), [aria](), [html](), [html5](), [php](), [xhp]()
### AI overview
A tutorial on modifying PHP-based XHP to support HTML5 data-* and WAI-ARIA attributes. It explains how to bypass validation for these attributes, limit that behavior to HTML elements rather than custom components, and optimize the relevant attribute-access methods.
### Source excerpt
UPDATE: I've added data- and aria- attribute support into XHP by default. Downloading the latest source will get you this for free. XHP runs validation checks on all attribute sets and gets, but in the emerging world of HTML5, data attributes are validation-less. With a little bit of tweaking, you can add HTML5 data attribute support to all HTML elements in XHP. In the same swing, you can add WAI-ARIA support for your accessibility users. In this post we'll dig into the php source of XHP and do a little optimizations of our own. First, you'll need to change the getAttribute() and setAttribute() functions inside :x:composable-element to account for these special attributes. The logic behind it is simple, if it's a data or aria attribute, skip the validation checks. This is how those two functions would now look: final public function setAttribute($attr, $val) { if (substr($attr, 0, 5) != 'data-' && substr($attr, 0, 5) != 'aria-') { $this->validateAttributeValue($attr, $val); } $this->attributes[$attr] = $val; return $this; } final public function getAttribute($attr) { if (isset($this->attributes[$attr])) { return $this->attributes[$attr]; } else if (substr($attr, 0, 5) == 'data-' || substr($attr, 0, 5) == 'aria-') { return null; } // Maintain the rest of this function as is. } Voila! Now all your XHP elements support HTML5 data attributes. You could stop here and be just fine, but technically this isn't the best solution. HTML elements support data attributes, but you don't want your own custom XHP components to take them*. To allow HTML5 data attributes on only HTML elements, we need to rethink our approach. Going back to XHP's default behavior, rename the getAttribute() and setAttribute() methods in :x:composable-element to getDeclaredAttribute() and setDeclaredAttribute() respectively, make them protected, and replace them with the following non-final functions: public function getAttribute($attr) { return $this->getDeclaredAttribute($attr); } public function setA