Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows] Add warning about activating "Monitor-specific UI scaling" in preferences dialog #2518

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fedejeanne
Copy link
Contributor

@fedejeanne fedejeanne commented Nov 14, 2024

[Windows only!]

Since the flickering issue (eclipse-platform/eclipse.platform.swt#1122) is still open and activating this option also sets Edge as the browser of choice, the user should be warned.

This is the new warning:

image

@fedejeanne
Copy link
Contributor Author

@HeikoKlare since you made the N&N about the new setting (eclipse-platform/www.eclipse.org-eclipse#243), can you please propose a PR to adapt the screenshot? I have a different windows theme and it wouldn't look good in the N&N

@laeubi
Copy link
Contributor

laeubi commented Nov 14, 2024

Would a link to the N&N not being better than clutter the UI with more an more text ... the more text the more unlikely it getting actually read.

Copy link
Contributor

github-actions bot commented Nov 14, 2024

Test Results

 1 514 files   -   307   1 514 suites   - 307   1h 26m 46s ⏱️ - 30m 44s
 7 725 tests ±    0   7 496 ✅ ±    0  229 💤 +  1  0 ❌  - 1 
22 490 runs   - 1 846  21 942 ✅  - 1 646  548 💤  - 199  0 ❌  - 1 

Results for commit 4fe1e47. ± Comparison against base commit 69f6e45.

This pull request skips 1 test.
UiTestSuite org.eclipse.ui.tests.api.ApiTestSuite org.eclipse.ui.tests.api.WorkbenchPluginTest ‑ testGetImageRegistryFromAdditionalDisplay

♻️ This comment has been updated with latest results.

@fedejeanne
Copy link
Contributor Author

Would a link to the N&N not being better than clutter the UI with more an more text ... the more text the more unlikely it getting actually read.

Who's to say someone would click on a link and wait for the browser to render something if he/she wouldn't even read some text that's right in front of them and starts with a big WARNING!.

@laeubi
Copy link
Contributor

laeubi commented Nov 14, 2024

Who's to say someone would click on a link and wait for the browser to render something if he/she wouldn't even read some text that's right in front of them and starts with a big WARNING!.

There is no guarantee, but a short

Read the following carefully ...some link ...

is likely getting more attention than a long text... also such text can be enhanced after the release.

And honestly if it is that dangerous that we now need two big WARNING message (actually it is not bold in the screenshot ...), we better should not ship this feature to the user at all. It is already mentions to be experimental, so either user want this then they don't care about some glitches, or the don't but adding multiple warnings, danger, don't click this does not feel right to let user make a good decision.

We have had some of such experimental switches already ere and there, and none of them have more than a few words.

@HeikoKlare
Copy link
Contributor

I have to admit that I am not an expert in when flickering might be problematic for people sensitive to it. But note that the issue is not an unavoidable, automated flickering. It only happens when resizing a browser window and it only happens as long as you do a resizing operation, so once you release the mouse button or stop moving the mouse, the flickering stops as well. And you experience the same with other embedded applications like Word, Excel etc. in an Eclipse IDE as well, but probably not so many people use those capabilities.

That said, I appreciate the awareness for this and we should definitely think about whether and where to place that information. I agree with @laeubi that we now have quite too much text (and particular, too many paragraphs) and too much "experimental" and "warning" in the box that may prevent people from using the feature. In my opinion, we could still integrate the information but just as an additional sentence to the existing description of the "experimental" paragraph. Adding a sentence like this at the end might be sufficient: "Note that the usage of Edge may currently lead to flickering when resizing a browser window."

@fedejeanne fedejeanne force-pushed the warn_about_edge_when_using_rescaling_at_runtime branch from 54ccb16 to 9c2195b Compare November 14, 2024 14:22
@fedejeanne
Copy link
Contributor Author

Then how about less "EXPERIMENTAL" and more focus on the WARNING?

image

@HeikoKlare
Copy link
Contributor

Then how about less "EXPERIMENTAL" and more focus on the WARNING?

The purpose of the additional text is to notify that the feature is experimental, i.e., we know that it is had glitches and is not ready to be enabled by default, but we consider it useful for testing and maybe even productive use if remaining glitches are individually acceptable. Now just adding the new warning text about the Edge glitch and removing every information about the feature itself and in total being experimental is not what the text is supposed to say.

@fedejeanne fedejeanne force-pushed the warn_about_edge_when_using_rescaling_at_runtime branch from 9c2195b to 493314d Compare November 15, 2024 07:02
@fedejeanne
Copy link
Contributor Author

Then how about:

image

?

Less clutter in the "EXPERIMENTAL" part and a link in the "WARNING"

@fedejeanne
Copy link
Contributor Author

BTW requesting PMC approval to merge this once the text is proper @merks / @akurtakov

@HeikoKlare
Copy link
Contributor

Could we please just have a simple solution for this?

Less clutter in the "EXPERIMENTAL" part and a link in the "WARNING"

My concern remains:

that we now have quite too much text (and particular, too many paragraphs) and too much "experimental" and "warning" in the box that may prevent people from using the feature

I propose to keep the existing paragraph (if possible, even shorten it) without any additional "WARNING" or the like and just add one simple sentence without references to issues, potential seizures etc.. When you mention that things may flicker, people sensitive to that will consider not using that functionality anyway without requiring a verbose explanation in the preferences.

@fedejeanne
Copy link
Contributor Author

I propose to keep the existing paragraph (if possible, even shorten it) without any additional "WARNING" or the like and just add one simple sentence without references to issues, potential seizures etc.. When you mention that things may flicker, people sensitive to that will consider not using that functionality anyway without requiring a verbose explanation in the preferences.

I disagree: the word "seizures" should be in it. We must be open about the possible implications, regardless of how low the chances are that someone may get seizures from it.

Would you like to propose a final text? Please explicitly warn about possible seizures, something like "may cause seizures". Skip the "WARNING" if you want.

@HeikoKlare
Copy link
Contributor

I disagree: the word "seizures" should be in it. We must be open about the possible implications, regardless of how low the chances are that someone may get seizures from it.

With this argumentation, we would need to have a disclaimer when starting/downloading Eclipse, because, as said, when opening other embedded applications inside Eclipse (like MS Office products), you have the same flickering and no one warns you about that. Don't get me wrong: it's good to discuss this and ensure that we provide a proper information about this. But as said, I consider a warning that there might be flickering enough for people who may be sensitive to it to decide whether they want to take the risk or not. I cannot even say whether this kind of flickering may cause seizures, so I would just make that statement about flickering without judging about potential consequences.

My proposal remains that I would add something simple to the existing paragraph like: "Note that the usage of Edge may currently lead to flickering when resizing a browser window." (#2518 (comment))

Since I have not seen any reasonable arguments to further clutter the dialog with more verbose statements so far, I do not agree with any more complicate statement. If someone else has a different opinion, feel free to overrule me.

@fedejeanne fedejeanne force-pushed the warn_about_edge_when_using_rescaling_at_runtime branch from 493314d to 50c8966 Compare November 15, 2024 09:40
@fedejeanne
Copy link
Contributor Author

My proposal remains that I would add something simple to the existing paragraph like: "Note that the usage of Edge may currently lead to flickering when resizing a browser window." (#2518 (comment))

A full text from you would have been better but I assume you meant (original text + 1 sentence):

image

... not my first choice but I can live with a slightly modified version of it:

image

It has your sentence, the word "seizures" (my preference) and a link for more details (Christoph's request).

I hope I hit the middle-ground and we can all accept this proposal, @HeikoKlare and @laeubi ?

@fedejeanne
Copy link
Contributor Author

I assume the current text is fine since there have been no objections/proposals in the past days.

@merks / @akurtakov requesting PMC approval to merge for RC2

@HeikoKlare
Copy link
Contributor

I assume the current text is fine since there have been no objections/proposals in the past days.

As said in my previous comment, I object to the current proposal.

@merks
Copy link
Contributor

merks commented Nov 19, 2024

I tend agree with Heiko. Personally, I think that people who are susceptible to seizures induced by flickering will be well aware of that fact and that we don't need to scream this out to every reader...

@fedejeanne fedejeanne force-pushed the warn_about_edge_when_using_rescaling_at_runtime branch from 50c8966 to b5f9bb7 Compare November 19, 2024 09:00
Add a warning about flickering effects caused by the Edge browser under
Preferences > General > Appearance.

Co-authored-by: Christoph Läubrich <[email protected]>
@fedejeanne fedejeanne force-pushed the warn_about_edge_when_using_rescaling_at_runtime branch from b5f9bb7 to 4fe1e47 Compare November 19, 2024 09:03
@fedejeanne
Copy link
Contributor Author

Majority has spoken. I changed the text.

@fedejeanne
Copy link
Contributor Author

Failing test is unrelated: #195

@merks may I merge this?

@akurtakov
Copy link
Member

So the edge warning will be shown on mac/linux too? It sounds not useful and overwhelming.

@fedejeanne
Copy link
Contributor Author

So the edge warning will be shown on mac/linux too? It sounds not useful and overwhelming.

It remains a Windows-only thing, nothing changed in that sense:

private void createHiDPISettingsGroup(Composite parent) {
if (!OS.isWindows()) {
return;
}

@fedejeanne fedejeanne changed the title Add warning about activating "Monitor-specific UI scaling" in preferences dialog [Windows] Add warning about activating "Monitor-specific UI scaling" in preferences dialog Nov 19, 2024
@fedejeanne fedejeanne added the Windows Happens on Windows OS label Nov 19, 2024
@fedejeanne
Copy link
Contributor Author

Today is the last stabilization day for RC2 and tomorrow is the signoff (calendar).

Do you think it would be possible to merge today or do you see any blockers, @merks and @akurtakov ? Anything I should do?

@akurtakov
Copy link
Member

I am not a fan of such kind of messages in preferences but it all depends on the "severity" of the issue .
As I don't have access to windows at all I don't feel qualified to have the say here and defer to the rest of the @eclipse-platform/eclipse-platform-project-leads and/or PMC to have a say here.

@fedejeanne
Copy link
Contributor Author

I am not a fan of such kind of messages in preferences but it all depends on the "severity" of the issue . As I don't have access to windows at all I don't feel qualified to have the say here and defer to the rest of the @eclipse-platform/eclipse-platform-project-leads and/or PMC to have a say here.

Understood. Thank you for the feedback.

FTR I added another way to reproduce the flickering to the original issue (eclipse-platform/eclipse.platform.swt#1122): the JavaDoc view flickers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Windows Happens on Windows OS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants