Closed
Bug 174235
Opened 22 years ago
Closed 22 years ago
wrong displayed website
Categories
(Core :: Layout: Tables, defect, P5)
Core
Layout: Tables
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: quiana, Assigned: karnaze)
References
()
Details
Attachments
(2 files)
http://www.nipc.gov/cybernotes/2002/cyberissue2002-20.htm
all html issues from nipc's cybernotes are not correctly displayed with mozilla
(1.1).
Comment 1•22 years ago
|
||
.
Assignee: attinasi → karnaze
Component: Layout → HTMLTables
QA Contact: petersen → amar
Comment 2•22 years ago
|
||
I see the bug under Mozilla OS/2 build 2002101008.
Confirming...
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Huh, how got this bug confirmed? The code is full of some ms-office tags, the
page will not validate. Before this mess can be confirmed a testcase would be
necessary ( http://www.mozilla.org/newlayout/bugathon.html). And yeah the
summary is very instructive, isn't that summary exactly the description of all
layout bugs?
Did the confirmee add value to the bug (
http://www.mozilla.org/projects/seamonkey/rules/bible.html)?
Or in short read and follow the rules at
http://www.mozilla.org/quality/help/unconfirmed.html before confirming layout bugs.
Reporter | ||
Comment 4•22 years ago
|
||
I wrote to nipc staff that they use ms-office specific tags.
they wrote back:
"Thank you for contacting the NIPC Watch. Thank you, also, for pointing
the failure of our cybernotes to render properly out to us. We have
forwarded your concern to the cybernotes personnel for their action."
it seems like author use word to edit one doc, then save it as html.
maybe it belongs to Tech Evangelism
Comment 6•22 years ago
|
||
to Bernd: I admit that I might have made a mistake confirming this bug. But
instead of putting a lot of shame on me you'd rather mark this bug as Invalid if
you really think it is. Anyway thank you for lesson.
Max, don't take it to serious, the problem behind is that a query for karnaze as
assignee will give you > 300 bugs. Without a testcase the chance that such a bug
will get fixed is exactly 0. The bug will lay around for a year and then
somebody will discover a) the url does not work or b) wfm because it was fixed
in another bug.
In order to avoid this, some diagnostics are necessary, the golden way in layout
is to create a testcase, then you will get a much better understanding why this
layout defect appears. Once you know this, you can very efficiently search
through bugzilla and mark it ,if possible, as a dupe or reassign it. I don't
want to put shame on you, I would like to see that you learn how to create
testcases and to triage on that base. If you can do this, your work will be a
great help for the whole project.
Comment 8•22 years ago
|
||
90% of the problem is that the main table has "style='margin-left: -62.1pt...'"
the non-existent borders along the bottom appear to be invalid as well.
testcase to follow
Comment 9•22 years ago
|
||
the page specifies 'border-bottom:solid windowtext .5pt;', but contains an
unclosed <tr>. also, if the xmlns="..." are remove from the <html>, the bottom
border is displayed, so in quirks mode, the page would look better.
Comment 10•22 years ago
|
||
Please change Summary to something more specific.
Comment 11•22 years ago
|
||
saving the testcase after opening it as webpage complete heavily modifies the
source.
Comment 12•22 years ago
|
||
ms cruft removed
there is <table border style='border-collapse:collapse;border:none;'>
which I believe is illegal, or at least html specifies there should be a border
css tells no.
I can't create a testcase out of it which a) validates and b) hides the bottom
border.
my vote is: invalid
<rant>
hmm, I have difficulties to take a page for serious, which should inform me
about security breaches that is written with MS-Office, a product which is a
whole bunch of security breaches.
</rant>
Comment 13•22 years ago
|
||
Resolving as invalid based on comment #12
Status: NEW → RESOLVED
Closed: 22 years ago
Priority: -- → P5
Resolution: --- → INVALID
Target Milestone: --- → Future
You need to log in
before you can comment on or make changes to this bug.
Description
•