Open
Bug 560089
Opened 14 years ago
Updated 2 years ago
Acid3: "YOU SHOULD NOT SEE THIS AT ALL" appears
Categories
(Core :: General, defect)
Tracking
()
NEW
People
(Reporter: laurent, Unassigned)
References
Details
(Whiteboard: invalid?)
In the acid3 test, a red message "YOU SHOULD NOT SEE THIS AT ALL" appears at top-left corner of the page, and disappears before the end of the test. I never see it before (and does not appear in firefox 3.6.3) The issue appears at least in nightlies after 2010-02-28-03-mozilla-central. I didn't test on older nightlies.
Comment 1•14 years ago
|
||
> and disappears before the end of the test. The test is making assumptions about how :visited works that are invalid. See bug 461199 comment 268. I was pretty sure we had a bug on this already...
Blocks: async-visited-check
Whiteboard: invalid?
Comment 2•14 years ago
|
||
It used to say "LINKTEST FAILED", not "YOU SHOULD NOT SEE THIS AT ALL" and it was at the bottom. dbaron said he was going to get in touch with hixie about it since his changes would break it further if I recall correctly.
Hixie fixed the issue that my changes broke it further; this is the issue that the lookup is asynchronous.
Comment 4•14 years ago
|
||
(In reply to comment #3) > Hixie fixed the issue that my changes broke it further; this is the issue that > the lookup is asynchronous. So now it is testing that lookups are synchronous?
Wasn't the "LINKTEST FAILED" text flashing before? Are you saying that the change in text is intended to imply that it can't flash briefly?
Comment 6•14 years ago
|
||
(In reply to comment #5) > Wasn't the "LINKTEST FAILED" text flashing before? Are you saying that the > change in text is intended to imply that it can't flash briefly? That's my guess (I cannot say what Hixie has in mind for it for sure). That text never existed before (it used to be the LINKTEST FAILED).
Comment 7•13 years ago
|
||
"YOU SHOULD NOT SEE THIS AT ALL" doesn't appear with Fx7.0.1 Linux, but remains visible with today's Fx8b6.
Comment 8•12 years ago
|
||
Can anybody reproduce this bug?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•