Closed
Bug 814235
Opened 12 years ago
Closed 10 years ago
svg Firefox 17 filters fail further
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: Annon0m0s, Assigned: jwatt)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
(deleted),
image/svg+xml
|
Details |
Displayed an existing svg from a file which mostly worked in Firefox 16. The svg is a simple example of the output of using the python svgwrite package.
The svg is incorrectly displayed. Three of the filter areas did not show properly.
They areas should show the svg filter as described in the svg standards. At least they should not have gotten worse than Firefox 16. In Firefox 16 the bottom of the screen would not display correctly when the page was scrolled but would display if Ctrl-0 was pressed. The svg displays correctly in Google docs. (Likely not needed but further python svgwrite examples are at https://docs.google.com/folder/d/0BwFQiTKfux0qY1Y2d1hRdndtSEk/edit ). I would prefer not to have to get IE10 when it comes out to get the best browser for svg standard filters.
Updated•12 years ago
|
Component: General → SVG
Product: Firefox → Core
Comment 1•12 years ago
|
||
Rendering seems fine in Firefox 14. In 15 and 16, interestingly, the filter effect disappears if you click on the text. And then in 17 it doesn't display initially at all.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Windows 7 → All
Hardware: x86_64 → All
It's a regression since Firefox 15. The rendering is various between June and July, and now in FF17, example #2 loses its black text if you click on it, example #3 has invisible black text (with Gaussian blur), #4 and #5 are invisible.
m-c
good=2012-05-17
bad=2012-05-18
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=762e95608da3&tochange=e794cef56df6
Suspected bug:
Jonathan Watt — Bug 734082 - Compute and store bounds and visual overflow bounds for both SVG leaf and container frames. r=roc.
Version: 17 Branch → 15 Branch
Updated•12 years ago
|
Assignee: nobody → jwatt
Comment 3•11 years ago
|
||
This is an issue with <use> presenting the wrong bounding box I think. If you avoid <use> in the testcase the filters work.
Comment 4•10 years ago
|
||
Seems to work now
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•