# Chrome console deprecation warnings on Discourse v2026.1.0-latest (+307)

**URL:** https://meta.discourse.org/t/chrome-console-deprecation-warnings-on-discourse-v2026-1-0-latest-307/394534
**Category:** Development
**Tags:** composer
**Created:** [January 28, 2026, 12:54pm UTC](https://meta.discourse.org/t/chrome-console-deprecation-warnings-on-discourse-v2026-1-0-latest-307/394534 "2026-01-28T12:54:09Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [January 28, 2026, 1:12pm UTC](https://meta.discourse.org/t/chrome-console-deprecation-warnings-on-discourse-v2026-1-0-latest-307/394534/2 "2026-01-28T13:12:24Z")

</div>

> [@Ethsim2](#):
>
> Accessing site.mobileView / site.desktopView during site initialization

This is legacy that’s slowly being replaced; we don’t have a distinct timeline for when all of the instances of this will be resolved.

I’m assuming the same for the other one.

> [@Ethsim2](#):
>
> - there is a recommended modern replacement pattern for themes / components that still rely on these APIs.

For the one above that’s outlined in:

[Designing for Different Devices (Viewport Size, Touch/Hover, etc.)](https://meta.discourse.org/t/designing-for-different-devices-viewport-size-touch-hover-etc/367810)

---

_[View the full topic](https://meta.discourse.org/t/chrome-console-deprecation-warnings-on-discourse-v2026-1-0-latest-307/394534)._