Opened 14 years ago
Closed 12 years ago
#4123 closed enhancement
Always try to use camel-case for styles and attributes
Reported by: | john | Owned by: | john |
---|---|---|---|
Priority: | major | Milestone: | 1.5 |
Component: | core | Version: | 1.3.1 |
Keywords: | camel-case | Cc: | |
Blocked by: | Blocking: |
Description
Right now we try to use both, we should standardize and simplify.
Change History (5)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
See also #4129 for an example where padding-top breaks but paddingTop works.
comment:3 Changed 14 years ago by
Milestone: | 1.3.2 → 1.3.3 |
---|
comment:4 Changed 12 years ago by
Keywords: | camel-case added |
---|---|
Milestone: | 1.4 → 1.5 |
Owner: | set to john |
Status: | new → pending |
Is this ticket still needed, John?. I notice that it's 21 months old and there hasn't been a resolution to it across the past few versions we've rolled out.
comment:5 Changed 12 years ago by
Status: | pending → closed |
---|
Automatically closed due to 14 days of inactivity.
Note: See
TracTickets for help on using
tickets.
Related:
http://blogs.msdn.com/ie/archive/2009/01/16/accessibility-improved-aria-support-in-the-IE8-RC.aspx
It sounded like ONLY the aria attributes would be supported in standard aria-checked syntax vs ariaChecked, which sounds to me like it's actually another inconsistency because the other attributes will be camelCase (at least in some modes?)