Closed
Bug 44759
Opened 26 years ago
Closed 25 years ago
Frame content is displayed twice
Categories
(Core :: DOM: HTML Parser, defect, P3)
Core
DOM: HTML Parser
Tracking
()
VERIFIED
FIXED
People
(Reporter: development, Assigned: harishd)
References
()
Details
(Keywords: regression, Whiteboard: [nsbeta3+][Fix in hand])
Attachments
(2 files)
|
442 bytes,
text/html
|
Details | |
|
14.62 KB,
patch
|
Details | Diff | Splinter Review |
The URL contains a frameset with 5 seperate frames. Every frame content is
shown twice. This could be a hover error.
The error did not occure with M16
Testet with BuildID 2000070620 on WinNT (also noticed on Win95)
| Reporter | ||
Comment 2•25 years ago
|
||
i have a little testcase for this problem.
i have a testcase for this.
it does not occure when i remove doctype, or the <noscript> tags.
| Reporter | ||
Comment 3•25 years ago
|
||
Comment 4•25 years ago
|
||
Reproduced on the Mac too. This is a regression that occured between 07/06 and
07/12.
As in bug 44432:
- you need a doctype: loose or strict dtd, any doctype is fine.
- even empty tags can make a difference: NOSCRIPT here, MAP there.
I'm going to attach another testcase to show that the problem is not related to
the stylesheet. If you LINK any dummy URL, like "file://foo", the bug happens
too. Note that bug 44285 was reported recently about document.write() and LINKed
stylesheet.
Reassigned to Parser/harishd like the other 2 bugs.
Assignee: pierre → harishd
Component: Layout → Parser
Keywords: regression
OS: Windows NT → All
Hardware: PC → All
*** Bug 44432 has been marked as a duplicate of this bug. ***
Comment 7•25 years ago
|
||
Marking nsbeta3+, given that we have a fix in hand and this is a relatively
serious user experience problem. This fix also fixes bug 7670 that enables
NOSCRIPT content display when JS is disabled from the preferences.
Whiteboard: Fix in hand → [nsbeta3+][Fix in hand]
| Assignee | ||
Comment 10•25 years ago
|
||
Fix is in. Marking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 11•25 years ago
|
||
This problem is no longer occuring. Verified in the Aug 24th build.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•