---
title: "Deprecation: #94094 - navigationFrameModule in Module Registration"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-94094"
source: "Changelog/11.5/Deprecation-94094-NavigationFrameModuleInModuleRegistration.rst"
typo3-version: "11.5"
typo3-major: 11
type: "deprecation"
issue: 94094
forge: "https://forge.typo3.org/issues/94094"
tags: ["Backend", "NotScanned", "ext:backend"]
rendered: "2026-09-23T19:53:57+00:00"
---

# Deprecation: #94094 - navigationFrameModule in Module Registration {#deprecation-94094}

See [forge#94094](https://forge.typo3.org/issues/94094)

## Description {#description}

TYPO3 allowed for each module to include an iFrame for the navigation area with
the option `navigationFrameModule` and `navigationFrameModuleParameters`.
Since TYPO3 4.5 it was possible to also use a JavaScript component instead
via `navigationComponentId`.

TYPO3 v11 allows to use Web Components for the `navigationComponentId` option,
and all Core-based navigation components have been migrated to Lit-based
Web Components.

With this technology, TYPO3 does not need to handle iFrames for
the navigation area anymore, which is why the feature, together
with the option `navigationFrameModule` has been marked as deprecated.

## Impact {#impact}

TYPO3 installations with third-party extensions registering
custom navigation iFrames will trigger a PHP `E_USER_DEPRECATED` error.

## Affected Installations {#affected-installations}

TYPO3 installations with third-party extensions shipping modules
with a custom navigation iFrame.

## Migration {#migration}

Migration should be done by using Web Components, as this is much
faster and allows for better interoperability due to less usages of iFrames.