Closed
Bug 1326262
Opened 9 years ago
Closed 5 years ago
Some Entries on Media Tab in Page Info Use Gray Text
Categories
(SeaMonkey :: Page Info, defect)
SeaMonkey
Page Info
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.53
People
(Reporter: david, Unassigned)
References
Details
(Keywords: reproducible)
Windows 7 Ultimate SP1
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 SeaMonkey/2.46
Entries on the Media tab in the Page Info window use gray text when the protocol is data:.
To see this, visit Slashdot at <http://slashdot.org/>. Select [View > Page Info] on the menu bar. Select the Media tab. Scroll down. All data: entries are in gray text, which is not always easy to read.
Yes, I see this running SeaMonkey in Safe Mode.
I would make this bug report minor, but I do not know of a workaround.
Comment 1•9 years ago
|
||
The styling seems to originate from <chrome://navigator/skin/pageInfo.css>:
treechildren::-moz-tree-cell-text(broken) {
font-style: italic;
color: graytext;
}
which suggests data: URIs are seen as "broken". These appear as regular entries in Firefox, for comparison.
Comment 2•9 years ago
|
||
(In reply to David E. Ross from comment #0)
I can read that without problems, and there might be good reasons for showing particular lines in grey, for example broken links, not working stuff and so on.
In your example the grey lines show "unusual" links, the contents seems to be embedded into page instead of being linked. And there are good reasons for an eye catching design of these lines, data: lines show embedded(?), not linked contents. Also see "Bug 1326377 - Media view 'Save As ...' for embedded(?) picture fails"
Any suggestions for a better design (also for accessibility aspects)?
Status: NEW → UNCONFIRMED
Ever confirmed: false
Updated•9 years ago
|
Keywords: reproducible
Comment 3•9 years ago
|
||
Personally I'm not arguing against the style but there's something wrong about the behavior – when it kicks in. I've tried saving the Slashdot page, HTML only, locally, and I see the Media tab shows links like:
file:///favicon.ico
as "broken" – that appears fine. Next I've tried saving the page as "complete", and I see all file: images listed as "broken" – that is links which otherwise appear perfectly fine:
file:///C:/Users/stanio/Downloads/Slashdot%20%20News%20for%20nerds,%20stuff%20that%20matters_files/container_data_002/UC18_Struggling_300x250_Bl.jpg
These I see in the "Media Preview" fine, and I could use the "Save As..." button to get another copy of elsewhere on the filesystem.
Comment 4•9 years ago
|
||
a) Not greyed in FF 53.0a1 (2016-12-15) (32-bit)
Entries are listed in gray when they are currently not loaded from external sources. This can have at least three reasons:
1.
They are blocked to load because of a non delivering server or an ad blocking software. This is a feature I like.
2.
They are not yet loaded. This happened for the item http://consent-pref-static.truste.com/images/truste-logo-small.png on the said slashdot frot page. While invoking the Page Info the first this item was gray. Without any interaction with the site it was black when invoking Page Info the second time. This behaviour of Seamonkey is also a feature I like.
3.
They are internal items like data: or about: items. This may be a bug. If so, this bug report should qualify exactly this error. "Some Entries …" is to broad.
Comment 6•5 years ago
|
||
NOT reproducible with with http://slashdot.org/ and installation of unofficial (by wg9s) De SeaMonkey 2.53.5 beta 1 pre Mozilla/5.0 (NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Build 20200727210001 (Default Classic Theme) on German WIN7 64bit.
Fixed on web page? Fix in SM?
![]() |
||
Comment 7•5 years ago
|
||
pageinfo was changed extensively by IanN in Bug 1575830 and others. If there are still problems a new bug should be filed. I think this one is fixed.
Not marking as duplicate because I can't pinpoint to one specific bug.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
![]() |
||
Updated•5 years ago
|
Target Milestone: --- → seamonkey2.53
You need to log in
before you can comment on or make changes to this bug.
Description
•