Open Bug 357703 Opened 19 years ago Updated 9 years ago

Chart too large - error is showing up only after clicking another format

Categories

(Bugzilla :: Reporting/Charting, defect)

2.22
defect
Not set
normal

Tracking

()

People

(Reporter: bigstijn, Unassigned)

References

()

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705; InfoPath.1) Build Identifier: Bugzilla 2.22 Chart too large - error is showing up only after clicking another format, not on the page where the error should have shown up. Reproducible: Always Steps to Reproduce: 1.Make a "large" report in table-format . I did choose vertical component, horizontal OS . (check url !) 2.This works nice, now, click on the "Bar" link. 3.You don't see anything, except an empty <img alt="Graphical report results" 4.Click on the "table" link 5.You get the error: "Sorry, but 2000 x 2000 is the maximum size for a chart." , and the links to table, .. are gone . Expected Results: the error: "Sorry, but 2000 x 2000 is the maximum size for a chart." is shown on the "bar"-page itself . When clicking on the table link, the table-page is shown like it was originally. (and, can you adjust those limitations about max size for a chart?)
Probably related to bug 185474, but not a duplicate, imho. This bug is about handling the error message once bug 185474 has occured.
There are a couple of issues here: - We don't put up a better error if the image ends up too large - The "Table" link has height and width parameters, which perhaps it shouldn't - Those parameters get validated, causing the error, even though they won't be used Still, the impact's not massive. Gerv
Assignee: gerv → charting
Still a problem in Bugzilla 3.7.1. It would probably be easy to validate the height and width of the image as they are passed to the URL.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → 2.22
(In reply to Frédéric Buclin from comment #3) > Still a problem in Bugzilla 3.7.1. And 5.0.3, was hitting it right now.
You need to log in before you can comment on or make changes to this bug.