Closed Bug 1110496 Opened 10 years ago Closed 9 years ago

SVG-as-an-image is broken, when used as CSS border-image (slice 9), in 33 -> 34 Update

Categories

(Core :: Graphics: ImageLib, defect)

34 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla48
Tracking Status
firefox34 --- wontfix
firefox35 --- wontfix
firefox36 - wontfix
firefox37 - wontfix
firefox48 --- fixed

People

(Reporter: brent.dearth, Assigned: u459114)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

Attachments

(5 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.38 Safari/537.36 Steps to reproduce: Upgraded from 33.0.2 to 34.0.5 Actual results: Layout using buttons with SVG border image (CSS below) broke with rendering issues. Using a PNG fallback instead renders as expected. Screenshot attached. CSS: button { border-width: 9px 21px 9px 9px; border-image: url('../../assets/vectors/pointy_button_light_turquoise_border.svg') 9 21 9 9 fill stretch; box-shadow: none; background: none; margin-bottom: -3px; margin-top: 0px; position: relative; } Expected results: Continued to render border-images as with 33.0.2.
Attached image Sample SVG
It looks fine on my Win 7 machine. Maybe broken only on OSX?
Component: Untriaged → SVG
Product: Firefox → Core
Can you attach a proper testcase that shows the issue please?
Flags: needinfo?(brent.dearth)
I can confirm that this testcase (using the CSS from comment 0) changed its rendering between Firefox 33 & 34.
Flags: needinfo?(brent.dearth)
I'm guessing this behavior-change was a result of the image "Draw" API refactoring in bug 1043560; adding regressionwindow-wanted to confirm. I'm also not sure what the "correct" rendering is here (haven't dug into the exact border-image value & what it calls for), but FWIW, Chrome renders the testcase nicely and stretches the arrow to match the button-size, if you increase e.g. the button 'height' and/or 'width' properties.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
Hardware: x86 → All
[Tagging seth as probably the best person to look at this, if he has cycles for it.]
Component: SVG → ImageLib
Flags: needinfo?(seth)
Summary: SVG border-image broken (slice 9) in 33 -> 34 Update → SVG-as-an-image is broken, when used as CSS border-image (slice 9), in 33 -> 34 Update
FWIW SVG-as-image in border-image was broken in Firefox 33 as well. I realize that it's now broken more, but the implementation has never been correct. I'll try to find cycles for this but it probably won't be in the next few days.
Recent regression, tracking.
Too late in the 35 cycle for speculative fixes and we're doing our last beta today.
(bug 619500 covers previous problems with SVG border-images)
As discussed by email with Seth, he believes that it is not critical bug since it was always broken. Stop tracking!
FWIW, even if this was somewhat broken in 33, it was not evident in this test case from a user perspective. For all intents and purposes, this test case was working as expected prior to 34.
(In reply to brent.dearth from comment #14) > FWIW, even if this was somewhat broken in 33, it was not evident in this > test case from a user perspective. For all intents and purposes, this test > case was working as expected prior to 34. Yes, even though SVG-as-image in border-image has always been broken, I agree that this particular test case has regressed. I am still going to fix this regression. I am mainly trying to avoid a situation where I am forced to implement a new feature (correct support for SVG-as-image in border-image, which we have never had) as a critical regression fix. Without investigating the issue, it's unclear whether a small fix is sufficient, or whether to fix this correctly we really need to fix SVG-as-image in border-image as a whole. That's something we need to do anyway, of course, and it's something we will do, but the process we need to follow there is different from the process we'd follow for something that was just a small patch to fix a regression.
See Also: → 619500
Seth, is this issue still on your radar? Is there anything left to do here outside of bug 619500?
Should be fixed after bug 619500 landed. The same root cause -- can not handle SVG-boder-image with viewBox correctly.
Depends on: 619500
Based on comment 18, this bug will be fixed along with bug 619500. Tested on latest m-c build[1] and problem was fixed. Change status to resolved. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=619500#c83
Assignee: nobody → cku
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(seth)
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: