Closed Bug 18664 Opened 25 years ago Closed 25 years ago

{dom1}Tables inside a DIV get a border after moving the DIV

Categories

(Core :: DOM: Core & HTML, defect, P3)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
Windows 95
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 25425

People

(Reporter: ahuotari, Assigned: karnaze)

References

(
URL
)

Details

Overview Description: (I don't know under what component I should file this bug.) The tables inside a DIV-layer have a border=0 attribute. If you move the layer, the tables inside it get a border. It looks like the moving caused the tables' border attribute to change to border=1. On the other hand if you omit the border=0 attribute all together, no funny stuff occurs after the moving. Steps to Reproduce: 1) Start apprunner or viewer 2) View the given URL Actual Results: Moving a DIV-layer caused the tables inside it to get a border. Expected Results: The DIV-layer just should have moved. Build Date & Platform Bug Found: M10 build on Win32 (Checked Viewer & Apprunner) Additional Builds and Platforms Tested On: - Occurs On 11/11/99 build on Win32 (Win95 osr. 2.5 on VMWare) - Doesn't Occur On M8 build on Linux, although it doesn't work as it should (RedHat Linux 5.2) Internet Explorer 5.0 (Ver. 5.00.2014.0216) (Win95 osr. 2.5 on VMWare)
Assignee: troy → karnaze
Component: Layout → HTMLTables
Summary: Tables inside a DIV get a border after moving the DIV → Tables inside a DIV get a border after moving the DIV
Entire bug report confirmed for 1999-11-13-08-M12 on Windows NT 4.0sp3.
Status: NEW → ASSIGNED
Target Milestone: M14
Component: HTMLTables → DOM Level 1
Summary: Tables inside a DIV get a border after moving the DIV → {dom1}Tables inside a DIV get a border after moving the DIV
*** This bug has been marked as a duplicate of 25425 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Keywords: verifyme
verified fixed and dupe
Status: RESOLVED → VERIFIED
Keywords: verifyme
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.