Title: Hydration writes values that the server already rendered, which restarts playing videos · Issue #71872 · angular/angular · GitHub
Open Graph Title: Hydration writes values that the server already rendered, which restarts playing videos · Issue #71872 · angular/angular
X Title: Hydration writes values that the server already rendered, which restarts playing videos · Issue #71872 · angular/angular
Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No Description During hydration, Angular writes values that the server already rendered, and the browser reacts to each write. A video with autoplay starts...
Open Graph Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No Description During hydration, Angular writes values that the server already rendered, and the browser reacts to ...
X Description: Which @angular/* package(s) are the source of the bug? core Is this a regression? No Description During hydration, Angular writes values that the server already rendered, and the browser reacts to ...
Opengraph URL: https://github.com/angular/angular/issues/71872
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Hydration writes values that the server already rendered, which restarts playing videos","articleBody":"### Which @angular/* package(s) are the source of the bug?\n\ncore\n\n### Is this a regression?\n\nNo\n\n### Description\n\nDuring hydration, Angular writes values that the server already rendered, and the browser reacts to each write.\n\nA video with `autoplay` starts playing as soon as the browser parses the server HTML. When Angular hydrates the page, the video jumps back to the start. All of these templates have the problem:\n\n```html\n\u003cvideo src=\"clip.webm\" autoplay muted>\u003c/video>\n\u003cvideo [src]=\"clip\" autoplay muted>\u003c/video>\n\u003cvideo [attr.src]=\"clip\" autoplay muted>\u003c/video>\n```\n\nThere are two causes:\n\n- `elementLikeStartShared()` calls `setupStaticAttributes()` on every element, including DOM nodes reused from the server. It writes each static attribute, the static `class`, and the static `style` again.\n- On the first update after hydration, attribute and property bindings write their values, because they have no previous value to compare with.\n\nIn Chrome, writing the same value to `src` restarts the load algorithm of a media element. Writing the same `src` to an `\u003ciframe>` loads a new document. I checked the `\u003ciframe>` case in plain JavaScript, not in an Angular app.\n\nThe writes also cost time. On a table with 300 rows of static classes, ARIA attributes, and SVG icons, hydration makes 12,961 attribute writes, and 12,871 of them keep the same value. After hydration, Chrome restyles 1,247 elements.\n\n### Please provide a link to a minimal reproduction of the bug\n\nhttps://github.com/jsaguet/ngimg-hydration-repro\n\nTo see the video restart, run `npm ci`, `npm run build:variants`, and `npm run serve:stock`, and open `http://localhost:4000/media?bootAfterLoad&bootDelay=3000`. The README has screenshots and measurements.\n\n### Please provide the exception or error you saw\n\nNo exception. The video restarts during hydration.\n\n### Please provide the environment you discovered this bug in (run `ng version`)\n\n```\nAngular CLI : 22.2.6\nAngular : 22.2.5\nNode.js : 26.11.1\nPackage Manager : npm 11.20.0\nChrome : 156\n```\n\n### Anything else?\n\nA draft pull request follows with one possible fix. It writes a value during hydration only if the DOM has a different value. The problem stands if you prefer another approach.\n\nA fix affects event handlers that run today only because of these writes. For example, a `(canplay)` handler on a video that was ready before hydration runs once today, because the video restarts. It wouldn't run after a fix, because event replay doesn't cover `canplay`.\n","author":{"url":"https://github.com/jsaguet","@type":"Person","name":"jsaguet"},"datePublished":"2026-11-08T12:29:28Z","url":"https://github.com/angular/angular/issues/71872"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:f8713ad8-7a72-c349-9675-3e3f2a8105c4 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A196:33D24F:316B30F:3F7B34E:6B01DEDB |
| html-safe-nonce | 0cfa4424f5fa320da5fcea7f5f51858e4fac2ec273720ffc51a5fc66be4c7241 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBMTk2OjMzRDI0RjozMTZCMzBGOjNGN0IzNEU6NkIwMURFREIiLCJ2aXNpdG9yX2lkIjoiODA0MDkyNTU5NzQxMDY0Nzc3MSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 3369ef972e631e3ccb79ed3719138ea6a629db7536388473b1bb335abab08953 |
| hovercard-subject-tag | issue:6270916696 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/71872/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d69a5a69d84d41ab3843417acf14f804acd4080897ef424905564e99b5423792/angular/angular/issues/71872 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d69a5a69d84d41ab3843417acf14f804acd4080897ef424905564e99b5423792/angular/angular/issues/71872 |
| og:image:alt | Which @angular/* package(s) are the source of the bug? core Is this a regression? No Description During hydration, Angular writes values that the server already rendered, and the browser reacts to ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jsaguet |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular git https://github.com/angular/angular.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 24195339 |
| octolytics-dimension-repository_nwo | angular/angular |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24195339 |
| octolytics-dimension-repository_network_root_nwo | angular/angular |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width