Closed
Bug 159143
Opened 22 years ago
Closed 20 years ago
caml.inria.fr - page is generated from latex using hevea, uses the LAYER tag, renders incorrectly in mozilla
Categories
(Tech Evangelism Graveyard :: French, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 141586
People
(Reporter: scottt958, Unassigned)
References
()
Details
(Whiteboard: [proprietary-js][layers])
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i586; U;) Gecko/0 BuildID: 20020607 page is generated from latex using hevea, (http://pauillac.inria.fr/~maranget/hevea) uses the LAYER tag, mozilla renders the code examples above some text, making the text unreadable. Reproducible: Always Steps to Reproduce: 1.view url with mozilla 2. 3. Actual Results: page renders incorrectly Expected Results: page renders correctly as is, or the author changes the page. The page in question is generated from latex sources by the program hevea, a latex to html translator written in ml. I wonder if all output from hevea renders incorrectly under mozilla, or just under some specific options ?
Comment 1•22 years ago
|
||
that's Europe:West, not Autors. they are also using proprietary hiding/shoing code so.
Assignee: bclary → nitot
Status: UNCONFIRMED → NEW
Component: Authors → Europe: West
Ever confirmed: true
QA Contact: mgalli → brantgurganus2001
Whiteboard: [proprietary-js][layers]
Updated•21 years ago
|
Summary: page is generated from latex using hevea, uses the LAYER tag, renders incorrectly in mozilla → caml.inria.fr - page is generated from latex using hevea, uses the LAYER tag, renders incorrectly in mozilla
Comment 2•21 years ago
|
||
moving.
Assignee: nitot → french
Component: Europe: West → French
QA Contact: brantgurganus2001 → french
Comment 3•20 years ago
|
||
these files are a copy of those in bug 141586 *** This bug has been marked as a duplicate of 141586 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•