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

Dev
1

Hi all,

While testing a Discourse site, I’m seeing consistent Chrome console deprecation warnings during initial page load.

This does not break functionality - the site operates normally - but I wanted to check whether this is already known or being cleaned up in recent commits.

Environment

  • Discourse core: v2026.1.0-latest +307
    (latest available at time of testing: +349, ~42 commits ahead)
  • Browser: Chrome (current stable)
  • OS: Windows 11
  • Theme: standard site theme (no custom JS added manually)
  • Plugins: only official Discourse plugins enabled

Console warnings observed

  • Accessing site.mobileView / site.desktopView during site initialization may lead to errors in future versions
  • document.execCommand() is deprecated

These appear during early app initialization (before user interaction) and are reproducible on hard reload.

I’m aware these are deprecation warnings rather than runtime errors - mainly checking whether:

  • these are already addressed in more recent -latest commits, or
  • there is a recommended modern replacement pattern for themes / components that still rely on these APIs.

Happy to test against +349 or a clean install if that helps.

Thanks!

2

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.

For the one above that’s outlined in:

Designing for Different Devices (Viewport Size, Touch/Hover, etc.)