Closed
Bug 1098262
Opened 10 years ago
Closed 9 years ago
[e10s] Firefox Interest Dashboard: visited links are not marked as such in browser content
Categories
(Content Services Graveyard :: Interest Dashboard, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: flod, Unassigned)
References
Details
1) Visit a website with a lot of links, for example I noticed the issue on this https://gaia-l10n.allizom.org/integration/gaia-central/ 2) Open a link, in the same or a new tab, it doesn't really matter. 3) Go back to the page and check, the link just opened will maintain the style of unvisited links (blue instead of purple) 4) Open a non-e10s window, open the link from #1, you'll notice that the link is immediately marked as visited and becomes purple.
Updated•10 years ago
|
Blocks: e10s
tracking-e10s:
--- → ?
Component: General → Untriaged
Product: Firefox → Core
Summary: [e10n] Visited links are not marked as such in browser content → [e10s] Visited links are not marked as such in browser content
Reporter | ||
Comment 1•10 years ago
|
||
I think I found the culprit: couldn't reproduce on a clean profile (I thought I did test it before), it seems to be an issue with Firefox Interest Dashboard 0.8 (you need to restart at least once the browser after install).
Component: Untriaged → Extension Compatibility
OS: All → Mac OS X
Product: Core → Firefox
Summary: [e10s] Visited links are not marked as such in browser content → [e10s] Firefox Interest Dashboard: visited links are not marked as such in browser content
Comment 2•10 years ago
|
||
Adding some people involved in the project.
Updated•10 years ago
|
Updated•10 years ago
|
Component: Extension Compatibility → Interest Dashboard
Product: Firefox → Content Services
Version: Trunk → unspecified
Comment 3•9 years ago
|
||
This appears to be fixed for me, is it still broken for anyone?
tracking-e10s:
+ → ---
Comment 4•9 years ago
|
||
WFM according to comment 3
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•