Skip to content

Conversation

@Suchitainf
Copy link
Collaborator

@Suchitainf Suchitainf commented Aug 26, 2024

This PR is to fix the accessibility issue for High Contrast mode. Stracktrace View was not readable at all in dark mode.

Before the fix:
image

After the fix:
image


Progress

  • Commit message must refer to an issue
  • Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

  • JMC-8248: [Accessibility] Low Contrast in High Contrast mode on Stacktrace View (Bug - P4)

Reviewers

Contributors

  • Marcus Hirt <hirt@openjdk.org>

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc.git pull/580/head:pull/580
$ git checkout pull/580

Update a local copy of the PR:
$ git checkout pull/580
$ git pull https://git.openjdk.org/jmc.git pull/580/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 580

View PR using the GUI difftool:
$ git pr show -t 580

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/580.diff

Webrev

Link to Webrev Comment

…e View

Co-authored By: Marcus Hirt <hirt@openjdk.org>
@bridgekeeper
Copy link

bridgekeeper bot commented Aug 26, 2024

👋 Welcome back schaturvedi! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Aug 26, 2024

@Suchitainf This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8248: [Accessibility] Low Contrast in High Contrast mode on Stacktrace View

Co-authored-by: Marcus Hirt <hirt@openjdk.org>
Reviewed-by: aptmac, bdutheil

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@mlbridge
Copy link

mlbridge bot commented Aug 26, 2024

Webrevs

}

private static final String HELP_CONTEXT_ID = FlightRecorderUI.PLUGIN_ID + ".StacktraceView"; //$NON-NLS-1$
private static final Boolean IS_DARK_MODE = ThemeUtils.isDarkMode();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: I would avoid the static final there, I think the themes can be dynamic, i.e. change without restarting ? If that's not the case maybe it can be in the future.

See the the comment on ThemeUtils to see a different approach.

@thegreystone thegreystone requested review from Gunde and aptmac August 28, 2024 17:24
@Suchitainf
Copy link
Collaborator Author

/contributor add @thegreystone

@openjdk
Copy link

openjdk bot commented Sep 13, 2024

@Suchitainf
Contributor Marcus Hirt <hirt@openjdk.org> successfully added.

Copy link
Member

@aptmac aptmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brice has a good point here, applying themes can be dynamic so IS_DARK_MODE needs to be able to be updated.

@Suchitainf
Copy link
Collaborator Author

Hi @bric3 & @aptmac , I have implemented the suggested change. I have also added the property listener in the static block. There is no issue with the eclipse development environment. I have tried to build JMC outside also and the build is working perfectly fine. But seems like spotbugs is not happy with updating static variable isCurrentThemeDark from the listener. Hence, there are test failures due to that. Please have a look at the changes and let me know if I am missing something.

Hope I understood the suggestion clearly and implemented accordingly.

@Suchitainf Suchitainf requested review from aptmac and bric3 September 15, 2024 11:49
@openjdk
Copy link

openjdk bot commented Sep 16, 2024

⚠️ @Suchitainf This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch> where <project> is the name of another project in the OpenJDK organization (for example Merge jdk:master).

@Suchitainf Suchitainf requested a review from bric3 September 16, 2024 08:34
@openjdk openjdk bot added the ready label Sep 16, 2024
@Suchitainf
Copy link
Collaborator Author

Thanks @bric3 for approving the changes.

@aptmac Can you please take a look now? I need one reviewer's approval before integrating the changes. Thanks in advance.

@Suchitainf
Copy link
Collaborator Author

/integrate

@openjdk
Copy link

openjdk bot commented Sep 16, 2024

Going to push as commit 8c67664.

@openjdk openjdk bot added the integrated label Sep 16, 2024
@openjdk openjdk bot closed this Sep 16, 2024
@openjdk
Copy link

openjdk bot commented Sep 16, 2024

@Suchitainf Pushed as commit 8c67664.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants