minor styling change

[iceljc]

PR Type

Enhancement

---

Description

• Add active state styling for links with reset properties

• Prevent visual feedback on link activation using !important

• Ensure consistent appearance across all link interaction states

---

Diagram Walkthrough

flowchart LR
  A["Link element"] -- "hover state" --> B["Remove underline and background"]
  A -- "active state" --> C["Reset all visual properties with !important"]
  C -- "properties reset" --> D["background, shadow, outline, decoration, transform"]

Loading

File Walkthrough

	Relevant files
Enhancement	_common.scss Add active state link styling with property resets              src/lib/scss/custom/common/_common.scss Added new &:active pseudo-class selector for link styling Applied !important flag to reset background, box-shadow, outline, text-decoration, and transform properties Prevents unwanted visual effects during link activation +8/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Not Applicable Scope: The PR only adds CSS styling for link active states and does not introduce or modify any application logic where audit trails would apply. Referred Code &:active { background: none !important; box-shadow: none !important; outline: none !important; text-decoration: none !important; transform: none !important; } Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Not Applicable Scope: The changes are limited to CSS selectors and do not introduce error handling paths or edge-case logic to evaluate. Referred Code &:active { background: none !important; box-shadow: none !important; outline: none !important; text-decoration: none !important; transform: none !important; } Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Avoid using !important for styling Avoid using !important in the &:active block. Instead, address potential CSS specificity issues to make the styles more maintainable and predictable. src/lib/scss/custom/common/_common.scss [221-227] &:active { - background: none !important; - box-shadow: none !important; - outline: none !important; - text-decoration: none !important; - transform: none !important; + background: none; + box-shadow: none; + outline: none; + text-decoration: none; + transform: none; } Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies the use of !important as a potential code smell that harms maintainability, which is a valid and important concern for CSS architecture.	Low
More