Modify ↓
Ticket #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: | |
| Blocking: | Blocked by: |
Description
Right now we try to use both, we should standardize and simplify.
Change History
comment:2 Changed 4 years ago by dmethvin
See also #4129 for an example where padding-top breaks but paddingTop works.
comment:4 Changed 3 years ago by addyosmani
- Keywords camel-case added
- Owner set to john
- Status changed from new to pending
- Milestone changed from 1.4 to 1.5
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.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
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?)