Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 2 min read

The Inline Layer of app.onepassapps.com: 10,574 Tags, One Style Value and Not One Event Handler

I work on OnePassApps, so this is our own site. Everything below was measured on 9 November 2026 over plain HTTPS: the 56 URLs in our own sitemap, one GET each, no browser, no session, no cookies, no JavaScript. The lay

I work on OnePassApps, so this is our own site. Everything below was measured on 9 November 2026 over plain HTTPS: the 56 URLs in our own sitemap, one GET each, no browser, no session, no cookies, no JavaScript.

The layer under the microscope here is the one that lives inside a tag - inline style declarations and inline event handlers. The stylesheet is already written up in The OnePassApps Stylesheet, and the class names are counted in The Class Layer. This post is about what the tags themselves carry, attribute by attribute.

The count

Across the fleet the served HTML holds 10,574 tags, once the contents of every script and style block are stripped out so that only real markup is counted.

Of those 10,574 tags:

  • 56 pages carry one style attribute, and it is always the html element - one per page, 56 of 56 pages.
  • 0 carry an inline event handler.

One style attribute, one value

Every one of the 56 style attributes reads the same sentence: color-scheme: dark. It sits on the html element, next to the language and theme attributes:

<html
  lang="en-GB"
  class="dark"
  data-theme="dark"
  data-theme-preset="graphite"
  style="color-scheme: dark"
>

One attribute, one value, 56 pages. No page sets a second inline style and no page sets a different one - the count of distinct style values across the whole fleet is 1.

Not one inline event handler

The other half of the measurement found nothing at all. No page in the fleet carries an onclick, an oninput, an onsubmit or any other inline handler, and that is not a sampling result - it is the whole fleet.

I checked it two ways. First, an explicit list of 47 event attribute names, matched against every attribute on every tag of every page: zero hits. Second, a generic scan of the raw bytes of all 56 responses for any on...= token at all, including inside the inline scripts: zero hits again.

So the shell the server sends is inert on purpose. The behaviour arrives with the app bundle that boots after it - which is the same split The Control Layer measured from the other end, where the served HTML carries zero inputs and 33 of the 56 pages are fallback cards.

What this does not measure

  • No browser was involved. These are counts of the bytes the server sent, not of a live DOM.
  • Listeners attached at runtime by the bundle are not counted, only attributes present in the served HTML.
  • Script and style contents were excluded from the tag count, so the 10,574 is markup only.
  • One build, one network, 9 November 2026.

Look at it yourself

The whole site is one membership of nine browser apps: app.onepassapps.com and the guides that sit next to each app.

That is the whole layer. One inline style, one value, and no inline handlers anywhere - measured on our own pages, in our own build, on the day.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.