Skip to content

fix(v1.2.1): extension not working on Edge browser due to DOM timing#5

Merged
AhmedV20 merged 1 commit intomainfrom
fix/edge-browser-timing-issue
Jan 28, 2026
Merged

fix(v1.2.1): extension not working on Edge browser due to DOM timing#5
AhmedV20 merged 1 commit intomainfrom
fix/edge-browser-timing-issue

Conversation

@AhmedV20
Copy link
Owner

Problem

Extension fails to activate on Microsoft Edge browser because Edge injects content scripts slower than Chrome. The isRepositoryPage()
function relies on finding a DOM navigation element (.UnderlineNav-item or .reponav-item), but on Edge this element may not be present when the script runs.

Solution

  • Increased INJECTION_TIMEOUT from 500ms → 1000ms to give Edge more time to load
  • Added URL pattern fallback validation when DOM check fails
  • Logs a debug message when falling back to URL pattern

Testing

  • Tested on Edge: extension now activates correctly
  • No impact on Chrome/Firefox behavior

  Edge browser injects content scripts slower than Chrome, causing the DOM
  navigation element check to fail before the page fully loads.

  Changes:
  - Increase INJECTION_TIMEOUT from 500ms to 1000ms to give Edge more time
  - Add URL pattern fallback in isRepositoryPage() for when DOM check fails
  - This ensures extension works even if GitHub DOM isn't ready yet
@AhmedV20 AhmedV20 self-assigned this Jan 28, 2026
@AhmedV20 AhmedV20 added bug Something isn't working release Release related labels Jan 28, 2026
@AhmedV20 AhmedV20 merged commit b7e2018 into main Jan 28, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working release Release related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant