Ir al contenido

State of HTML 2025

Utilización

Cómo se utiliza HTML.

Interoperabilidad de navegadores

There's always a bit of lag between the state of the web platform and actual real-world adoption, so it shouldn't come as a surprise that the Popover API still tops the rankings. But make no mistake, this feature now officially has the "Newly Available" Baseline status, meaning using it across browser should be much less of an issue going forward.

¿Qué funciones HTML o API de navegador existentes no puedes utilizar debido a las diferencias entre navegadores o a la falta de compatibilidad?
Multiple
Top pain point topics corresponding to specific web platform features.

View:

Items tagged “features”
0%
20%
40%
60%
80%
100%
1
2
<select>
+4
3
-1
4
5
+7
6
-1
7
-3
8
+2
9
<input type="date">
-1
10
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
884
14%
25
5

Funcionalidad limitada

Form controls and other interactive elements are once again those perceived as most limiting. With customizable select out of the way, it looks like perhaps date pickers should be the next target.

¿Qué funciones HTML o API de navegador existentes no puedes utilizar por otros motivos (y por qué)?
Multiple
Top pain point topics corresponding to specific web platform features.

View:

Items tagged “features”
0%
20%
40%
60%
80%
100%
1
<select>
2
<input type="date">
3
+5
4
5
-1
6
+1
7
<select multiple>
8
-2
9
10
<input type="color">
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
406
7%
5

Elementos que faltan

This year again datatable is the most requested new element. While it would certainly be nice to have built-in filtering, sorting, searching, etc. capabilities, it doesn't seem like something that will become a reality anytime soon.

On the other hand, progress is being made on other long-awaited features such as a native switch element, which explains its drop in the rankings.

Si pudieras añadir 3 elementos a HTML, ¿cuáles serían?
Multiple
0%
20%
40%
60%
80%
100%
1
Tabla de datos (con clasificación, filtrado, etc.)
1,545
2
Combobox / Autocompletar
1,249
3
Pestañas
-1
1,182
4
Menú desplegable
1,071
5
Rich text editor
975
6
Interruptor / Palanca
-3
957
7
HTML include
920
8
Sortable drag-and-drop list
910
9
Esqueleto de interfaz de usuario / Marcador de posición de carga
-5
728
10
Menú contextual / Menú del botón derecho del ratón
-5
719
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,887
62%
25

Styling Issues

It will be no surprise that form inputs top the list of hardest elements to style. Thankfully, customizable select elements are in the works, even though browser support is still lagging.

Which elements do you struggle the most to style or visually customize?
Multiple
0%
20%
40%
60%
80%
100%
1
<select>
1,699
2
<input type="date">
1,178
3
<select multiple>
792
4
791
5
Validation errors
491
6
432
7
<input type="time">
401
8
369
9
<input type="range">
317
10
314
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,331
54%
10

HTML Reuse

It's hard to dispute that JavaScript components have become the dominant paradigm of building UIs on the web. And yes, dealing with all these competing front-end frameworks can be messy–but it's a mess we know (and maybe even love?), a fact that makes it tough for web components to gain ground beyond fourth place.

Which strategies do you use to implement components or otherwise reuse HTML code?
Multiple
0%
20%
40%
60%
80%
100%
1
Component-based JavaScript Frameworks
2,696
2
Server-side templating
1,922
3
Client-side templating
1,297
4
1,237
5
Build-time templating
1,184
6
Copy-paste
914
7
Web Components helper libraries
492
8
🚫 None
44
9
Other Answers
69
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,749
60%
10

Design Systems

Design systems have become a requirement for most large-scale projects, and that fact is reflected in the popularity of all these various approaches.

Do you use any of the following design system strategies to maintain UI consistency?
Multiple
0%
20%
40%
60%
80%
100%
1
Elements/components
3,084
2
Design tokens
2,664
3
Utilities
2,407
4
Guidelines
2,008
5
Patterns
1,316
6
🚫 None
112
7
Other Answers
45
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,810
61%
10

Equilibrio entre HTML/CSS y JavaScript/TypeScript

As shown in the “Component Strategies” chart above, JavaScript is the de facto vessel for a lot of the HTML code we produce. Which explains why we spend so much time writing it!

¿Cómo divides tu tiempo entre escribir código HTML/CSS y JavaScript (o TypeScript)?
0%
20%
40%
60%
80%
100%
1
100% HTML/CSS
65
2
1
269
3
2
422
4
3
287
5
50%–50%
635
6
5
494
7
6
1,179
8
7
494
9
100% JS
40
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,885
62%
57%
63%
10

Uso de HTML

While the average survey respondents mainly works on dynamic web apps, many of us also spend time creating blogs or other text-heavy sites, harkening back to HTML's roots as a document-oriented language.

¿Para qué utilizas HTML?
Multiple
0%
20%
40%
60%
80%
100%
1
Aplicaciones web
3,378
2
Blogs o sitios con mucho texto
2,253
3
Sitios de marketing y landing pages
1,894
4
Sistemas de diseño
1,519
5
Correos electrónicos
1,139
6
Desktop apps
891
7
Aplicaciones móviles
879
8
Documentos impresos
659
9
E-Commerce sites
10
🚫 None
16
11
Other Answers
114
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
3,933
63%
10
💡
Está científicamente probado que compartir esta encuesta en Twitter, Facebook o por correo electrónico mejora tu rendimiento de JavaScript hasta en un 15%.

Otros puntos débiles

When looking at web platform pain points more generally, browser support stands out–especially when it comes to the Apple ecosystem.

As a result, community initiatives such as the #AppleBrowserBan hashtag have been gaining steam, while on the vendor front Interop moves the needle in the right direction each year.

¿Algún otro problema relacionado con el uso de HTML y tecnologías afines?
Multiple
Top pain point topics overall.

View:

Items that are not one of “limitations”
0%
20%
40%
60%
80%
100%
1
Browser support
1
2
Environments & Consumers
2
3
Content
2
4
Reliance on JavaScript
5
Cognitive overload
2
6
Ecosystem issues
2
7
Education
8
Accessibility
9
Excessive complexity
10
Poor design
1
11
Styling & customization
1
12
Performance
13
Vendor politics
14
Missing elements
15
16
workplace
17
Tooling
18
Security & privacy
19
PDF
20
Declarative APIs
21
Other Answers
0%
20%
40%
60%
80%
100%
% de respuestas respondidas
191
3%
5

Recursos recomendados

Frontend Masters

Frontend Masters

Advance Your Skills with In-Depth, Modern Front-End Engineering Courses
¡Gracias a nuestros socios por apoyarnos! Aprende más.