http://www.nira.com is horribly broken

RESOLVED WORKSFORME

Status

()

P5
minor
RESOLVED WORKSFORME
18 years ago
17 years ago

People

(Reporter: dr, Assigned: harishd)

Tracking

({compat})

Trunk
Future
compat
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

18 years ago
The NIRA website, http://www.nira.com, is horribly broken. If you look at the
source, the reason why is obvious. You see a lot of code that looks like this
(pay attention to start and end tags):

<layer>
  <nolayer>
    <div style="position:absolute">
  </nolayer>
  <!-- ...content here... -->
  <nolayer>
    </div>
  </nolayer>
</layer>

The author probably intended for the content to fall between layer tags if we
have layers, or between absolute-positioned div tags if not. But this document
is obviously not well-formed.

The kicker is, IE 5 renders this page just fine. So here's a bug for you. Happy
birthday... :)
(Reporter)

Updated

18 years ago
Keywords: polish, pp
(Assignee)

Comment 1

18 years ago
layers --> Evang.
Assignee: harishd → bclary
Component: Parser → Evangelism
QA Contact: bsharma → zach
(Reporter)

Comment 2

18 years ago
It's not a layers bug. We don't support layers, nor should we -- this has
nothing to do with layers.

This bug is assigned to *Parser* because IE seems to support some
non-well-formed HTML which we don't, and I suspect the particular pattern:

<foo>
  <nofoo>
    <something-else>
  </nofoo>
  <!-- ...content... -->
  <nofoo>
    </something-else>
  </nofoo>
</foo>

is a common mistake which we might (or might not) accomodate for. If you don't
want to fix this, WONTFIX is fine. I just filed this bug to bring this to your
attention.
Assignee: bclary → harishd
Component: Evangelism → Parser
QA Contact: zach
If we decide to WONTFIX this for Parser, we still need to make this an
Evangelism bug so they can contact the site, and other sites with the same problem.
QA Contact: bsharma
(Assignee)

Comment 4

18 years ago
ok..I took a shot :). Will see if this could be fixed.
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.5
(Assignee)

Updated

18 years ago
Priority: -- → P5

Updated

18 years ago
QA Contact: bsharma → moied
(Assignee)

Comment 5

18 years ago
--> 0.9.6
Target Milestone: mozilla0.9.5 → mozilla0.9.6
(Assignee)

Comment 6

18 years ago
Moving lower priority bugs to m1.0.
Target Milestone: mozilla0.9.6 → mozilla1.0

Comment 7

17 years ago
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Keywords: pp → compat

Updated

17 years ago
Blocks: 91185

Updated

17 years ago
Keywords: polish
(Assignee)

Comment 8

17 years ago
This bug has been marked "future" because the original netscape engineer working 
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug, or if it blocks your work in some way
 -- please attach your concern to the bug for reconsideration. 
Target Milestone: mozilla1.0.1 → Future
The site looks fine now. Resolving WORKSFORME.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.