When I load the reference case locally, I see: - a circular bullet appear, while the image is loading. - then, the image appears after it's loaded. I suspect that the 1px "fringe" here is some piece of the edge of the bullet that doesn't get invalidated correctly. (This is a bit odd because the fringe isn't where the bullet actually appears during the image load -- but I'm guessing that maybe the bullet moves + repaints just before the image gets painted, maybe [?]) So, I'll bet we could work around this by adding "list-style-type:none" to the reference case, but that might slightly defeat the point of the test (because the testcase effectively has "list-style-type:none" via a shorthand, and is seeing how it interacts with "list-style-image"). So, I feel a bit unethical making that edit to the test, given that it's a not a test that we wrote and it lives in a shared testsuite. So for now, until we can annotate tests as fuzzy, I feel like our only ethical course of action here is to just mark the test as random.
Bug 1383451 Comment 89 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When I load the reference case locally, I see: - a circular bullet appear, while the image is loading. - then, the image appears after it's loaded. I suspect that the 1px "fringe" here is some piece of the edge of the bullet that doesn't get invalidated correctly. (This is a bit odd because the fringe isn't where the bullet actually appears during the image load -- but I'm guessing that maybe the bullet moves + repaints just before the image gets painted, maybe [?]) So, I'll bet we could work around this by adding "list-style-type:none" to the reference case, but that might slightly defeat the point of the test (because the testcase effectively has "list-style-type:none" via a shorthand, and is seeing how it interacts with "list-style-image"). So, I feel a bit unethical making that edit to the test, given that it's a not a test that we wrote and it lives in a shared testsuite. So for now, until we can annotate tests as fuzzy, I feel like our only ethical course of action here is to just mark the test as disabled.