Closed
Bug 945237
Opened 12 years ago
Closed 6 months ago
Pattern fill does not work on SVG elements with large offset
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: swieser, Unassigned)
Details
Attachments
(2 files)
gehtnit.png
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258
Steps to reproduce:
This SVG, embedded in an HTML page:
<html><svg version="1.1" width="45921.864039" height="113">
<defs><linearGradient id="aab" x1="0" y1="0" x2="0" y2="20" gradientUnits="userSpaceOnUse"><stop offset="0%" stop-color="#79A"></stop><stop offset="20%" stop-color="#BDE"></stop><stop offset="100%" stop-color="#79A"></stop></linearGradient><pattern id="aaa" x="0" y="0" width="17" height="20" viewBox="0 0 17 20" patternUnits="userSpaceOnUse"><rect x="0" y="0" width="17" height="20" fill="url(#aab)"></rect><circle cx="5" cy="18" r="6" fill="#EEF"></circle><circle cx="9" cy="19" r="6" fill="#EEF"></circle><circle cx="14" cy="18.5" r="5" fill="#EEF"></circle><circle cx="3" cy="16" r="3" fill="#EEF"></circle><circle cx="18" cy="16" r="2" fill="#EEF"></circle></pattern></defs>
<rect x="32000.460588" y="0" width="2335.0832999999984" height="21" stroke-width="1" stroke="#000" fill="url(#aaa)"></rect></svg></html>
Actual results:
The pattern is not shown (you need to scroll 32000 pixels to the left). Sometimes, if you scroll in and out, the pattern partially shows.
Expected results:
The pattern should be shown.
|
||
Updated•12 years ago
|
Component: Untriaged → SVG
Product: Firefox → Core
|
|
||
Comment 1•12 years ago
|
||
I'm not able to reproduce the issue, I have the same rendering as IE11 on Win 7. With HWA disabled, the black rectangle is empty, its content disapears.
> With HWA disabled, the black rectangle is empty, its content disapears.
> I'm not able to reproduce the issue
It's not supposed to be empty.
Congratulations, you have reproduced the bug.
So, I have wondering, since, you know, the bug has been open for a long time, "unconfirmed", despite users describing they are reproducing the bug ("the black rectangle is empty, its content disapears"), and despite users at the company I work at seeing the bug too:
When exactly does the bug get "confirmed", or even looked at?
I mean, I continuously read news on heise.de where exploits are quickly fixed after lingering seven years here on bugzilla. Sure, this is not exploitable, does that mean it'll take even longer than that? Like https://bugzilla.mozilla.org/show_bug.cgi?id=115199 , which is now 13 years old and still not fixed (it says "solved", but if you read the bug, you'll see it was misunderstood and something else was fixed. The original issue is still unfixed to date).
I mean, sure, I can workaround, but it's pretty sad that back then, when I filed the bug, I said to my colleagues, laughing, "sure, I'll file a bug, and knowing mozilla it'll take a few years to be fixed", and true to that, we're pretty much in July next year, and the bug (despite having a test case, and someone trying to shoot it down ("can't reproduce") actually confirms the bug by describing that the rectangle is empty) didn't even get as much as a glance.
At least bugzilla does a good job hiding those bugs from Google's index (searching for the full title gives nothing). I mean, it would look really bad if people could see the wealth of bugs that haven't been handled yet, so kudos.
|
||
Comment 5•11 years ago
|
||
It's all about priorities. We do things like consider whether we should spend time on bugs in large coordinate handling like in your testcase - which is rare in content - or fix things we know affect more users and content authors. Naturally we focus our limited resources on fixing the things that have the biggest negative impact, and that means that certain bugs may never be fixed. Sorry if that annoys you as much as it clearly does, but I think it's the right thing to do.
Status: UNCONFIRMED → NEW
Ever confirmed: true
|
||
Comment 6•9 years ago
|
||
I'd like to add that it is also the case even if you transform-translate the object to be well within your initial viewport.
| Comment hidden (offtopic) |
| Comment hidden (offtopic) |
|
|
||
Updated•8 years ago
|
Flags: needinfo?(aschen)
|
|
||
Updated•8 years ago
|
Flags: needinfo?(aschen)
|
||
Updated•3 years ago
|
Severity: normal → S3
|
|
||
Comment 9•6 months ago
|
||
Seems OK now.
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•