On SpikerSoftware.com, changing the website language causes a page reload that resets the user's position within the current page, returning them to the top. This disrupts navigation and creates a poor user experience, especially on long pages where users may be reviewing content before switching languages.
Issue Description
The website currently performs a full page reload when the language is changed. As a result, the user's current scroll position and navigation context are lost. Instead of remaining at the same section of the page after the translation is applied, the user is returned to the beginning of the page.
For example, if a user is reading content near the middle or bottom of the landing page and decides to switch from English to Spanish (or vice versa), the page reloads and automatically places the user back at the top of the site.
This behavior is not ideal from a UX perspective because language selection should only affect content localization, not the user's browsing position.
Environment
Property
Value
Application
SpikerSoftware.com
Module
Localization / Language Selector
Environment
Production
Browser
Firefox
Operating System
Windows 11
Device
Desktop
Preconditions
User is browsing a page with sufficient scrollable content.
User is not positioned at the top of the page.
Language selector is available.
Steps to Reproduce
Navigate to www.spikersoftware.com.
Scroll to the middle or bottom section of the page.
Change the language using the language selector (e.g., English → Spanish or Spanish → English).
Observe the page behavior after the reload.
Expected Result
The language should change successfully.
The user should remain at the same page location and scroll position.
The current navigation context should be preserved.
Actual Result
The page reloads.
The user is returned to the top of the page.
Current reading position is lost.
Evidence
The attached screenshot shows the language selector located in the navigation bar of the main landing page. During testing, changing the language triggered a page refresh that returned the user to the beginning of the page instead of preserving the current scroll position.
Impact
Disrupts the browsing experience.
Forces users to manually locate the section they were reading.
Creates friction when comparing translations.
Becomes increasingly noticeable on long pages with multiple sections.
Frequency
Always
Reproducibility
100%
Severity
Medium
Notes
The issue appears to be caused by a full page reload without preserving the current scroll position or route state.
This behavior may also affect other pages throughout the site where language switching is available.
Suggested Fix
Preserve the current URL, route, and scroll position during language changes.
Store the user's scroll position before applying localization and restore it afterward.
Prefer client-side localization updates when possible to avoid full page reloads.
If a reload is required, maintain navigation context by restoring the previous viewport position once translation resources have loaded.
## Summary
On **SpikerSoftware.com**, changing the website language causes a page reload that resets the user's position within the current page, returning them to the top. This disrupts navigation and creates a poor user experience, especially on long pages where users may be reviewing content before switching languages.
## Issue Description
The website currently performs a full page reload when the language is changed. As a result, the user's current scroll position and navigation context are lost. Instead of remaining at the same section of the page after the translation is applied, the user is returned to the beginning of the page.
For example, if a user is reading content near the middle or bottom of the landing page and decides to switch from English to Spanish (or vice versa), the page reloads and automatically places the user back at the top of the site.
This behavior is not ideal from a UX perspective because language selection should only affect content localization, not the user's browsing position.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoftware.com |
| Module | Localization / Language Selector |
| Environment | Production |
| Browser | Firefox |
| Operating System | Windows 11 |
| Device | Desktop |
## Preconditions
- User is browsing a page with sufficient scrollable content.
- User is not positioned at the top of the page.
- Language selector is available.
## Steps to Reproduce
1. Navigate to **www.spikersoftware.com**.
2. Scroll to the middle or bottom section of the page.
3. Change the language using the language selector (e.g., English → Spanish or Spanish → English).
4. Observe the page behavior after the reload.
## Expected Result
- The language should change successfully.
- The user should remain at the same page location and scroll position.
- The current navigation context should be preserved.
## Actual Result
- The page reloads.
- The user is returned to the top of the page.
- Current reading position is lost.
## Evidence
The attached screenshot shows the language selector located in the navigation bar of the main landing page. During testing, changing the language triggered a page refresh that returned the user to the beginning of the page instead of preserving the current scroll position.
## Impact
- Disrupts the browsing experience.
- Forces users to manually locate the section they were reading.
- Creates friction when comparing translations.
- Becomes increasingly noticeable on long pages with multiple sections.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium
## Notes
The issue appears to be caused by a full page reload without preserving the current scroll position or route state.
This behavior may also affect other pages throughout the site where language switching is available.
## Suggested Fix
- Preserve the current URL, route, and scroll position during language changes.
- Store the user's scroll position before applying localization and restore it afterward.
- Prefer client-side localization updates when possible to avoid full page reloads.
- If a reload is required, maintain navigation context by restoring the previous viewport position once translation resources have loaded.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
On SpikerSoftware.com, changing the website language causes a page reload that resets the user's position within the current page, returning them to the top. This disrupts navigation and creates a poor user experience, especially on long pages where users may be reviewing content before switching languages.
Issue Description
The website currently performs a full page reload when the language is changed. As a result, the user's current scroll position and navigation context are lost. Instead of remaining at the same section of the page after the translation is applied, the user is returned to the beginning of the page.
For example, if a user is reading content near the middle or bottom of the landing page and decides to switch from English to Spanish (or vice versa), the page reloads and automatically places the user back at the top of the site.
This behavior is not ideal from a UX perspective because language selection should only affect content localization, not the user's browsing position.
Environment
Preconditions
Steps to Reproduce
Expected Result
Actual Result
Evidence
The attached screenshot shows the language selector located in the navigation bar of the main landing page. During testing, changing the language triggered a page refresh that returned the user to the beginning of the page instead of preserving the current scroll position.
Impact
Frequency
Always
Reproducibility
100%
Severity
Medium
Notes
The issue appears to be caused by a full page reload without preserving the current scroll position or route state.
This behavior may also affect other pages throughout the site where language switching is available.
Suggested Fix