Open
Bug 1378362
Opened 8 years ago
Updated 2 years ago
Favicon handling - problems with erroneous icon in bookmarks, embedded base64 handling and tab labelling (Nightly)
Categories
(Toolkit :: Places, defect, P3)
Tracking
()
NEW
People
(Reporter: rossgk, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170705100303
Steps to reproduce:
Prob A) Dragging a URL from address bar into bookmarks will assign a 'favicon' icon based on previous drag into bookmarks.
To reproduce, create a simple favicon-free html page
e.g.
<!DOCTYPE html>
<html>
<body>
<h1>My First Heading</h1>
<p>My first paragraph.</p>
</body>
</html>
Open page this simple page into a tab.
In another tab, open some other page (e.g. I used duckduckgo.com)
Drag the 'other page' - click-drag the "i" icon in the address bar - down into the shortcuts bar and release it there.
Now change to the simple-page tab, and drag it into the shortcut bar.
The icon assigned to simple-page is the icon of the 'other-page'.
Other problem (related?)
Problem B) Wrong title on Tab after the event of 'A' above (May have to close the simple-page tab and re-open it?)
The simple-page's tab has a Title of the "other page" (in my test case DuckDuckGo)
Problem C) Doing an embedded base64 encoded favicon doesn't seem to be working in nightly. ie using form:
<link rel="icon" type="image/x-icon" href="data:image/x-icon;base64,AAA.....characters....==" >
placed in the <Head> section does not seem to be picked up by Nightly, yet works in Safari browser.
Actual results:
As above A) wrong icon assigned to bookmark B) wrong title on tab C) no favicon picked up from an embedded data <link> tag.
Updated•8 years ago
|
Component: Untriaged → Places
Product: Firefox → Toolkit
Summary: Favicon handling - problems with erroneous icon in bookmarks, embedded base64 handling and tab labelling → Favicon handling - problems with erroneous icon in bookmarks, embedded base64 handling and tab labelling (Nightly)
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•