# [QoL Improvement] Disable Text Selection Across Non-Editable Areas of Spiker Stack Website #1219

Open
opened 2026-10-30 03:27:26 +00:00 by enjin2310 · 0 comments

Summary

On Spiker Stack, text selection is currently enabled across most of the website. As a quality-of-life improvement, text selection should be disabled for non-editable interface elements to provide a more polished and application-like user experience.

Issue Description

While navigating the Spiker Stack website, users can accidentally highlight headings, paragraphs, labels, platform selectors, and other static content. This behavior is especially noticeable when dragging the mouse while interacting with buttons, sliders, comparisons, animations, or image demonstrations.

The attached screenshot shows a large portion of the landing page text selected unintentionally. Since these elements are informational and not intended for text interaction, allowing selection creates unnecessary visual noise and can make the interface feel less polished.

This behavior is common on websites but is generally avoided in product landing pages that aim to simulate a desktop application experience.

Environment

Property Value
Application Spiker Stack Website
Module Landing Page
Environment Production
Browser Firefox
Operating System Windows 11
Device Desktop

Preconditions

User accesses the Spiker Stack marketing website.

Steps to Reproduce

  1. Open spikerstack.com.
  2. Navigate through the landing page.
  3. Click and drag the mouse across text content.
  4. Observe that headings, descriptions, and UI labels become highlighted.

Expected Result

Static UI content should not be selectable.

Examples:

  • Headlines
  • Marketing descriptions
  • Navigation labels
  • Product feature labels
  • Demo captions
  • Platform badges

Actual Result

  • Most page text can be selected.
  • Large text blocks become highlighted accidentally.
  • The selection remains visible until manually cleared.

Evidence

The attached screenshot shows:

  • The main title "Spiker Stack" selected.
  • The marketing description fully highlighted.
  • Platform tags and pricing information selected.
  • Multiple content blocks highlighted simultaneously.

Impact

  • Reduces perceived polish of the website.
  • Creates accidental visual artifacts during navigation.
  • Makes the site feel less application-like.
  • Can interfere with interaction on animated or drag-based components.

Frequency

Always

Reproducibility

100%

Severity

Low

Notes

Text selection should remain enabled where it serves a functional purpose, including:

  • Documentation pages.
  • License keys.
  • Code snippets.
  • Input fields.
  • Text areas.
  • User-generated content intended for copying.

Suggested Improvement

Apply non-selectable behavior to static interface elements.

##Examples:

user-select: none;
-webkit-user-select: none;
-moz-user-select: none;


##Recommended targets:

Hero sections
Navigation components
Marketing cards
Demo labels
Feature descriptions
CTA buttons

##Exclude:

Form fields
Input controls
Documentation content
Support pages intended for text copying

This would provide a cleaner and more professional user experience while reducing accidental text highlighting.
## Summary On **Spiker Stack**, text selection is currently enabled across most of the website. As a quality-of-life improvement, text selection should be disabled for non-editable interface elements to provide a more polished and application-like user experience. ## Issue Description While navigating the Spiker Stack website, users can accidentally highlight headings, paragraphs, labels, platform selectors, and other static content. This behavior is especially noticeable when dragging the mouse while interacting with buttons, sliders, comparisons, animations, or image demonstrations. The attached screenshot shows a large portion of the landing page text selected unintentionally. Since these elements are informational and not intended for text interaction, allowing selection creates unnecessary visual noise and can make the interface feel less polished. This behavior is common on websites but is generally avoided in product landing pages that aim to simulate a desktop application experience. ## Environment | Property | Value | |-----------|--------| | Application | Spiker Stack Website | | Module | Landing Page | | Environment | Production | | Browser | Firefox | | Operating System | Windows 11 | | Device | Desktop | ## Preconditions User accesses the Spiker Stack marketing website. ## Steps to Reproduce 1. Open **spikerstack.com**. 2. Navigate through the landing page. 3. Click and drag the mouse across text content. 4. Observe that headings, descriptions, and UI labels become highlighted. ## Expected Result Static UI content should not be selectable. Examples: - Headlines - Marketing descriptions - Navigation labels - Product feature labels - Demo captions - Platform badges ## Actual Result - Most page text can be selected. - Large text blocks become highlighted accidentally. - The selection remains visible until manually cleared. ## Evidence The attached screenshot shows: - The main title **"Spiker Stack"** selected. - The marketing description fully highlighted. - Platform tags and pricing information selected. - Multiple content blocks highlighted simultaneously. ## Impact - Reduces perceived polish of the website. - Creates accidental visual artifacts during navigation. - Makes the site feel less application-like. - Can interfere with interaction on animated or drag-based components. ## Frequency Always ## Reproducibility 100% ## Severity Low ## Notes Text selection should remain enabled where it serves a functional purpose, including: - Documentation pages. - License keys. - Code snippets. - Input fields. - Text areas. - User-generated content intended for copying. ## Suggested Improvement Apply non-selectable behavior to static interface elements. ##Examples: ```css user-select: none; -webkit-user-select: none; -moz-user-select: none; ##Recommended targets: Hero sections Navigation components Marketing cards Demo labels Feature descriptions CTA buttons ##Exclude: Form fields Input controls Documentation content Support pages intended for text copying This would provide a cleaner and more professional user experience while reducing accidental text highlighting.
Sign in to join this conversation.