Hide fully transparent latex text in PS output #21470
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This PR closes #21466. It is a follow-up fix for #10166.
The PS backend initially rendered transparent text, which was not visible in other backends (e.g. PDF). #101166 fixed this for regular text but missed fixing this when using latex to render text. This PR fixes the problem for latex.
In #21466 @anntzer proposed to add a
@pytest.mark.parametrize()
decorator totest_transparency()
. However, I think duplicating the test is the better approach here, as we also need the@needs_usetex
decorator. this would result in the test not being run anymore when latex is missing which would be a step back.However, if you think it is fine that the test is only run when latex is installed, we can change to
@pytest.mark.parametrize()
. I tried this already but had the additional problem that the test would be green regardless of the fix being applied (this is either me being stupid or@image_comparison()
not working with additional decorators).PR Checklist
pytest
passes).flake8
on changed files to check).flake8-docstrings
and runflake8 --docstring-convention=all
).doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).