Closed Bug 267722 Opened 21 years ago Closed 21 years ago

failure to use style within element disables change of css style via script.

Categories

(Core :: SVG, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jay, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041102 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041102 onmouseover the graphic should provide a highlight. please note this doesn't work in asv3. however I can see no reason for this behaviour. Reproducible: Always Steps to Reproduce: 1.open file 2.mouseover graphic 3. Actual Results: nothing Expected Results: highlight 'border' displayed with changed stroke-width compare with http://peepo.co.uk/temp/css-script.svg an identical file, but with style attributes in the element, which works in mozSVG. If the style attributes are in a class this still won't work because of another bug. surely the default style attributes are present and sufficient?
I'm marking this as a duplicate of bug 267713. Please comment there about the changes you made between the report for that bug and this one. *** This bug has been marked as a duplicate of 267713 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Does it matter that the "inline" version never sets "stroke"? If I set it (either in the JS or on the node itself), I get a highlight.
Boris, can't make sense of your comment. the example code includes a javascript change of attribute, which does not occur. (apparently because the attribute is not used inline) so yes it does matter, otherwise the whole purpose of classes is being rejected, and this could result in significant bloatware.
> can't make sense of your comment. You have two testcases. You claim: compare with http://peepo.co.uk/temp/css-script.svg an identical file, but with style attributes in the element, which works in mozSVG. This claim is manifestly false, since one file sets the "stroke" property and the other one does not. Hence there are differences between the files other than the use or not use of CSS. Now I don't know SVG well enough to know whether leaving out "stroke" would have an effect on the testcase. So I guess I'm going to have to go and read the spec here.... I was rather hoping that I wouldn't have to waste time doing that... http://www.w3.org/TR/SVG11/painting.html#StrokeProperty says: Initial: none So since you're not setting "stroke", its value is "none", and "stroke-width" doesn't do anything. Marking invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → INVALID
Boris, you do seem to have got out of bed on the wrong side. cheers, and apologies for what is in this instance an invalid bug.
You need to log in before you can comment on or make changes to this bug.