Steps to reproduce:
[Testcase attached in a bit, listing js here doesn't make sense]
Big green line
You can see a big green line if you change the last lineTo call to a moveTo call instead, or make the coordinates smaller.
I'm setting severity normal because I don't know if many people will experience this. I have a problem with it because I'm making an extension to render math functions, and I didn't exactly expect to have to implement my own magic not to display items outside the viewport...
Note that in this case, the coordinate number used is rather large. It *seems* that as a path has more nodes, the size of the coordinate number required to make the path vanish decreases.
I'm wondering if a keyword 'dataloss' is appropriate here or not. I'm not experienced in filing Core bugs, if someone else (more experienced than me in the subject at hand) thinks it is, please add it.
db48x reproduced this on linux with trunk from 'a day or two ago'. Marking Platform/OS all. Maybe this is a cairo problem?
Created attachment 207517 [details]
eh. Linux reproduction build used was
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051220 Firefox/1.6a1
I reproduced on a Windows 1.5 release build:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
and current trunk:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060104 Firefox/1.6a1
Found the green line in the 1.9a1_2005081922 build but it was gone in the 1.9a1_2005082008 build.
Created attachment 219075 [details]
Better testcase; the problem is that coordinates that are too large I think overflow the 16.16 internals inside cairo, and cause segments to not get rendered.
Vlad: so if this is a Cairo problem, do 'we' have anything to fix and/or does a new version of Cairo (plan to) fix this problem?
FWIW, still broken on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061121 Minefield/3.0a1
But I suppose that's sorta expected...
It's nothing that we can really fix; there is some upstream cairo work going on in this area, but noone's tackled this yet. Chances are that it probably won't get fixed anytime soon though, but we'll see.
Fixed by bug 384681, at least getting us to 24.8.
(In reply to comment #7)
> Fixed by bug 384681, at least getting us to 24.8.
So my testcase now works, but yours doesn't... (3.5.5) What am I missing? :-)