AI summary by TwinMind

The State Of HTML

Theo - t3․gg

24m 24s

Survey Introduction & Background

  • State of HTML survey by Sasha Grief with Leveroo helping with design/branding
  • Survey open until October 10th, results not yet available
  • Significantly improved design compared to previous surveys
  • Features reading list functionality to save items for later review

HTML Forms Section

  • Form Controls Discussed:
    • Datalist: Used for autocomplete functionality
    • Input media capture: Has more experience than most
    • Input show picker: Heard of but not used yet
    • Form data API: Used but frustrated with type safety challenges
    • Select list: No browser support yet
    • Content editable plain text only: Hadn't heard of but sounds useful
  • Input Types Experience:
    • Extensively used: Range, number, file, date, datetime-local, month, color, email, tel, URL
    • Limited use: Time (once), week (never used)
  • Form Features:
    • Required attribute: Absolutely used
    • Pattern attribute: Not used directly but may be used under hood with React Hook Form
    • Custom validity and check validity: Used
    • Report validity: Never used, added to reading list
  • Pain Points: Type safety integration with reactive JS frameworks, relationship between HTML elements and validation layer

Interactivity Features

  • Dialog Element: Used before, will continue using
  • Details/Summary: Heard of but haven't used, interested in use cases
  • Exclusive Accordion: Played with but not supported yet
  • Popover: Extensively used, very happy it's built into HTML now
  • Inert Attribute: Never heard of, likes concept for accessibility (better than disabled buttons for screen readers)
  • DOM Manipulation Methods:
    • Used: All DOM attribute methods, most DOM HTML string handling features
    • DOM parser: Fun experience
    • Insert adjacent element: Haven't used
    • Fragments: Seem cool, added to reading list
  • Pain Points: Relationship with forms, popovers, tooltips, disabled states with good accessibility

Media & Performance

  • Lazy Loading: Used quite a bit, very nice
  • Source Set/Sizes: Used, relies on components like Next.js image component
  • Resource Hints: Really cool for browser optimization, done automatically with Next.js
  • Content Security Policy: Dealt with extensively, important for XSS prevention
  • Fetch Priority: Used for ensuring logo loads quickly
  • Blocking Render: Used sparingly for critical scripts like analytics

Media Elements

  • Elements Used: Math (fine), SVG (absolutely), video (will use again), object, canvas (love), iframe (has gotchas), picture (usually use image), audio (very familiar with)
  • Iframe Attributes: Sandbox, allow, cross-origin, integrity all used
  • Structured Data: Time/date elements used, no experience with RDFa or JSON-LD (added to reading list)

Internationalization

  • Features Used:
    • Lang and dir attributes: Absolutely used
    • International date/time and number formatting: Used once each
    • International message format: Haven't used but very excited about it
    • International plural rules and relative time: Used both
  • Pain Points: Hydration errors around client/server runtime differences, especially relative datetime rendering in different timezones

Web Components

  • Template Element: Really cool for rendering DOM content later without re-rendering
  • Custom Elements: Used but mixed feelings, prefers framework land
  • Shadow DOM: Did not love, feels like weird abstraction, painful interrupt between shadow and traditional DOM
  • Declarative Shadow DOM: Gets more confusing with shadow trees
  • Slot Assignment: Curious about named and imperative slot assignment
  • Element Internals API: Never heard of but seems interesting
  • DOM Parts & HTML Modules: Not supported yet but interesting concepts
  • Pain Points: Many parts necessary for simple things, Shadow DOM roughness, compatibility with existing tools, accessibility challenges

Accessibility Considerations

  • Impairments Considered:
    • Vision: Very colorblind, accounts for this, uses contrast tools
    • Mobility: Thinks about drag-and-drop alternatives, ensures one-click methods
    • Vestibular disorders: Avoids flashing lights but acknowledges not enough
    • Learning disabilities: Simplifies copy, increases text size
  • Features Used: Landmark elements, tab index (lots of effort), ARIA attributes, semantic HTML
  • Screen Readers Tested: VoiceOver (most used on Mac), NVDA (good bit on Windows), some Jaws experience
  • Tools Used: Axe, Lighthouse
  • Biggest Pain Point: Access to teams - users with accessibility needs should be able to reach development teams directly, advocates for contact buttons on every page

Progressive Web Apps & Native-like Features

  • APIs Used:
    • File system access API: Very useful
    • Badging API: Heard of, needs to use more
    • Share API: Used, really nice
    • File handling API: Using for many things
  • Window Controls Overlay API: Didn't know existed, very exciting for PWA customization
  • Storage: Abuses local/session storage, used document cookie, should use cache storage/IndexedDB more
  • PWA Technologies: Used manifest, mock service worker (not real service worker yet), notifications
  • Pain Points: iOS PWA support (improving but has ways to go), web animations feel rudimentary compared to native tools

Development Tools & Frameworks

  • Site Generators Used: 11ty, Gatsby (didn't like), Next.js (loves), Astro (used but needs more), SvelteKit, Solid Start, Remix
  • Missing Features: Regex backwards lookup, WebRTC >30fps (Firefox issue), view transitions (wants more browser support)
  • Most Wanted Elements: Infinite scroll, tabs, toggle/switch (needs these badly)

Personal Developer Profile

  • Experience: 11-20 years coding
  • Age: 28 (mustache makes him look older)
  • Company Size: 2-5 people
  • Education: CS degree
  • Location: US
  • Usage: Thousands of developers use libraries/packages he creates/maintains
  • HTML Usage: 50/50 split between TypeScript and JSX
  • Survey Score: 865 points, top 2% (expected given time spent on these topics)

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome