Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 1.7.2 SP1b
-
Fix Version/s: None
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
Description
http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.1
According to this W3C page, the <body> tag can take the regular passthrough attributes of: onclick, ondblclick, onmousedown, onmouseup, onmouseover, onmousemove, onmouseout, onkeypress, onkeydown, onkeyup, which we don't have in our ExtendedAttributeConstants definition for ice:outputBody.
As well, we might want to look into supporting: onload, onunload, which would involve framework changes, since we probably stomp over those.
I'm curious if any more of our components are missing those first intrinsic events?
According to this W3C page, the <body> tag can take the regular passthrough attributes of: onclick, ondblclick, onmousedown, onmouseup, onmouseover, onmousemove, onmouseout, onkeypress, onkeydown, onkeyup, which we don't have in our ExtendedAttributeConstants definition for ice:outputBody.
As well, we might want to look into supporting: onload, onunload, which would involve framework changes, since we probably stomp over those.
I'm curious if any more of our components are missing those first intrinsic events?
Issue Links
- depends on
-
ICE-4133
Support W3C spec pass-through attributes
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | 2.0 [ 10032 ] | |
| Affects Version/s | 1.7.2 SP1b [ 10160 ] | |
| Affects Version/s | 1.8RC1 [ 10143 ] |
| Salesforce Case | [] | |
| Fix Version/s | 2.0-Alpha3 [ 10032 ] |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Invalid [ 6 ] |