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.

Sign up for GitHub

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

Jump to bottom

Handle algorithm screenshot resizing within documentation more intelligently #10456

Closed
martyngigg opened this issue Jun 9, 2014 · 1 comment
Closed

Handle algorithm screenshot resizing within documentation more intelligently #10456

martyngigg opened this issue Jun 9, 2014 · 1 comment
Assignees
@martyngigg
Labels
Documentation Issues and pull requests related to documentation High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Release 3.2

Comments

@martyngigg
Copy link
Member

We currently set an arbitrary width for the generated screen shot images in the documentation, which allows a clickable link to be generated. Some images however are smaller and could just have the image with the correct width.

We should set a maximum allowed width and only use this width if the actual size of the image is larger.
@martyngigg
Copy link
Member Author

This issue was originally trac ticket 9613

@martyngigg martyngigg added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Documentation Issues and pull requests related to documentation labels Jun 3, 2015
@martyngigg martyngigg self-assigned this Jun 3, 2015
@martyngigg martyngigg added this to the Release 3.2 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martyngigg martyngigg

Labels
Documentation Issues and pull requests related to documentation High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Milestone
Release 3.2
Development

No branches or pull requests
1 participant
@martyngigg