> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Browser-Specific Issues
> Resolve Nextedy RISKSHEET problems that occur in specific browsers, including Firefox scrollbar behavior, post-update rendering failures, and comparison mode quirks.
export const LastReviewed = ({date}) => {
if (!date) return null;
const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
year: "numeric",
month: "long",
day: "numeric",
timeZone: "UTC"
});
return
Last reviewed on {formatted}
;
};
## Browser Compatibility Overview
| Browser | Status | Known Issues |
| --------------- | -------------------------- | --------------------------------------- |
| Google Chrome | ✅ **Recommended** | None known |
| Microsoft Edge | ✅ **Recommended** | None known |
| Mozilla Firefox | Supported with limitations | Scrollbar click triggers cell selection |
Use **Google Chrome** or **Microsoft Edge** for the best Risksheet experience. These browsers have the highest usage among users and receive the most testing coverage.
## Firefox Scrollbar Issue
In Firefox, clicking on Risksheet scrollbars can cause the sheet to jump unexpectedly. Firefox treats scrollbars as part of the page area, which triggers cell selection beneath the scrollbar position.
**Symptoms:**
* Clicking a vertical or horizontal scrollbar selects a cell behind the scrollbar
* The grid view jumps to a different position after scrollbar interaction
* Scroll position becomes unpredictable during extended editing sessions
**Workaround:**
1. Use the mouse scroll wheel instead of clicking scrollbar tracks
2. Use keyboard navigation ( arrow keys, Page Up/Down) to move through the grid
3. Switch to Chrome or Edge for extended editing sessions
This Firefox scrollbar behavior is tracked as a known issue. Due to very low Firefox usage among Risksheet users, it is prioritized at a lower level.
## Post-Update Rendering Failures
After updating Risksheet, you may experience what appears to be a browser-specific rendering failure. Before investigating browser compatibility, follow this diagnostic sequence:
### Step 1: Check the Risksheet Topic
The most common cause of post-update failures is a missing Risksheet topic in the current Polarion view -- not a browser problem.
1. Verify you are in the correct Polarion view/hat
2. Navigate to **Administration > Topics**
3. Confirm the Risksheet topic is enabled for your current view
XML parsing errors on `style.css` or redirects to the project home page after an update are almost always caused by a missing Risksheet topic in the user's current Polarion view. Check topic configuration before investigating browser-specific causes.
### Step 2: Clear Browser Cache
If the topic is correctly configured, clear your browser cache to remove stale cached assets:
* **Chrome / Edge:** Press `Ctrl+Shift+Delete` (Windows) or `Cmd+Shift+Delete` (Mac), select "Cached images and files", and clear
* **Firefox:** Press `Ctrl+Shift+Delete` (Windows) or `Cmd+Shift+Delete` (Mac), select "Cache", and clear
Then reload the page with a hard refresh: `Ctrl+Shift+R` (or `Cmd+Shift+R` on Mac).
### Step 3: Check Browser Console
Open the browser Developer Tools (`F12`) and check the **Console** tab for errors:
* Errors on non-Risksheet Polarion pages indicate a Polarion-level issue, not a Risksheet problem
* Errors only on Risksheet pages may indicate a configuration or compatibility issue
* Look for messages such as `Network response was not ok` or `Error while reading configuration`, which point to server communication or sheet configuration problems rather than browser incompatibility
## Baseline Comparison URL Behavior
Baseline comparison mode adds a `comparingTo` parameter to the browser URL. This parameter management works in both iframe and standalone contexts across all supported browsers.
If comparison mode gets stuck or the URL retains the `comparingTo` parameter after exiting:
1. Click **Cancel Comparison** in the Risksheet toolbar
2. If the parameter persists, manually remove `comparingTo=...` from the URL bar
3. Reload the page
## Browser Extensions and Conflicts
Browser extensions that modify page content, inject scripts, or block network requests can interfere with Risksheet rendering and data loading.
1. Open Risksheet in an **incognito** or **private** browsing window (extensions are disabled by default)
2. If the issue resolves in incognito mode, disable extensions one at a time to identify the conflict
3. Common problematic extension types:
* Ad blockers that filter network requests
* Script blockers or privacy extensions
* Custom CSS injection tools
## Verification
After troubleshooting, you should now see:
* Risksheet loads correctly with the full grid visible
* Scrollbar interactions work smoothly (or you are using the recommended Chrome/Edge browsers)
* Baseline comparison activates and deactivates cleanly with proper URL management
* No stale cached assets interfere with rendering after updates
## See Also
* [Rendering and Display Errors](/risksheet/troubleshooting/rendering-errors) -- resolve grid display problems
* [Session Timeout Errors](/risksheet/troubleshooting/session-timeout) -- fix session expiration during editing
* [Baseline Loading Issues](/risksheet/troubleshooting/baselines-loading) -- troubleshoot baseline loading failures
* [Access Denied Errors](/risksheet/troubleshooting/access-denied) -- resolve topic and permission issues
* [Slow Page Loading](/risksheet/troubleshooting/performance-slow-loading) -- improve loading performance