Closed
Bug 143951
Opened 24 years ago
Closed 17 years ago
rows with broken content in Page Info Media tab should be emphased
Categories
(SeaMonkey :: Page Info, enhancement)
SeaMonkey
Page Info
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: aha, Assigned: db48x)
References
Details
Because actual visual presentation of broken image is insufficient for
webdevelopers (no way to recognize broken image after onLoad), I think, that
rows with broken/blocked images (or other content) shoul be emphased (by color,
italics or anything else).
Comment 1•24 years ago
|
||
How does one tell it's broken?
| Reporter | ||
Comment 2•24 years ago
|
||
=) I don't know how to implement it. But there have to be any way (in future?),
because same information will be needed for error indicating icon in status bar
(Ian tells me, that this bug is already filled).
BTW what about Error tab listing all discoverable errors in actual document? It
should be target for click on error indicating icon in status bar.
Comment 3•24 years ago
|
||
This is a duplicate of bug 41924; once that bug is fixed, there will be little
icons where images are broken.
| Reporter | ||
Comment 4•24 years ago
|
||
Ian: Duplicate? This RFE is about indicating broken content in Page Info (what
mean, that every row in Page Info | Media tab has that info), not about small
icon in status bar indicating, that whole Page has some errors.
Or I missed sommething?
Comment 5•24 years ago
|
||
Oh! My bad! Sorry, I didn't see "page info" in the description or summary
anywhere so I assumed it was a layout request. Terribly sorry. I'm so used to
people filing bugs in the totally wrong component that I just ignore that now.
Yes! This bug is indeed valid.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: [RFE] rows with broken content in Media tab should be emphased → [RFE] rows with broken content in Page Info Media tab should be emphased
Comment 6•24 years ago
|
||
An image that is unreachable is not a page error, and we should never flag it as
such, imo. The network could just be temporarily down to the server hosting the
image... So I would not bank on there being a scriptable way to tell that an
image has not loaded any time soon.
_Especially_ because that information is not stored in the DOM node but rather
in the frame. And frames are not scriptable.
| Reporter | ||
Comment 7•24 years ago
|
||
Some notes: From user's view it's missing content, from webdeveloper's view it's
error. Both cases are IMHO problems and would be good to emphase them.
Comment 8•24 years ago
|
||
From the user's view it should be a non-issue since the alt text should show
instead. I somewhat agree about the developer issue, I'm just saying that
flagging it as a page error in a user-visible location would be irresponsible
and would misrepresent the page to the user, lowering the credibility of the
rest of our error reporting.
All of which has a _very_ tangential impact on page info, as does comment #2.
| Reporter | ||
Comment 9•24 years ago
|
||
Okay, we could name it as "difference to ideal state" or "warning issue", but we
could still indicate it. IMHO it's not important, if row has red color and huge
WARNING or has small decent icon "Note" or anything else visible - it's still
only question of visualisation (and GUI).
Broken content in summary should mean: blocked link, broken data, unsupported
data format, unaccesible data (40x errors, timeout, DNS problems, wrong
protocol) etc. Do you agree?
In detailed part of concrete item should be detailed status (what's wrong with
content).
Comment 10•24 years ago
|
||
A couple of minor things here - I accidentally filed a duplicate bug on this
because the Summary mentions "rows" and not "images" (and there's a spelling
mistake in the Summary ["emphasised" or "emphasized", but not "emphased"].
The lack of flagging up which images have failed to load via the Media tab is
an important issue for Web designers, particularly for transparent GIFs (e.g.
those one-pixel spacer GIFs) - it's nearly impossible to work out if a single-
pixel transparent GIFs has loaded or not [I'd like a tick/cross column
personally rather than a colour highlight].
Another potential enhancement (possibly should be filed as a separate RFE ?) is
some way to select one of the appropriately flagged broken images, click on it
[menu, right button, whatever] and jump to the View Source window, highlighting
the IMG SRC HTML where the image is referenced. This would be fantastic for
tracking down where in the source code a broken image reference is [and now we
have "View Source Selection", I'm sure that code could be called appropriately].
Comment 11•24 years ago
|
||
*** Bug 168633 has been marked as a duplicate of this bug. ***
| Reporter | ||
Updated•23 years ago
|
Summary: [RFE] rows with broken content in Page Info Media tab should be emphased → rows with broken content in Page Info Media tab should be emphased
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•18 years ago
|
QA Contact: pmac
Comment 12•17 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 13•17 years ago
|
||
WONTFIX: See the following post in mozilla.dev.apps.seamonkey:
http://groups.google.com/group/mozilla.dev.apps.seamonkey/browse_thread/thread/722358827994743a/5b76454811bb342d
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•