Skip to content

Conversation

@danthe1st
Copy link
Contributor

@danthe1st danthe1st commented Oct 26, 2025

When setVisibleRegion is repeatedly called with projection regions enabled, it first expands everything outside of the old visible region and then collapses everything inside the new visible region. This can result in Eclipse showing unwanted text for a fraction of a second.

Without this change:

Screencast_20251026_113947.webm

With this change:

Screencast_20251026_114117.webm

(I made the recordings with eclipse-jdt/eclipse.jdt.ui#2302 active to get the visible regions logic in JDT)

I don't think an automated test is reasonable for this but I can try to provide a way to reproduce this manually without JDT if necessary.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 26, 2025

Test Results

 3 018 files  ±0   3 018 suites  ±0   2h 31m 6s ⏱️ + 8m 2s
 8 234 tests ±0   7 985 ✅ ±0  249 💤 ±0  0 ❌ ±0 
23 622 runs  ±0  22 828 ✅ ±0  794 💤 ±0  0 ❌ ±0 

Results for commit bac8d3d. ± Comparison against base commit 3a441d9.

♻️ This comment has been updated with latest results.

@danthe1st danthe1st force-pushed the set-visible-region-flickering branch from 4f15c45 to c46953f Compare November 1, 2025 14:30
@danthe1st danthe1st force-pushed the set-visible-region-flickering branch from c46953f to bac8d3d Compare November 1, 2025 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants