#292 - Scrap standard boxes
-
By Chris Graham
- Added
- 9 views
| Identifier | #292 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Scrap standard boxes |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | core |
| Description | Once CSS3 is common-place we can use things like border-radius so that standard boxes aren't a useful abstraction anymore. Removing them will simplify things.
Generally it is worth trying to simplify all the CSS, in a cleaner more modern way, with more re-use. We don't need lots of different styles of rendering boxes, borders, etc. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
The CSS properties that deal with standardbox_* will necessarily need to be ripped out, affecting how the boxes and titles are rendered. But that can't be a bad thing!
Currently the major browsers are capable of rendering CSS3 properties, and where they are not (e.g. IE9 can't render text_shadow - IE10 might be able to!), they all allow the page to degrade gracefully, so there really isn't a major loss to the average user. And where a commercial enterprise wishes for the display to render 'correctly' in all browsers, they are in a position to pay for 'hacks' to take care of their wishes.
Long overdue, I say!
I'm working on this now.
I think all your intentions are to move Composr forward and drop a load of legacy stuff, so all our lives fan be easier in the future.
To this end I am really going for it in terms of restructuring things for the next version of Composr, going quite beyond the scope of this issue.
One of the reasons I am going beyond things is because for this issue I cannot realistically provide you a patch, because it would override about 80 files (bad idea...). So I want to deliver greater value, but it'll need to be with a longer term view.
I think that it is very important that you take whatever time you deem necessary for these CSS changes and the dropping of legacy support. There should be no hurry because it is more important that this be done right — as you say, you are laying the foundation for Composr's future.
Maybe you can thrill us with a .1 release which contains some of the already finished work while maybe these CSS changes become the foundation for v9.
Whatever you decide, I am sure we will be pleased with the improvements.