We have had a continuing trickle of
requests related to our CSS definitions, the most substantial of which
came late enough that it occurred as a public review comment. The proposal
has been developed because this indicated to the TC that what we currently
have will definitely not satisfy the UI designers, but there is a counter-balancing
pressure to not require all Consumer to implement too large of a set of
CSS.
Many of the issues you raise were discussed
on the Interfaces SC call yesterday. The requiresConsumerProxy field was
added such that the referenced CSS files could be treated as resources
which have to be rewritten within the set for any page including them.
Note that this would apply only if the Consumer includes the Portlet's
CSS definitions rather than supplying its own ...
This does not have to be included into
v2, but that is a decision for the TC to make regarding how we serve the
protocol's users ...
Rich
Subbu Allamaraju <>
08/17/2006 10:23 AM
To
Rich Thompson/Watson/IBM@IBMUS
cc
Subject
Re: [wsrp-interfaces] Groups - CSS-proposal.html
uploaded
Few comments:
a. Last October, we explicitly excluded this use case from V2, and added
as a candidate for V3. Why introduce this in V2 at this late stage?
b. JavaScript, and questions related to registering document level event
handlers need to be considered as well.
c. Need to discuss rewriting of id selectors
d. Need to discuss fetching/rewriting of @import rule
e. More...
Subbu
wrote:
> The document revision named CSS-proposal.html has been submitted by
Rich
> Thompson to the WSRP Interfaces SC document repository. This
document is
> revision #2 of CSS-proposal.html.
>
> Document Description:
>
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=19783
>
> Download Document:
> http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/19783/CSS-proposal.html
>
> Revision:
> This document is revision #2 of CSS-proposal.html. The document
details
> page referenced above will show the complete revision history.
>
>
> PLEASE NOTE: If the above links do not work for you, your email
application
> may be breaking the link into two pieces. You may be able to
copy and paste
> the entire link address into the address field of your web browser.
>
> -OASIS Open Administration
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries
and affiliated
entities, that may be confidential, proprietary, copyrighted
and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
