Closed Bug 153047 Opened 22 years ago Closed 22 years ago

Transitional rendering mode

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 153032

People

(Reporter: ian, Assigned: dbaron)

Details

As a compromise, I propose that we increase the granularity of our quirks/
standards modes.

I propose we use the following three modes:

   Standards -- default rendering mode, follows the specs as best we can. 
   Triggered by all unrecognised DOCTYPEs, all Strict DOCTYPEs, all text/xml
   content, and all documents with internal subsets.

   Transitional -- triggered for documents with Transitional DOCTYPEs, 
   including:
      HTML 4.01 Transitional with URI
      XHTML 1.0 Transitional sent as text/html
      <!DOCTYPE html SYSTEM
          "http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd">
   Acts the same as Standard mode, except for the two most common quirks:
      * use the compatability inline box model in certain cases
      * handle text/plain stylesheets as text/css

   Quirks -- triggered by documents using the DOCTYPEs that currently trigger
   our compatability mode, plus the following:
      <!doctype html public "-//w3c//dtd html 4.01 transitional//en">
   Acts the same as our current compatability mode, including the use of the
   quirks.css stylesheet.

This suggestion will increase the acceptance of our standard mode, while
accepting that most transitional documents do not expect to use the fully
standard inline box model, and accepting that many servers are not correctly
configured to sent CSS files as text/css.
oops, someone got there before me.

*** This bug has been marked as a duplicate of 153032 ***
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.