Closed Bug 2072 Opened 26 years ago Closed 26 years ago

compatibility mode

Categories

(Core :: CSS Parsing and Computation, defect, P2)

Other
Other
defect

Tracking

()

VERIFIED DUPLICATE of bug 1312

People

(Reporter: dbaron, Assigned: rickg)

References

()

Details

I have been trying to use table inheritance (see bug 1044) to trigger compatibility mode to test what doctypes force compatibility mode...and I have been unable to find any differences. Is compatibility mode working? See the tests at the above URL. (Note: the PRE bug on the above URL is already reported as bug 2031.)
Compatibility mode is not currently controlled by a doctype. Until it is, you can switch it via a menu item in the viewer.
Assignee: peterl → rickg
Note that the viewer switch is only a *persentation* mode. It will have no effect on the parser's behavior. You'll have to wait for doctype or a meta tag support for that. Re-assigning to rickg so he can connect the parser's behavior and wire it to the HTML document's DTDMode. (Then transfer bug back to me and I'll connect the doc's DTD mode to the presentation mode.)
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
QA Contact: 4110 → 3847
Reassigning qa contact to janc@netscape.com
Note. This is currently making QA of standards compliance issues difficult (eg, verification of 2749 is awaiting doctype-controlled compat mode).
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 1312 ***
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.