Closed
Bug 121541
Opened 23 years ago
Closed 22 years ago
Links not active
Categories
(Core :: DOM: HTML Parser, defect)
Core
DOM: HTML Parser
Tracking
()
Future
People
(Reporter: bht237, Assigned: harishd)
Details
Attachments
(2 files)
Attached HTML file is from the Navigator 4 JavaScript manual.
With build ID 2002011604, links further down on the page are no longer rendered
as links as can be seen on the attached .gif image.
Comment 3•23 years ago
|
||
Page has oodles of unclosed font tags. Eventually it hits our "max number of
open tags" ceiling and then it can't open any <a> tags.
Assignee: asa → harishd
Status: UNCONFIRMED → NEW
Component: Browser-General → Parser
Ever confirmed: true
OS: Windows 95 → All
QA Contact: doronr → moied
Hardware: PC → All
Sorry for this.
It's not usually my style to open bugs like this.
I just didn't look further into the HTML because it is a Netscape hosted page
originally. As far as I am concerned I wouldn't want to give this any priority.
I am getting frustrated with this browser because of other things such as
bug 120940 suddenly has no more priority.
The thing is supposed to display pages. If it can't display a page background
then I don't know why bugs are being chased that don't even have a testcase
e.g. bug 118404.
I think you developers have to be selfish enough to sometimes give preference to
faults that have sponsors (man-hour wise) in the service provider segment of
user community.
As far as I am concerned, bugs submitted to bugzilla (except this one) have
testcases that mostly took considerable effort to extract from what would
otherwise very difficult to analyse problems.
So please by all means close this ugly thing if you wish and maybe have a look
at the more juicy bits that are almost 99% complete such as:
bug 119529
I am obviously waiting for bug 120940, bug 114827, bug 119529, bug 44306,
bug 102341, bug 96943 at least.
This is all stuff that works in Netscape 4.
Why are things suddenly getting stuck and more bugs start to apear every day
while old ones are losing priority?
This bug is a know problem with CSSFrameConstructor and fixing it would mean
rewriting parts of layout. I don't think this is feasible in the near future.
>I am obviously waiting for bug 120940, bug 114827, bug 119529, bug 44306,
>bug 102341, bug 96943 at least.
Please make your plea on the respective bugs.
Target Milestone: --- → Future
Comment 6•22 years ago
|
||
*** This bug has been marked as a duplicate of 58917 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•