Closed
Bug 771935
Opened 12 years ago
Closed 12 years ago
SVGs that are larger than the browser content area should scroll
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
FIXED
mozilla16
People
(Reporter: jwatt, Assigned: jwatt)
References
Details
(Keywords: regression)
Attachments
(1 file)
4.74 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
SVG files that take up an area larger than the browser content area should scroll, but the change to svg.css in the patch for bug 769645 has broken that. The reason for that change was to prevent SVGs that are smaller than the viewport from painting outside their content area (needed for backwards compatibility), but I think the value that we really need is 'scroll', not 'hidden'. I need to run some tests to check that both fixes this bug and keeps us backwards compatible, but if it works I'll attach a patch.
Assignee | ||
Comment 1•12 years ago
|
||
No, using: svg:root { overflow: scroll; } in svg.css doesn't work since it causes SVG files embedded using <embed> to get scrollbars when they didn't previously. For example, the references for the following two tests are given scrollbars when they should not be: reftests/svg/as-image/zoom/img-zoomIn-1.html reftests/svg/as-image/zoom/img-zoomOut-1.html
Assignee | ||
Comment 2•12 years ago
|
||
Let's just go back to clipping without checking IsScrollableOverflow(), as we used to, but still using the nsDisplayClip to do the clipping. Right now I don't have any more time to spend on this, so I'll look into giving users more clipping control in bug 378923 later.
Attachment #640102 -
Flags: review?(roc)
Attachment #640102 -
Flags: review?(roc) → review+
Assignee | ||
Comment 3•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/43993f45c328
Target Milestone: --- → mozilla16
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/43993f45c328
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•