콘텐츠로 건너뛰기

Content

Embedding, multimedia, data, and other content-related features.

Content Experience & Sentiment

Both the most liked and most disliked features were security-related: the Sanitizer API drew the most positive opinions, while Content-Security Policy topped the frustration list.

This contrast highlights how security mechanisms that reduce friction and integrate cleanly with existing workflows are welcomed, while those that impose rigid policies, demand meticulous configuration, or break previously working code can generate resentment.

Group by:

Sort by:

01
Content
47.6%
29%
22.3%
02
Content
33.5%
26.7%
39.6%
03
Content
19.8%
25.6%
54.3%
04
Content
17.6%
31.2%
50.7%
05
Content
14.1%
31.2%
53.7%
06
Content
13.7%
20.1%
66%
07
Content
6.9%
16.4%
76.2%
08
Content
6.1%
27%
66.3%
09
Content
6%
45.6%
47.9%
10
Content
WebMCP
5.3%
47.8%
46.3%

Experience

  • <span aria-hidden="true">🤓</span> 사용해 본 적 있음: Respondents who have used an item.
  • <span aria-hidden="true">👀</span> 들어본 적 있음: Respondents who have heard about an item, but haven't used it.
  • <span aria-hidden="true">🤷</span> 들어본 적 없음: Respondents who have never heard about an item.

Sentiment

  • Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
  • Neutral: Responents who did not indicate any sentiment about a technology.
  • Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.

Content Pain Points

The data paints a very clear picture: By far the most pressing content point is HTML reuse, both across pages, and within the same page. Even though this is already possible through build tools and component-based front-end frameworks, it appears there is large demand for a platform-native feature.
What are your pain points around managing content in HTML?
(자유 형식 질문)
Multiple
Top pain point topics overall.

View:

Items that are not one of “limitations”
0%
20%
40%
60%
80%
100%
01
HTML Reuse
2
02
Internationalization
1
+1
03
Browser vendor issues
2
-1
04
Tables
+4
05
1
-2
06
Accessibility
+4
07
Semantics
08
Ecosystem issues
+5
09
Developer Experience
10
<iframe>
11
Styling & customization
+4
12
Headings
1
-1
13
Education
-1
14
Security & privacy
-10
15
Cognitive overload
+10
16
Reliance on JavaScript
-10
0%
20%
40%
60%
80%
100%

추천하는 리소스

Web Security, v2
Steve Kinney
Temporal

Web Security, v2

Take control of your application's security! Learn how to protect against common vulnerabilities every developer should know.
우리를 지원해 준 파트너들께 감사 드립니다! 더 알아보기.