[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp] [CR310] - Add doctype fields
For the reasoning, I meant to say "Due to the legacy nature of web, some portal sites are designed to generate either _strict_ or quirks mode HTML ..." I missed "strict" in my request sent to Rich. Subbu Rich Thompson wrote: > > Document: Specification > Requested by: Subbu Allamaraju > Section: 6.1.9 MarkupParams Type > Page: 31 > Old Text: > New Text: > > [O] string doctype > > - doctype: The value of the PUBLIC ID of the DOCTYPE declaration, if > any, used by the Consumer. Consumers using legacy or strict style HTML > may supply the DOCTYPE. Producers MAY honor such DOCTYPE while > generating markup. > > Document: WSRP1.0 > Section: 5.1.10 MarkupType Type > Page: 20 > Old Text: > New Text: > > [O] string doctypes[] > > - doctypes: An array of DOCTYPE declarations that the Portlet can > support. > > Reasoning: > > Due to the legacy nature of web, some portal sites are designed to > generate either or quirks mode HTML markup and expect browsers to > interpret the markup accordingly. Browsers use the HTML DOCTYPE > declaration to indicate browsers which mode to use. For example, the > following DOCTYPE declaration can be used for strict interpretation: > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" > "http://www.w3.org/TR/html4/strict.dtd";> > > During an earlier discussion, the following issues have been identified: > > a. Consumers do not know whether a portlet can generate markup in a > given DOCTYPE. > b. Portlets do not know what kind of DOCTYPE to expect. > > The above changes address these issues. Please note that, in order to > preserve backwards compat, both these elements are optional, and the > behavior is unspecified when the doctypes are not supplied by either side.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]