<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web Standards on Dmitry Sheiko&#39;s Web Development Blog</title>
    <link>https://dsheiko.com/categories/web-standards/</link>
    <description>Recent content in Web Standards on Dmitry Sheiko&#39;s Web Development Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dsheiko.com/categories/web-standards/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Add Web Push Notifications to a Next.js App</title>
      <link>https://dsheiko.com/weblog/how-to-add-web-push-notifications-to-nextjs-app/</link>
      <pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/how-to-add-web-push-notifications-to-nextjs-app/</guid>
      <description>Web Push notifications have quietly become one of the most effective engagement channels on the web. They don’t require an email address. They don’t depend on social algorithms. And they work even when your website isn’t open.&#xA;If you run a blog, SaaS, e-commerce store, or internal platform, Web Push can dramatically improve retention and real-time communication.&#xA;Let’s walk through what Web Push actually is, how it works under the hood, and how you can implement it in a Next.</description>
    </item>
    <item>
      <title>Leveraging HTML5.2 for More Functional and Interactive Web Apps</title>
      <link>https://dsheiko.com/weblog/building-real-life-applications-with-functional-elements-of-html-5-2/</link>
      <pubDate>Tue, 15 Aug 2017 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/building-real-life-applications-with-functional-elements-of-html-5-2/</guid>
      <description>What do you do when you need a widget-like functionality? At the present there is a whole generation of developers who with as a rule are googling for ready-made jQuery plugin. Can&amp;rsquo;t we do better than that? With advance of web-components we are expected to compose UIs from these building blocks. They are many. One can find one for almost any task. They are highly customizable. One can reuse the functionality, but with own original representation.</description>
    </item>
    <item>
      <title>JavaScript Modules in 2017: Where We Stand and What’s Next</title>
      <link>https://dsheiko.com/weblog/state-of-javascript-modules-2017/</link>
      <pubDate>Thu, 10 Aug 2017 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/state-of-javascript-modules-2017/</guid>
      <description>Before modules Historically JavaScript had neither a module system, nor facilities to load sources from within the code. In order to understand what have now, let&amp;rsquo;s take a retrospective look. I remember in the past a number of libraries where the code-base was split into a separate files which were concatinating during the build process. As simply as that it didn&amp;rsquo;t help with module isolation, but improved maintainability by organizing the code in files of meaningful names.</description>
    </item>
    <item>
      <title>Creating a web-component: VanillaJS vs X-Tag vs Polymer</title>
      <link>https://dsheiko.com/weblog/creating-a-web-component-with-vanillajs-x-tag-and-polymer/</link>
      <pubDate>Wed, 10 Sep 2014 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/creating-a-web-component-with-vanillajs-x-tag-and-polymer/</guid>
      <description>It seems like these days the most trending concept in the HTML5 world is web components. But what the fuss is all about? In order to make such a simple thing as a container expanding on click in past we needed to write CSS and JavaScript. Today thanks to checkbox-hack and :focus or :target pseudo-selector we go on with CSS-only. In fact by using summary/details elements we do not need any tricks with CSS to make it working, considering that browser already supports this feature.</description>
    </item>
    <item>
      <title>Mastering HTML5 Forms: Validation, Inputs, and Beyond</title>
      <link>https://dsheiko.com/weblog/making-use-of-html5-form/</link>
      <pubDate>Wed, 27 Mar 2013 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/making-use-of-html5-form/</guid>
      <description>Since the very beginning of HTML there were no much of changes regarding forms until recently. Yet, there was an attempt to bring a new API with XForms, but it was never really supported by any of major browsers. Now we have a comprehensive consistent Form API which allows us to create full-fledged forms even with not help of JavaScript. Everything sounds so exciting until you try to use HTML 5 Forms on real projects.</description>
    </item>
    <item>
      <title>Optimizing Mobile Navigation: A Smooth UX for Small Screens</title>
      <link>https://dsheiko.com/weblog/tuning-navigation-for-mobile-devices/</link>
      <pubDate>Sat, 27 Oct 2012 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/tuning-navigation-for-mobile-devices/</guid>
      <description>Making design responsive means not only certain representations on different screens, but also particular behavior on different devices. Usually on mobile devices mouse is not available, keyboard with navigation keys is out of reach. So we are short of controls to provide a useful navigation.&#xA;Image viewer Let’s take image viewer. User taps a thumbnail and gets an overlay with the image. We don’t have much screen space on the smartphone.</description>
    </item>
    <item>
      <title>Bringing realtime to your web applications</title>
      <link>https://dsheiko.com/weblog/real-time-web-application-architecture/</link>
      <pubDate>Mon, 17 Oct 2011 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/real-time-web-application-architecture/</guid>
      <description>Few years ago only lazy didn’t say about bringing desktop application experience to the web ones. However in reality, it just meant that user actions didn’t always required page reload, but could change page UI dynamically. As for other application events, as a rule they were not handled dynamically.&#xA;Well, now you can find more and more web applications acting really like desktop ones. For example, Facebook and G+ have widgets which update automatically.</description>
    </item>
    <item>
      <title>WebSockets vs Server-Sent Events vs Long-polling</title>
      <link>https://dsheiko.com/weblog/websockets-vs-sse-vs-long-polling/</link>
      <pubDate>Mon, 05 Sep 2011 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/websockets-vs-sse-vs-long-polling/</guid>
      <description>Apparently social networking is the banner of the nowadays web. Everybody intends bringing some features into his projects. Some of them require immediate notification. That is getting common, if you open a page with upcoming messages (status feed, notification subsystem, friends-list), you expected them being updated as soon as a new message (status, notification, friend-making action) arrives. As you well know, original web design allowed only one-way client-server communication (one requests, another one responds), though now HTML5 working group doing their best to fix it or rather to patch it.</description>
    </item>
    <item>
      <title>HTML5 Video on iPhone: Challenges and Solutions</title>
      <link>https://dsheiko.com/weblog/html5-video-on-iphone/</link>
      <pubDate>Tue, 17 May 2011 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/html5-video-on-iphone/</guid>
      <description>Enabling your videos for iPhone Safari doesn’t seem as a big deal. You know it supports HTML5 . Besides, you don’t even need to write event handlers and produce a skin by yourself, but only take a ready JS component. Apparently [videojs.com] is getting close to be the most popular one. Though, I personally like [mediaelementjs.com]. It is very simple to use any of them. The only difficulty is to get your videos converted to h.</description>
    </item>
    <item>
      <title>ECMAScript 5 and JS frameworks</title>
      <link>https://dsheiko.com/weblog/ecmascript-5-and-js-frameworks/</link>
      <pubDate>Mon, 13 Dec 2010 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/ecmascript-5-and-js-frameworks/</guid>
      <description>Standards are being always approved with a slow pace. Though, the features declared in drafts usually find their implementation long before the standard release. Let’s take for an instance Websockets, which were already implemented in Chrome/Safari and Firefox 4b when standard unexpectedly changed. Apparently YUI3 and jQuery have implemented for long time the features, which are only coming up with ECMAScript 5 (the implementations is called JavaScript 1.8.5) spread.&#xA;YUI 3 from the very beginning introduced controllable attributes.</description>
    </item>
    <item>
      <title>Real-Time Updates with HTML5: Unlocking Server-Sent Events</title>
      <link>https://dsheiko.com/weblog/html5-and-server-sent-events/</link>
      <pubDate>Thu, 10 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/html5-and-server-sent-events/</guid>
      <description>Related articles: Bringing realtime to your web applications and WebSockets vs Server-Sent Events vs Long-polling&#xA;Besides, already noted bidirectional communication channel, known as WebSocket, HTML5 propositions include also comet communication pattern by defining Server-Sent Events (SSE). WebSocket widely discussed by now, tons of server implementations are available and you can play already with fluent browser implementation under Chrome. However the second server-push technology of HTML5 yet stays in shadow.&#xA;We are used to consider the HTTP protocol as request-response model, which means that the client sends a HTTP request and waits until the HTTP response is received.</description>
    </item>
    <item>
      <title>Persistent Full Duplex Client-Server Connection via Web Socket</title>
      <link>https://dsheiko.com/weblog/persistent-full-duplex-client-server-connection-via-web-socket/</link>
      <pubDate>Wed, 05 May 2010 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/persistent-full-duplex-client-server-connection-via-web-socket/</guid>
      <description>RIA is considered one of the most distinctive features of the modern Web, reflecting a trend where web applications grow to resemble desktop applications. The approach, however, has limits. The overwhelming majority of &amp;ldquo;rich&amp;rdquo; web applications are still built on the request-response model. Events on the client side can reach the server, but not vice versa. To build something as simple as a chat, you have to use tricks. These techniques for emulating bi-directional connections are collectively called Comet, a term coined by Alex Russell of Dojo.</description>
    </item>
    <item>
      <title>How to Make AJAX Read between the Lines</title>
      <link>https://dsheiko.com/weblog/how-to-make-ajax-read-between-the-lines/</link>
      <pubDate>Fri, 24 Feb 2006 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/how-to-make-ajax-read-between-the-lines/</guid>
      <description>Technical sites often include terms that readers may not know. The old approach was to link each term to a definition popup, but that requires a click, a load, and another click to close. With AJAX, the definition appears the moment the cursor hovers over the term and disappears when it moves away. No extra page weight: JavaScript fetches the definition from an external source on demand.&#xA;The same technique has broader uses.</description>
    </item>
  </channel>
</rss>
