Closed
Bug 301846
Opened 19 years ago
Closed 19 years ago
visited link color does not change
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
People
(Reporter: agoldis, Assigned: mikepinkerton)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050721 Camino/0.9a2+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050721 Camino/0.9a2+ Link color does not change but instead a non-animated dotted line "marquee" is drawn around the link. Most apparent when using a page with lots of links, the bugzilla search page for example, and using the Back button to return to the page. However, if the link does not load immediately, you can observe the marquee and no color change on the original page. The marquee only remains around the most recently clicked link, and no link colors are changed. Reloading the page restores the correct link colors. Reproducible: Always Steps to Reproduce: 1. Load a page with at least one link. 2. Click a link. (If the link does not load immediately, you can observe the marquee and no color change.) 3. Use the Back button or keyboard command to return to the original page. Actual Results: No link color changes and a dotted line, non-animated "marquee" remains around the most recently clicked link. Expected Results: Changed color for visited links.
Comment 1•19 years ago
|
||
I'm not completely sure what you mean. I click on links here in Bugzilla and they change from blue to purple, showing they've been visited. Some sites may specify that the visited color and the regular color are the same color. Can you provide a specific link?
Comment 2•19 years ago
|
||
The link color has never changed to "visited" before the next page loads. Also, the link color still not being changed when you click "back" is (IIRC) a current side effect of bfcache (fastback).
(In reply to comment #2) > the link color still not being changed when you click "back" is (IIRC) a current > side effect of bfcache (fastback). Only in Firefox. They forked core code and fixed it prior to bfcache, but the code Camino and SeaMonkey use is still busted (you can verify by turning bfcache off). *** This bug has been marked as a duplicate of 78510 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Er, wait, I read that too fast and got confused. The reporter describes both bug 78510 and bug 293235 (the bfcache-back bug Wevah's comment mentions). Since bug 78510 is about to be fixed and is needed for bug 293235 to be fixed (and it should be fixed before Gecko branches for 1.8), I'm not going to change which bug this is duped to and create more bugspam. Sorry for the too-quick-read.
You need to log in
before you can comment on or make changes to this bug.
Description
•