A more accurate bug summary is: If the clip rects left or top edge causes the polygon to be clipped away completely, a non-empty polygon is returned which ignores that left or top clip edge. (The left edge's clipping plane is stored in `planeNormals[0]`, the top edge's clipping plane is stored in `planeNormals[2]`, and the bug only appears if the loop is exited at plane index 0 or 2.
Bug 1578045 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
A more accurate bug summary is: If the clip rect's left or top edge causes the polygon to be clipped away completely, a non-empty polygon is returned which ignores that left or top clip edge. (The left edge's clipping plane is stored in `planeNormals[0]`, the top edge's clipping plane is stored in `planeNormals[2]`, and the bug only appears if the loop is exited at plane index 0 or 2.
A more accurate bug summary is: If the clip rect's left or top edge causes the polygon to be clipped away completely, a non-empty polygon is returned which ignores that left or top clip edge. (The left edge's clipping plane is stored in `planeNormals[0]`, the top edge's clipping plane is stored in `planeNormals[2]`, and the bug only appears if the loop is exited at plane index 0 or 2.)
A more accurate bug summary is: If the clip rect's left or top edge causes the polygon to be clipped away completely, a non-empty polygon is returned which ignores that left or top clip edge, and also includes the point (0, 0). (The left edge's clipping plane is stored in `planeNormals[0]`, the top edge's clipping plane is stored in `planeNormals[2]`, and the bug only appears if the loop is exited at plane index 0 or 2. And the wrongly constructed range of points happens to include all 32 points in points[0], which usually include ones that have been default-initialized to (0, 0) by the Point4D constructor.)