Affected by core regression issue on no route match?

Postponed on #3348592: [regression] Language switcher block throws exception when no route is matched

Problem/Motivation

This is a follow-up on #3270979: Incorporate Drupal 9.4 core changes to getLanguageSwitchLinks to track changes in core.

I just saw #3348592: [regression] Language switcher block throws exception when no route is matched and the lines of code are very similar to the ones in this module:

-    $links = $this->languageManager->getLanguageSwitchLinks($type, Url::fromRouteMatch(\Drupal::routeMatch()));
+    $route_match = \Drupal::routeMatch();
+    // If there is no route match, for example when creating blocks on 404 pages
+    // for logged-in users with big_pipe enabled using the front page instead.
+    $url = $route_match->getRouteObject() ? Url::fromRouteMatch($route_match) : Url::fromRoute('<front>');
+    $links = $this->languageManager->getLanguageSwitchLinks($type, $url);

I didn't run into it yet myself, but I guess our implementation here should be aligned to the one in core?

Did anyone experience this issue?
---
jan26/2026|skaught: linking #3353518: Frontpage (View as Page) url-alias's are different after upgrading. similarities in work.

Steps to reproduce

TBD!

Proposed resolution

Fix the implementation in this issue like core does

Remaining tasks

- Monitor the core isse
- Make changes accordingly
- Carry over tests

User interface changes

None

API changes

None

Data model changes

None