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 015 files  + 46   3 015 suites  +46   2h 46m 2s ⏱️ + 14m 26s
 8 258 tests ±  0   8 010 ✅ +  2  248 💤 ±0  0 ❌  - 2 
23 598 runs  +262  22 807 ✅ +264  791 💤 ±0  0 ❌  - 2 

Results for commit 0c8d2ab. ± Comparison against base commit 8e47cc1.

♻️ This comment has been updated with latest results.

@danthe1st danthe1st force-pushed the set-visible-region-flickering branch from 6d4731e to 0c8d2ab Compare January 5, 2026 11:16
@danthe1st
Copy link
Contributor Author

danthe1st commented Jan 5, 2026

(only rebased/updated copyright headers, still waiting for re-review)

@danthe1st danthe1st requested a review from iloveeclipse January 5, 2026 11:20
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