This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26650 - Having a single content attribute for this is okay, but wouldn't it make sense to have IDL propertie [...]
Summary: Having a single content attribute for this is okay, but wouldn't it make sens...
Status: RESOLVED LATER
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 enhancement
Target Milestone: Needs Impl Interest
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-24 18:07 UTC by contributor
Modified: 2015-08-13 07:12 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2014-08-24 18:07:24 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/tables.html
Multipage: http://www.whatwg.org/C#attr-th-sorted
Complete: http://www.whatwg.org/c#attr-th-sorted
Referrer: 

Comment:
Having a single content attribute for this is okay, but wouldn't it make sense
to have IDL properties like "sortOrdinal" and "sortReversed" instead? I'm
imagining people wanting to be able to do something like `th.sortReversed =
!!!th.sortReversed;` rather than doing more complicated string operations.

Posted from: 99.237.75.191
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2014-08-25 20:53:08 UTC 
If browsers implement what we have so far, it would make sense to consider extending the API in this manner.