ISSUE-93: Is there a problem in removing the "at risk" admonition associated with the empty exi:p element
Is there a problem in removing the "at risk" admonition associated with the empty exi:p element
- State:
- CLOSED
- Product:
- Profile
- Raised by:
- Takuki Kamiya
- Opened on:
- 2013-07-17
- Description:
- In the CR version of the profile spec, we have one feature at risk [1].
We need to remove the admonition in SOTD when we have determined the feature be retained by positive implementation experiences with the feature.
[1] http://www.w3.org/TR/2013/CR-exi-profile-20130416/#emptyPelement
- Related Actions Items:
ACTION-702 on Daniel Peintner to Disallow the use of <p/> (i.e. empty p element) in profile header options - due 2013-08-28, closed- Related emails:
- ISSUE-93: Is there a problem in removing the "at risk" admonition associated with the empty exi:p element [Profile] (from sysbot+tracker@w3.org on 2013-07-17)
Related notes:
EXIficient now supports empty <p/> element.
https://lists.w3.org/Archives/Member/member-exi-wg/2013Jul/0051.html
RK and YF seems to be in agreement [1] that we'd better remove this feature.
[1] https://lists.w3.org/Archives/Member/member-exi-wg/2013Aug/0022.html
The WG decided during 2013-08-21 telecon that we converge on non-empty <p> element by removing this feature (i.e. <p/> to signify the default option).
Takuki Kamiya, 21 Aug 2013, 18:30:09Display change log
