-
Notifications
You must be signed in to change notification settings - Fork 189
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
base: master
Are you sure you want to change the base?
Conversation
@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 |
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. |
Test Results 1 514 files - 307 1 514 suites - 307 1h 26m 46s ⏱️ - 30m 44s Results for commit 4fe1e47. ± Comparison against base commit 69f6e45. This pull request skips 1 test.
♻️ This comment has been updated with latest results. |
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
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 We have had some of such experimental switches already ere and there, and none of them have more than a few words. |
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." |
54ccb16
to
9c2195b
Compare
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. |
9c2195b
to
493314d
Compare
BTW requesting PMC approval to merge this once the text is proper @merks / @akurtakov |
Could we please just have a simple solution for this?
My concern remains:
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. |
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. |
493314d
to
50c8966
Compare
A full text from you would have been better but I assume you meant (original text + 1 sentence): ... not my first choice but I can live with a slightly modified version of it: 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 ? |
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 |
As said in my previous comment, I object to the current proposal. |
.../org.eclipse.ui.workbench/eclipseui/org/eclipse/ui/internal/dialogs/ViewsPreferencePage.java
Outdated
Show resolved
Hide resolved
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... |
50c8966
to
b5f9bb7
Compare
Add a warning about flickering effects caused by the Edge browser under Preferences > General > Appearance. Co-authored-by: Christoph Läubrich <[email protected]>
b5f9bb7
to
4fe1e47
Compare
Majority has spoken. I changed the text. |
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: Lines 202 to 205 in 69f6e45
|
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? |
I am not a fan of such kind of messages in preferences but it all depends on the "severity" of the issue . |
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. |
[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: