SVG handling does not work any longer

RESOLVED FIXED

Status

()

Core
SVG
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: Armin Müller, Unassigned)

Tracking

({regression})

Trunk
x86
Windows Vista
regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2

if you click on the legend to check or uncheck the layers, this does not work correctly.
In FF2 and FF3 Beta1 and FF3 Beta2 Gecko/2007111304, Opera9.x and IE with ASV you have a correct handling.

You can test it with other examples on http://www.mapviewsvg.com/examples/ all are working bad now. But only the legend all other things are ok 

Reproducible: Always

Steps to Reproduce:
1. click on one of the x buttons in the legend
2. the handling is not correct
3.
Actual Results:  
layer is not switched off
the handling in the legend part is not correct (please see FF2 for correct handling)

Expected Results:  
The result should be the same you see when using FF2 or FF3 Beta1 or FF3 Beta2 Gecko/2007111304, Opera9.x or IE with ASV
Strictly, this is a regression from bug 401112. 
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=1196700240&maxdate=1196702459
(There was a kind of performance problem before it regressed. I see the delay also in Firefox 2, but drawing is handled less elegant in trunk. But this issue is probably a different bug.)
Blocks: 401112
Status: UNCONFIRMED → NEW
Component: General → SVG
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → Trunk
Perhaps the patch in bug 406985 would fix it.
As I thought, the patch in bug 406985 does fix it.
Depends on: 406985

Updated

11 years ago
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.