fixed it by getting rid of the 100% width setting on the textarea. Prefer that because (a) it leaves us with less CSS overall, and (b) I think the fix will be more reliable across browsers.
It's times like this I want a "very low" priority :-).
I know there are bigger things that would make more of a difference, but I think the accumulation of getting these little things right actually adds up to something.
I don't want to add anything to *css; there's already too much there.
It's not that it's hard to add to the code, it's that more css is worse. If we were to fix this, it should be by figuring out why it doesn't look right naturally -- not by adding more pixel-specific padding. It's the kind of thing we should visit with whole new skins. The accumulation of attention space on these little things (which will eventually disappear on their own) adds up too.
We need to get designers working on this and marketing folks working on marketing. The way to get there, for now, is for us to focus on our strengths and get to 2.0.
should also note that css changes should be tested in all major browsers -- a big argument for doing work in large chunks. It would take an hour to test this one thing.
Cool, thanks. I don't think there was much acknowledgement of the value of what you were saying up there. I do agree with this: "the accumulation of getting these little things right actually adds up to something." Very much so. And should have said so before piling on other context.
Thx. And, I can get tunnel-visioned on applying value A (e.g. getting details right), so the reminder of bigger-picture stuff to hold in balance (e.g., we're anticipating a redesign fairly soon) is welcome.
fixed it by getting rid of the 100% width setting on the textarea. Prefer that because (a) it leaves us with less CSS overall, and (b) I think the fix will be more reliable across browsers.
--Ethan McCutchen.....Tue May 04 16:45:59 -0700 2010
Looks good in sidebar, but there's too much space on the right in _main. See Menu in both contexts: http://test.dwagn.org/wagn/Menu
--John Abbe.....Fri May 07 13:31:27 -0700 2010
I think this is the kind of thing we should just let folks handle in skins. doesn't seem bad enough to me to add more hard-coded css.
--Ethan McCutchen.....Sun Feb 13 21:53:56 -0800 2011
It's times like this I want a "very low" priority :-).
I know there are bigger things that would make more of a difference, but I think the accumulation of getting these little things right actually adds up to something.
I could just fix it on http://en.dwagn.org/*css ?
--John Abbe.....Sun Feb 13 22:50:41 -0800 2011
I don't want to add anything to *css; there's already too much there.
It's not that it's hard to add to the code, it's that more css is worse. If we were to fix this, it should be by figuring out why it doesn't look right naturally -- not by adding more pixel-specific padding. It's the kind of thing we should visit with whole new skins. The accumulation of attention space on these little things (which will eventually disappear on their own) adds up too.
We need to get designers working on this and marketing folks working on marketing. The way to get there, for now, is for us to focus on our strengths and get to 2.0.
--Ethan McCutchen.....Mon Feb 14 08:21:37 -0800 2011
should also note that css changes should be tested in all major browsers -- a big argument for doing work in large chunks. It would take an hour to test this one thing.
--Ethan McCutchen.....Mon Feb 14 08:46:34 -0800 2011
"We need to get designers working on this and marketing folks working on marketing."
That sounds awesome. Willing to drop this in that spirit.
--John Abbe.....Mon Feb 14 09:20:41 -0800 2011
Cool, thanks. I don't think there was much acknowledgement of the value of what you were saying up there. I do agree with this: "the accumulation of getting these little things right actually adds up to something." Very much so. And should have said so before piling on other context.
--Ethan McCutchen.....Mon Feb 14 09:29:48 -0800 2011
Thx. And, I can get tunnel-visioned on applying value A (e.g. getting details right), so the reminder of bigger-picture stuff to hold in balance (e.g., we're anticipating a redesign fairly soon) is welcome.
--John Abbe.....Mon Feb 14 10:15:32 -0800 2011