On SpikerSoftware.com, text selection is currently enabled throughout most of the website. As a low-priority UX improvement, text selection should be disabled across navigation and marketing content to reduce accidental interactions, particularly on mobile devices.
Issue Description
While browsing the website, users can unintentionally highlight headings, descriptions, cards, and other static content. On touch devices, this behavior is more noticeable because accidental long-presses may trigger text selection instead of the intended navigation or scrolling action.
The attached screenshot demonstrates multiple content elements selected simultaneously within The Symbiote section, including:
Hero headlines
Step titles
Description text
Section labels
Because these elements are informational and do not require copying under normal usage, maintaining text selection can negatively affect the perceived responsiveness of the site and introduce unnecessary user interaction states.
Environment
Property
Value
Application
SpikerSoftware.com
Module
Global Website Navigation & Marketing Pages
Environment
Production
Browser
Firefox
Operating System
Windows 11
Device
Desktop / Mobile
Page Tested
The Symbiote
Preconditions
User is navigating the website.
Steps to Reproduce
Open SpikerSoftware.com.
Navigate to any product page (e.g., The Symbiote).
Drag the mouse across content or perform a long press on mobile.
Observe that text becomes selected.
Expected Result
Static interface content should not be selectable.
Examples include:
Navigation menus.
Product descriptions.
Marketing cards.
Headlines.
Call-to-action buttons.
Product walkthrough sections.
Actual Result
Users can select most page content.
Large sections of marketing text become highlighted.
Mobile interactions can result in unintended text selection events.
Evidence
The attached screenshot shows:
The "Cinco pasos. Control total." section selected.
Multiple descriptive paragraphs highlighted.
Marketing content entering an unintended selection state.
Impact
Reduces the perceived responsiveness of the site.
Can interfere with touch-based navigation.
Creates accidental interactions on mobile devices.
Slightly degrades the overall polished feel of the user interface.
Frequency
Always
Reproducibility
100%
Severity
Low
Notes
Text selection should remain enabled where copying content is expected or beneficial, including:
Documentation.
Support articles.
Technical references.
Input fields.
Contact forms.
Code snippets.
User-generated content.
Suggested Improvement
Apply non-selectable behavior to marketing and navigation components.
## Summary
On **SpikerSoftware.com**, text selection is currently enabled throughout most of the website. As a low-priority UX improvement, text selection should be disabled across navigation and marketing content to reduce accidental interactions, particularly on mobile devices.
## Issue Description
While browsing the website, users can unintentionally highlight headings, descriptions, cards, and other static content. On touch devices, this behavior is more noticeable because accidental long-presses may trigger text selection instead of the intended navigation or scrolling action.
The attached screenshot demonstrates multiple content elements selected simultaneously within **The Symbiote** section, including:
- Hero headlines
- Step titles
- Description text
- Section labels
Because these elements are informational and do not require copying under normal usage, maintaining text selection can negatively affect the perceived responsiveness of the site and introduce unnecessary user interaction states.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoftware.com |
| Module | Global Website Navigation & Marketing Pages |
| Environment | Production |
| Browser | Firefox |
| Operating System | Windows 11 |
| Device | Desktop / Mobile |
| Page Tested | The Symbiote |
## Preconditions
User is navigating the website.
## Steps to Reproduce
1. Open **SpikerSoftware.com**.
2. Navigate to any product page (e.g., The Symbiote).
3. Drag the mouse across content or perform a long press on mobile.
4. Observe that text becomes selected.
## Expected Result
Static interface content should not be selectable.
Examples include:
- Navigation menus.
- Product descriptions.
- Marketing cards.
- Headlines.
- Call-to-action buttons.
- Product walkthrough sections.
## Actual Result
- Users can select most page content.
- Large sections of marketing text become highlighted.
- Mobile interactions can result in unintended text selection events.
## Evidence
The attached screenshot shows:
- The "Cinco pasos. Control total." section selected.
- Multiple descriptive paragraphs highlighted.
- Marketing content entering an unintended selection state.
## Impact
- Reduces the perceived responsiveness of the site.
- Can interfere with touch-based navigation.
- Creates accidental interactions on mobile devices.
- Slightly degrades the overall polished feel of the user interface.
## Frequency
Always
## Reproducibility
100%
## Severity
Low
## Notes
Text selection should remain enabled where copying content is expected or beneficial, including:
- Documentation.
- Support articles.
- Technical references.
- Input fields.
- Contact forms.
- Code snippets.
- User-generated content.
## Suggested Improvement
Apply non-selectable behavior to marketing and navigation components.
Recommended CSS:
```css
user-select: none;
-webkit-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
Recommended targets:
Navigation bar.
Hero sections.
Product marketing cards.
Landing page content.
Step-by-step showcase sections.
CTA buttons.
Excluded targets:
Forms.
Documentation pages.
Knowledge base articles.
Support content.
Code examples.
This would create a cleaner, more app-like browsing experience while minimizing accidental text selection on both desktop and mobile devices.
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, text selection is currently enabled throughout most of the website. As a low-priority UX improvement, text selection should be disabled across navigation and marketing content to reduce accidental interactions, particularly on mobile devices.
Issue Description
While browsing the website, users can unintentionally highlight headings, descriptions, cards, and other static content. On touch devices, this behavior is more noticeable because accidental long-presses may trigger text selection instead of the intended navigation or scrolling action.
The attached screenshot demonstrates multiple content elements selected simultaneously within The Symbiote section, including:
Because these elements are informational and do not require copying under normal usage, maintaining text selection can negatively affect the perceived responsiveness of the site and introduce unnecessary user interaction states.
Environment
Preconditions
User is navigating the website.
Steps to Reproduce
Expected Result
Static interface content should not be selectable.
Examples include:
Actual Result
Evidence
The attached screenshot shows:
Impact
Frequency
Always
Reproducibility
100%
Severity
Low
Notes
Text selection should remain enabled where copying content is expected or beneficial, including:
Suggested Improvement
Apply non-selectable behavior to marketing and navigation components.
Recommended CSS: